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
{{ message }}
This repository has been archived by the owner on Nov 21, 2024. It is now read-only.
Currently the schema allows for both instantiationPhysical and instantiationDigital to be used for the same instantiation. If the elements and their usage stays as is (depending on the outcome of #67), the schema should be modified so that only one of the two is allowed, using xsd:choice. For example:
Agreed! This has never made sense to me. We use instantiationPhysical for our physical tape instantiations and instantiationDigital for audiofiles on servers.
I could see where it would be useful to allow both and disallow both. In addition to disallowing the use of both instantiationPhysical and instantiationDigital, a reference element to another instantiation (either physical or digital) could be added (if there isn't one already).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the schema allows for both instantiationPhysical and instantiationDigital to be used for the same instantiation. If the elements and their usage stays as is (depending on the outcome of #67), the schema should be modified so that only one of the two is allowed, using xsd:choice. For example:
The text was updated successfully, but these errors were encountered: