-
Notifications
You must be signed in to change notification settings - Fork 2
Initial version of library and bflc vocabulary #17
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
base: main
Are you sure you want to change the base?
Conversation
data/vocab/bflc.ttl
Outdated
| @prefix owl: <http://www.w3.org/2002/07/owl#> . | ||
| @prefix bf: <http://id.loc.gov/ontologies/bibframe/> . | ||
| @prefix bflc: <http://bibfra.me/vocab/bflc/> . | ||
| @prefix bflcext: <http://id.loc.gov/ontologies/bflc/> . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bflc --> http://bibfra.me/vocab/bflc/
bflcext --> http://id.loc.gov/ontologies/bflc/
Any better name suggestion for "bflcext"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does bflc stand for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bflc = BIBFRAME LC Extension
LC = Library of Congress
59abe68 to
ea86ebe
Compare
|
Please add the new file(s) to the list here so they can be validated: https://github.com/ebsco/builde/blob/main/package.json#L3 You can setup your environment to run this check prior to committing/pushing. Eventually we will setup a CI pipeline which runs this. The validator tool doesn't support wildcards so we have to pass each file in by name. |
6be595a to
34b63c5
Compare
| rdfs:range rdfs:Literal . | ||
| rdfs:range rdfs:Literal . | ||
|
|
||
| library:place a rdf:Property ; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have two redundant 'place' properties in builde that store place as a literal text.
http://bibfra.me/vocab/lite/place -> Used in ProviderEvent resource.
http://bibfra.me/vocab/marc/place -> Used in Concept, Meeting, Jurisdiction, Organization resources.
See these examples:
https://viewer.internal.live.library.link/graph/cairn/resource/4AUq8wyT5W8 (uses lite:place property)
https://viewer.internal.live.library.link/graph/cairn/resource/Fh_0PnNViIM (uses library:place property)
In Bibframe (LC's) vocabulary, there is a property http://id.loc.gov/ontologies/bflc/simplePlace that holds place as a literal. However, there is no 'simplePlace' in builde.
In order to clean this up, how about doing one of the following two options:
Option 1:
- Deprecate one of http://bibfra.me/vocab/lite/place or http://bibfra.me/vocab/marc/place.
- Use the retained one as a property that can point to either a Place resource or a Literal.
Option 2:
- Deprecate one of http://bibfra.me/vocab/lite/place or http://bibfra.me/vocab/marc/place.
- Use the retained one as a property that points to a Place resource (instead of holding the literal place text)
- Create a new property http://bibfra.me/vocab/bflc/simplePlace equivalent to Bibframe's simplePlace
What do you think? If needed, I can schedule a short call to discuss this.
No description provided.