We used to have sh:path as a predicate that we use to indicate the property path to the literal that we can compare. However, we should also allow implicit property paths: property paths to elements that are not in the current page, but might be in another information resource (e.g., that could be retrieved by dereferencing the entity’s URI or fetching another information resource).
Example: Linked Connections clusters based on the location of the departure stops, without the departure stops location being mentioned in every connection system. Yet the location of the stops can be found in another resource.
Implication:
The spec defines a tree:path instead of using sh:path
The spec says a tree:path should be able to be resolved in the current page, but may be implicit too
We used to have
sh:pathas a predicate that we use to indicate the property path to the literal that we can compare. However, we should also allow implicit property paths: property paths to elements that are not in the current page, but might be in another information resource (e.g., that could be retrieved by dereferencing the entity’s URI or fetching another information resource).Example: Linked Connections clusters based on the location of the departure stops, without the departure stops location being mentioned in every connection system. Yet the location of the stops can be found in another resource.
Implication:
tree:pathinstead of usingsh:pathtree:pathshould be able to be resolved in the current page, but may be implicit too