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

Consider using subclasses instead of bf:noteType #35

Closed
melanieWacker opened this issue Jun 27, 2018 · 1 comment
Closed

Consider using subclasses instead of bf:noteType #35

melanieWacker opened this issue Jun 27, 2018 · 1 comment
Labels
under review Work begins on issue; incl. questions, consultations, or BFC review.

Comments

@melanieWacker
Copy link

Justification: Many notes can be attached to the appropriate node and then note type is therefore implied. That limits the cases where a noteType has to be defined. Using subclasses would provide a higher level of standardization. See also the related proposal #33

[This recommendation was made on behalf of the LD4P Art & Rare Materials BIBFRAME Ontology Extension (https://github.com/LD4P/arm).]

@raydAtLC raydAtLC added the semantic changes to rdfs:domain, rdfs:range, owl changes, etc. label Aug 9, 2018
@raydAtLC raydAtLC added the under review Work begins on issue; incl. questions, consultations, or BFC review. label Sep 4, 2018
@kefo kefo added id-fix and removed semantic changes to rdfs:domain, rdfs:range, owl changes, etc. labels May 6, 2020
@kefo
Copy link
Member

kefo commented Jun 24, 2021

All members of this scheme - https://id.loc.gov/vocabulary/mnotetype - are of type bf:Note, meaning they can be used to indicate the note type in BIbframe. We will likely add to this list over time; it is a pattern for others to consider.

@kefo kefo closed this as completed Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
under review Work begins on issue; incl. questions, consultations, or BFC review.
Projects
None yet
Development

No branches or pull requests

3 participants