Welcome to PBCore Resources
PBCore Resources is a place to collaborate and share resources related to PBCore, a metadata standard developed to exchange information about audio/video media objects. PBCore can also be used to exchange the media objects themselves.
This ain't the official PBCore website
For an official description of the PBCore metadata standard visit www.pbcore.org. This unofficial site is intended to move PBCore forward by the people using it.
Please contribute to PBCore evolution and development
Many of us are jumping into PBCore for cataloging and sharing information about A/V objects. We are finding it useful but imperfect, and clearly the PBCore standard needs further development. Change management has been administered by the PBCore Resource Group, members of which started this website. But everyone using PBCore in the wild could usefully drive the discussion. So please consider this a welcome to write something: questions, observations, projects...bring it.
XML Bad Practices — Introduction — Robin Berjon
Perhaps this series is of interest as PBCore goes forward
"XML is now over ten years old and can euphemistically be dubbed a success. That being said, I don't believe I need convince readers that not all of its uses have been successful. Over time, many bright minds have attempted to describe how to best make use of it when designing vocabularies, but I believe it is safe to say that those efforts, no matter how excellent, have not been sufficient in ensuring that all applications of XML are produced in an entirely sane manner."
From http://berjon.com/blog/2009/12/xmlbp-intro.html (via http://delicious.com/anarchivist)
PBCore Recommendation : PBCoreCollection
Over the last few months, I have worked with Jack Brighton and Dave Rice to have the NPR API (http://www.npr.org/api) output PBCore as a supported format. In the early stages, we were able to put together a mapping of NPRML (our native XML format) to PBCore. From this mapping, my team and I started conceptualizing how this would work within the framework of the API. This exercise ultimately failed because of a philosophical issue between PBCore and the NPR API.Some thoughts on future directions of PBCore
For the last couple weeks, I've been thinking about some ways PBCore could changes to be easier to use and friendlier. Part of this was spurred by the PBCore 2.0 RFP, but also while I was trying to figure out how to teach PBCore to a workshop introducing XML at AMIA '09. This allowed me to take a step back from my use of PBCore to power digital archives and think about some bigger picture issues. I've been jotting my thoughts down elsewhere, but it would be more helpful to the community to record them here as well.pbcoreContributor element issue
Let's say I'm trying to record contributors to a movie and have a list of actors. In PBCore I can list each name, and record contributorRole as "actor." But there's no way to record what role they played as actor. Seems like a big gap! This could easily be solved in one of two ways:
Add an optional third element inside the pbcoreContributor container to record this. What to call it? Part maybe?
Add an optional attribute to contributorRole, so you can say something like:
<pbcoreContributor>
<contributor>Julie Roberts</contributor>
<contributorRole part="Erin Brockovich">Actor</contributorRole>
</pbcoreContributor>
Only problem with this is, PBCore doesn't use attributes. So maybe the first way is better:
<pbcoreContributor>
<contributor>Julie Roberts</contributor>
<contributorRole>Actor</contributorRole>
<contributorPart>Erin Brockovich</contributorPart>
</pbcoreContributor>