-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Search first
- I searched and no similar issues were found
What Happened?
Some background, the graph that is tested is being constructed using the layout of schemas.org where almost everything falls under the root tag #Thing. Attached a screenshot of the testing scenario with the root tag #Thing and its children.
For every #Place/#Person (and their children) a #PostalAddress is required. When adding the #PostalAddress to the property Extends of the tag #Place (in order to inherit the address data) the original Extends value (#Thing) is removed. This also changes the parent of #Place from #Thing to #PostalAddress (see screenshot).
Thing
- Intagible
--- PostalAddress
- Person <-- Setting an extend value #Thing/Intangible/PostalAddress removes the value #Thing instead of adding it.
- Place <-- Setting an extend value #Thing/Intangible/PostalAddress removes the value #Thing instead of adding it.
--- LocalBusiness
Also the following three things are noticed:
- Multiple values in the Extends property only can be used when they don't share the same root parent (in this case #Thing). When the value #PostalAddress has another root parent, that is not part of #Thing it works. In example below hierarchy works:
Thing
- Person
- Place
--- LocalBusiness
Intagible
- PostalAddress
- Multiple values in the Extends property do work if the level/ident is one deeper. In example I can't set a root tag #PostalAddress to #Thing/Place but you can set it in #Thing/Place/FoodEstablishment.
Thing
- Intagible
--- PostalAddress
- Person
- Place <-- Setting the tag #Postalddress is not possible without getting the structure changed.
--- LocalBusiness <-- Setting the tag #Postalddress is possible without structure changes.
- Multiple values in the Extends property do work if you move the conflicting tag out of the hierarchy and bring it in later. In example, you start with the following hierarchy (see screenshot):
Thing
- Person <-- Set extend tag to #Thing and to #Intangible/PostalAddress
- Place <-- Set extend tag to #Thing and to #Intangible/PostalAddress
--- LocalBusiness
Intagible
- PostalAddress
Now change the root of #Intangible from Root tag to #Thing. You will get below structure (see screenshot):
Thing
- Intagible
--- PostalAddress
- Person <-- Has the Extend value #Thing and #Thing/Intangible/PostalAddress
- Place <-- Has the Extend value #Thing and #Thing/Intangible/PostalAddress
-- LocalBusiness
Reproduce the Bug
See above.
Expected Behavior
- Adding a root tag, that shares the same parent root tag, won't change the hierarchy structure.
- Adding a root tag, that shares the same parent root tag, is possible on 'level/ident 2' as it is on 'level/ident 3'.
Files
No response
Browser, Desktop or Mobile Platform Information
Windows 11, desktop version 0.11.0.
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)



