search

WGBH / PBCore2.0

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

R2: Guidance on PBCore Profile Development #5

Open pdpinch opened 13 years ago

pdpinch commented 13 years ago

Many PBCore users work in specialized or controlled collections where much of PBCore's field structure and controlled vocabularies are not relevant. Provide guidance on constraining and profiling PBCore (via controlled vocabularies, suppression of elements, authorities, and extensions) to streamline application of PBCore within controlled environments. See Jack's comments on ensuring lossless interoperability between PBCore and COVE via profiles.

pdpinch commented 13 years ago

This will be addressed in documentation.

jackbrighton commented 13 years ago

I think facilitating the use of Profiles would encourage further development and adoption of PBCore in specific applications that would broaden its use and utility. For example, COVE has certain character limits on things like Title and Description. If you could say something like COVE:pbcoreTitle enclosing a title and titleType intended for COVE, and included a COVE namespace declaration, then COVE could validate and parse that COVE-specific metadata and ignore the rest of the titles. This assumes that COVE has a namespace and can ingest PBCore, which it doesn't and can't. Merlin does have a namespace and ingests via MediaRSS. Whatever, the point is if PBCore allowed this kind of Profile-specific application it would facilitate adoption. I might go further and allow this for pbcoreSubject and pbcoreGenre also. Alternatively, you could do something like pbcoreTitle profile="COVE" but that would be harder to validate against a COVE namespace…if one existed. sigh

pdpinch commented 13 years ago

We're opening up the CV for titleType, so could we recommend the following in documentation?

<pbCoreTitle>
    <titleType source="http://pbs.org/list-of-PBS-products">COVE</titleType>
    <title>Really short COVE ti...</title>
</pbCoreTItle>

It's perhaps not as clean as a namespace, but it could be transformed, if & when one exists.

I didn't realize Merlin has namespaces, but without an XSD it can't validate, right?

jackbrighton commented 13 years ago

Addressing the CV for titleType is good, but if we shove COVE in there we'll need to also include Merlin, then Ensemble, then Kaltura, and keep adding to the list as systems change.

I'm just guessing here, but Merlin is going to need to validate somehow so I bet they have an XSD, or will have. Since I'm setting up automation to feed it my content, I sure hope so!