Open AllisonAnn opened 10 years ago
I think this will be a helpful way to think about it as we begin modeling PBCore as RDF.
For the XSD, I think instantiationDigital and instantiationPhysical supports this. It is up to the implementor to choose the elements they need depending on which type of instantiation they choose, as you indicate. The one problem I have with these is that the XSD actually allows you to select both, which is problematic. I will open a separate issue on that.
What about physical and digital attributes of the pbcoreInstantiation element? Then we could eliminate the physicalInstantiation and digitalInstantiation elements altogether and express them with format or something else. I'm not sure about the XSD validation when it comes to attributes, though. For example, this could be perfectly legal:
<pbcoreInstantiation type="digital">
<instantiationDimensions unitsOfMeasure="inches">1 x 4 x 9</instantiationDimensions>
</pbcoreInstantiation>
I would like the PBCore Instantiation class to have a “pbcoreInstantiationObjectClass” element with the following class types:
• Physical instantiation • Digital instantiation
These classes could be used by local systems to determine the properties (pbcore Instantiation elements and attributes), relationships, and behaviors of those classes.