Open doriantaylor opened 1 year ago
Hi @doriantaylor!
Yes I think you are right. @bdarcus do you see any potential issue that this could create downstream?
I really don't know.
But this issue has me wondering about whether and how we should be making changes, given the DC stewardship?
However, BIBO is now hosted & managed by DCMI: https://www.dublincore.org/specifications/bibo/
It should be discussed with them at this point
@bdarcus you are too quick, I was answer exactly that 😄
Yes, they should by now
Just updated the readme accordingly
I wonder what should happen with this report, and how DC manages changes?
Do they, for example, have their own repositories?
It is a good question, I am not sure how they do their versioning now.
I noticed that there is an
owl:Restriction
ondcterms:isPartOf
forbibo:DocumentPart
and its subclasses. Namely it asserts that an instance should only be part of exactly one parent. Is this a desired outcome? It seems to me there are lots of cases where a distinct, identifiable document part can be part of more than one document, for instance when a given chapter shows up in two or more editions of the same book with no changes. For digital documents that use transclusions, component content management, etc., a document part could easily be part of many documents.Would there be negative ramifications to relaxing this constraint?