Skip to content

Conversation

@pkjacob
Copy link
Collaborator

@pkjacob pkjacob commented Aug 15, 2024

No description provided.

@pkjacob pkjacob requested a review from gloriagonz August 15, 2024 21:28
@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/> .
Copy link
Collaborator Author

@pkjacob pkjacob Aug 15, 2024

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"?

Copy link
Contributor

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?

Copy link
Collaborator Author

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

@pkjacob pkjacob force-pushed the pjacob/bflc branch 7 times, most recently from 59abe68 to ea86ebe Compare August 20, 2024 18:29
@gmreburn
Copy link
Contributor

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.

@pkjacob pkjacob force-pushed the pjacob/bflc branch 2 times, most recently from 6be595a to 34b63c5 Compare November 12, 2024 15:17
rdfs:range rdfs:Literal .
rdfs:range rdfs:Literal .

library:place a rdf:Property ;
Copy link
Collaborator Author

@pkjacob pkjacob Nov 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HI @gmreburn @gloriagonz

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:

  1. Deprecate one of http://bibfra.me/vocab/lite/place or http://bibfra.me/vocab/marc/place.
  2. Use the retained one as a property that can point to either a Place resource or a Literal.

Option 2:

  1. Deprecate one of http://bibfra.me/vocab/lite/place or http://bibfra.me/vocab/marc/place.
  2. Use the retained one as a property that points to a ⁠Place resource (instead of holding the literal place text)
  3. 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.

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

Successfully merging this pull request may close these issues.

3 participants