30
edits
Changes
m
no edit summary
8:30am – Welcome, introductions
<br>9am - 9:45am - Discuss and determine the domain and scope of the ontology
<br>9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, etc.)to determine what can be used for PBCore. Snacks and coffee to be served.
<br>Noon - 1pm – Lunch on your own.
<br>1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.<br>2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing classes from other ontologies.
<br>4:45pm - 5pm - Review and wrap up.
<br> 8:45am - noon - Continue working on class hierarchy and properties
<br> noon - 1pm - Lunch on your own
<br> 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Keep existing ontologies in mind. Do they meet the needs of PBCore users?
<br> 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
<br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation
== Summary & Background==
The PBCore RDF Ontology Hackathon is occurring out of a growing need for PBCore users to express their metadata in RDF. A number of PBCore users contribute to and are part of the [http://projecthydra.org/ Project Hydra] community, a collaborative, open source effort to build digital repository software solutions at archives institutions. Hydra is built on a framework that uses Fedora Commons as the repository for storing metadata. Many users are seeking to update their Fedora repositories to the latest version (Fedora 4), which provides a great opportunity to develop an RDF data structure. If PBCore had an RDF ontology, it would be easier for PBCore users to take full advantage of Fedora 4 capabilities in managing data and encourage adoption of Fedora 4.
<br>We envision building upon existing knowledge bases that are already well established. In particular, we hope to harmonize the EBUCore ontology with PBCore and determine what existing terms from the EBUCore vocabulary can be re-used, and what concepts may be unique to PBCore that would deem the need for additional terms.
<br>[http://www.pbcore.org PBCore] is a metadata schema for audiovisual materials. Its original development in 2004 was funded by the Corporation for Public Broadcasting, with a goal of creating a metadata standard for public broadcasters to share information about their video and audio assets within and among public media stations. Since its conception, PBCore has been adopted by a growing number of audiovisual archives and organizations that needed a way to describe their archival audiovisual collections. The schema has been reviewed multiple times and is currently in further development via the [http://www.americanarchive.org American Archive of Public Broadcasting] and the [http://amianet.org/ Association of Moving Image Archivists (AMIA)] PBCore Advisory Subcommittee.
