You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some time ago, we addressed the issue of bad RDF being formed when a resource template contained only the Range class and a lookup. This came out as a blank node with the URI as a label. To fix this we introduced suppression of the blank node. This has worked well for the exact problem.
Unfortunately, the suppression only allows for one property within in the suppressed node and we are more and more facing blank nodes that may have one or more lookups in them and other properties as well. The whole new Relation/Relationship model does this as do languages.
Example from id.loc.gov in ontology. Note that the URI for hasSeries is a lookup (other values are possible). I
Describe alternatives you've considered
It is possible to exchange the lookup for a literal and make this work, but that really devalues the linked data aspect of the whole thing .
The text was updated successfully, but these errors were encountered:
Some time ago, we addressed the issue of bad RDF being formed when a resource template contained only the Range class and a lookup. This came out as a blank node with the URI as a label. To fix this we introduced suppression of the blank node. This has worked well for the exact problem.
Unfortunately, the suppression only allows for one property within in the suppressed node and we are more and more facing blank nodes that may have one or more lookups in them and other properties as well. The whole new Relation/Relationship model does this as do languages.
Example from id.loc.gov in ontology. Note that the URI for hasSeries is a lookup (other values are possible). I
Describe alternatives you've considered
It is possible to exchange the lookup for a literal and make this work, but that really devalues the linked data aspect of the whole thing .
The text was updated successfully, but these errors were encountered: