Open AllisonAnn opened 10 years ago
kvanmalssen
commented
10 years ago The Documentation Committee is working on improving definitions for all elements, including this one. I suggest we close this ticket an reopen after the revisions have been issued, if there are still problems.
AllisonAnn
commented
10 years ago Hi Kara -
Who is on the Documentation committee? That committee just sort of formed out of the blue, and we don't have any information about it. Would be nice to know.
Thanks,
Allison
On Fri, Aug 8, 2014 at 7:57 AM, kvanmalssen notifications@github.com wrote:
The Documentation Committee is working on improving definitions for all elements, including this one. I suggest we close this ticket an reopen after the revisions have been issued, if there are still problems.
— Reply to this email directly or view it on GitHub https://github.com/WGBH/PBCore2.0/issues/55#issuecomment-51596704.
caseyedavis12
commented
10 years ago Hi Allison, In June, the Steering Team had a meeting and decided that the scope of the Schema Team's work was extremely broad, and could be better divided into two completely separate teams. We decided that the Schema Team should work primarily on schema updates, controlled vocabularies, harmonization with EBUCore and RDF, another team of folks could review and refine the documentation (element and attribute definitions) and create new PBCore examples, and develop guidelines to add to the website, like a page about use of attributes, creation of a PBCore XML generator, etc. Both of these are huge projects, and the Steering Team felt that together these are too broad for one team to successfully complete within the timeline. The next thing that the Schema Team will be working on is Controlled Vocabularies. This, I imagine, will be a big undertaking, as right now none of the PBCore controlled vocabularies have any definitions, broader or narrower terms, related terms, etc.
Right now the Doc Team is reviewing current element and attribute definitions and creating new examples for each element (at the element level). If the Schema Team decides on changes to the Schema, we will edit affected element examples. We're hoping the Schema Team can wrap up Schema Review by mid-October so that the Doc Team can move forward with Documentation.
The Doc Team includes Morgan Morel, Stephanie Sapienza, Jack Brighton, Kara Van Malssen, Kevin Carter, Dave Rice, and me.
Best, Casey
I’ve copied 3 notes below about this issue from the Schema team worksheet discussion. This issue is still unresolved. Allison
Kara Van Malssen: This is a container for multiple pbcoreDescriptionDocuments so that they can be bundled together, most likely when requested from a web service or API. In this way it functions similarly to rss. A propsed new definitions could be: "Root container element for multiple PBCore records serialized as XML." or "Groups multiple pbcoreDescriptionDocument XML into one container element to allow for a serialiized output. Uses might include API returns or other web service output. This element is not intended to be equivalent to the archive/library concept of a 'collection.' Please see pbcoreAssetType for information on how PBCore can be used to express information about collections."
To disambiguate with archival uses of the term "collection" we may want to disambiguate by changing the element name to something like pbcoreContainer.
Allison Smith: Recommend that Usage Rule remain 1 time only, but also recommend best practice that it be required, and that it be the Collecting Institution name. Use DocumentDescription for Collection and Series level records. OR Rename it pbcorePackage? pbcoreContainer? QUESTION: Can PBCore be used as a means to package / transfer digital files along with its descriptive metadata (as digital objects)? Or, is this outside the scope of what PBCore is trying to do?
Leah Weisse: We have had a lot of discussion on the idea of "Collection." It has both an intellectual and a property connotation. I think we need to think of "Collection" as an intellectual grouping of assets. Therefore the attributes are describing the intellectual grouping, not necessarily the individual assets.