-
Notifications
You must be signed in to change notification settings - Fork 4
Description
Contact Details (Optional)
No response
What are you curious about?
In the current suggestion a interoperable specification will mark a data vocabulare (described resource in a specification) as reused or not. The benefit is that the amount of data vocabularies in a interoperable specification is clearly listed, even those that are indirectly reused. If we instead rely on prof:isProfileOf, we have to link between specifications more.
There is a benefit, the idea of reuse mark is to inform a harvester that this interoperable specification is not responsible for harvesting a specific data vocabulary, mostly to avoid duplicates. However, that does not enforce that someone else has provided it.
Hence, if we instead rely on prof:isProfileOf, this specication exists and has already made sure the data vocabulary at hand is harvested already.
A negative aspect is that we may end up loading many specifications to assemble a complete picture of an individual specification.