Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

which type of property to use with a controlled vocabulary #197

Open
delahousse opened this issue May 5, 2024 · 4 comments
Open

which type of property to use with a controlled vocabulary #197

delahousse opened this issue May 5, 2024 · 4 comments

Comments

@delahousse
Copy link

RDA documentation indicates the use of rdae:P20001 if the value is a structured description, an identifier or a uri.
Then in which case should we use the data property rdaed:P20001 ?

‹ex:1› | ‹rdae:P20001› | "cartographic dataset" | structured description
‹ex:1› | ‹rdae:P20001› | "1001" | identifier
‹ex:1› | ‹rdae:P20001› | ‹rdaco:1001› | IRI

@GordonDunsire
Copy link
Contributor

A datatype property has rdfs:Literal as its range. This is the class of strings, and all string values (indicated by quotation marks) are assigned to a datatype property.

As your example indicates, RDA structured, and identifier values are strings and should use the datatype property. The only recording method for an object property is IRI.

The RDA Tookit says that rdae:P20001 can use any of the four recording methods, including unstructured description which is also a string value.

@delahousse
Copy link
Author

delahousse commented May 5, 2024

Thanks a lot for your answer
So if I understand well the proper triple would be
‹ex:1› rdaed:P20001 rdaco:1001
to indicate that the type of Expression is a cartographic dataset

Jean

@GordonDunsire
Copy link
Contributor

Jean

No, the poper triple would be:
ex:1 rdae:P20001 rdaco:1001 .

The object of the the triple is a thing, not a string, so the datatype element is not appropriate. RDA Registry does not provide an object element for attributes, only for relationships, but this may be developed in future. Instead, it is correct to use the canonical element. The type of the object (and thus the range of the canonical element) can be entailed from the domain of the object IRI, in this case skos:Concept.

@delahousse
Copy link
Author

thanks for your return - jean

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants