We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, language properties from the 008/35-37 can have as their object a linked data resource from id.loc.gov, e.g.:
<bf:Work rdf:about="http://example.org/1#Work"> <bf:language> <bf:Language rdf:about="http://id.loc.gov/vocabulary/languages/eng"/> </bf:language> </bf:Work>
This seems a little more elaborate than necessary. Would it be better to just convert like this?
<bf:Work rdf:about="http://example.org/1#Work"> <bf:language rdf:resource="http://id.loc.gov/vocabulary/languages/eng"/> </bf:Work>
In addition, the 041 creates entities like this:
<bf:Work rdf:about="http://example.org/1#Work"> <bf:language> <bf:Language> <bf:identifiedBy> <bf:Identifier> <rdf:value rdf:resource="http://id.loc.gov/vocabulary/languages/eng"/> <bf:source> <bf:Source rdf:about="http://id.loc.gov/vocabulary/languages"/> </bf:source> </bf:Identifier> </bf:identifiedBy> </bf:Language> </bf:language> </bf:Work>
In the case where there is no bf:part property of the bf:Language entity, perhaps it would be better to simplify this down to the same pattern:
bf:part
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
wafschneider
No branches or pull requests
Currently, language properties from the 008/35-37 can have as their object a linked data resource from id.loc.gov, e.g.:
This seems a little more elaborate than necessary. Would it be better to just convert like this?
In addition, the 041 creates entities like this:
In the case where there is no
bf:part
property of the bf:Language entity, perhaps it would be better to simplify this down to the same pattern:The text was updated successfully, but these errors were encountered: