You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Justification: Current definitions reference only the organization and arrangement of a collection of objects. We recommend the extension of the terms to include individual objects, so that for example, during exhibitions the arrangement of a book (opened to plate 10) can be noted.
[This recommendation was made on behalf of the LD4P Art & Rare Materials BIBFRAME Ontology Extension (https://github.com/LD4P/arm).]
The text was updated successfully, but these errors were encountered:
We made a pretty big change to this area of the vocabulary the last time around: #77
That's one of the reasons I annotated this as "need to revisit" back in June. Is the request here more or less the same except now targeting the collectionArrangement property and CollectionArrangement class, though both bake the issue you present into the name not just the definition (but maybe that is OK?)?
@sfolsom -- using bf:collectionArrangement and bf:CollectionArrangement instead of bf:arrangment/Arrangement, does the definition still need to be refined?
I think the use case of an arrangement of a single resource still holds, which is a little different from how bf:collectionArrangement/bf:CollectionArrangement are named/defined. It would seem to me that bf:arrangment/Arrangement (as @kefo provides in #77) would encapsulate bf:collectionArrangement/bf:CollectionArrangement, but not the other way around.
Justification: Current definitions reference only the organization and arrangement of a collection of objects. We recommend the extension of the terms to include individual objects, so that for example, during exhibitions the arrangement of a book (opened to plate 10) can be noted.
[This recommendation was made on behalf of the LD4P Art & Rare Materials BIBFRAME Ontology Extension (https://github.com/LD4P/arm).]
The text was updated successfully, but these errors were encountered: