search

WGBH / PBCore2.0

Public Broadcasting Metadata Dictionary Project
http://www.pbcore.org
32 stars 9 forks source link

R22: Allow or provide guidance on validatable expression of multiple PBCore assets within a single XML document/feed. #25

Closed pdpinch closed 13 years ago

pdpinch commented 14 years ago

Exchange of PBCore data between systems is complicated by lack of recommended methodology or means to package multiple assets into a single document or package (see MARCXML's collection element, modsCollection, atom, etc)

pdpinch commented 14 years ago

Plan to add a PBCoreCollection element at the top of the hierarchy.

Also plan to recommend use of BagIt as an alternative.

WeAreAVP commented 13 years ago

It's good to see two options, either the PBCoreCollection element or bagit. The PBCore 2.0 draft 3 adds a 'PBCoreCollection' element; however the new 'PBCoreCollection' is the only permitted top-level element; thus a PBCore XML may not be written without the expression of a 'PBCoreCollection'. At one point we discussed allow either 'PBCoreDescriptionDocument' or 'PBCoreCollection' as the top level element (I remember Kara asking for allowance of 'pbcoreInstantiation' as an allowable top level element).

pdpinch commented 13 years ago

I didn't think that was technically allowed in XML Schema. If I'm wrong, can you propose the schema change?

WeAreAVP commented 13 years ago

Yeah, this is definitely allowed and well used in other comparable schemas. For instance see how mods accomplishes the same task: http://www.loc.gov/standards/mods/v3/mods-3-3.xsd. The top level element may either be mods or modsCollection.

MarcosSueiro commented 13 years ago

The upcoming AES schema also uses something similar.

Can this be accomplished by formalizing an "isPartOf" via an xLink between different assets, or is it too complicated?

http://www.w3.org/TR/xlink11/

pdpinch commented 13 years ago

We will publish an example use of pbcoreCollection.