30
edits
Changes
m
SIGN UP HEREHere are our notes from day 1 and day 2: https://docs.google.com/spreadsheetsdocument/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z1n6VXxklbSOeGu-SqQY8ZwYqYb02YGl6HnjlyObYBYzV_OfhxaFQsk/edit?usp=sharing<br>Please also fill out this formGithub: httphttps://googithub.glcom/formsWGBH/nAvL52W9MIpbucore/
NameRebecca Guenther, InstitutionLC and NYU/MIAP, Twitter handle@rguenther52, rguenther52@gmail.com Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/email addressrhfraim @rhfraim]
added github
<br><br>
'''>>> When, Where, What time?'''
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.BIBFRAME, PREMIS) 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 ontologiesvocabularies and harness EBUCore data model when appropriate.
<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 Review facets of 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
<br>The Schema Team is working on an updated version of PBCore (PBCore 2.1), the changes of which will consist of minor tweaks and bug fixes, and is expected to be released in March 2015. Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.
==Important Links and Documentation==
* Here is the shared Google Drive folder where we will put all documentation created during the hackathon: https://drive.google.com/folderview?id=0B0v2vnLd6vOSeGJjQnFxXzlzOUk&usp=sharing
* PBCore website: http://pbcore.org/
* To download EBUCore documentation: https://tech.ebu.ch/docs/tech/tech3293.pdf
* A handy translator from RDF/XML to turtle: http://rdf-translator.appspot.com/
*Adam's EBUCore in RDF example: https://github.com/awead/pbcore-rdf/blob/master/news_ebucore_rdf.n3
*
== Working Groups ==
==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]
Jack Brighton, University of Illinois, [https://twitter.com/jackbrighton @jackbrighton]
Glenn Clatworthy, PBS, [https://twitter.com/glennclatworthy @glennclatworthy]
=== Intellectual Property Working Group ===
==== Participants ====
=== Instantiation Working Group ===
==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]
Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]
=== Essence Track Working Group ===
==== Participants ====
Name, Institution, Twitter handle/email address
Lauren Sorensen, Library of Congress, [https://twitter.com/laurensx @laurensx] laurens@nyu.edu (won't have access to work email Sat/Sun)
=== Documentation Working Group ===
==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]
Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]
== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* Sign up Everyone should read at least the first chapters of the Allemang book, Semantic Web for a WebProtege accountthe Working Ontologist: http://protegewww.stanfordworldcat.eduorg/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/733936673* Everyone should understand the RDF meaning of classes, properties, domain and range before beginning. (cf: http://kcoyle.blogspot.com/2014/11/classes-in-rdf.html)
* Review PBCore Schema: http://pbcore.org/elements/
* Read this awesome Ontology Development 101 publication: http://protege.stanford.edu/publications/ontology_development/ontology101-noy-mcguinness.html
* Read about RDF on the W3C website: http://www.w3.org/RDF/
* Read this article: "Multi-Entity Models of Resource Description in the Semantic Web: A comparison of FRBR, RDA and BIBFRAME." (http://kcoyle.net/LHTv32n4preprint.pdf)
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.htmland http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf and https://tech.ebu.ch/docs/tech/tech3293v1_5.pdf
** MODS: http://www.loc.gov/standards/mods/modsrdf/
** BIBFRAME: http://www.loc.gov/bibframe/
** DC Terms: http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=terms#
** FOAF: http://www.foaf-project.org/
**PREMIS: http://id.loc.gov/ontologies/premis.html
* Review common ontology pitfalls and the OOPS! Ontology Pitfall Scanner: http://oeg-lia3.dia.fi.upm.es/oops/catalogue.jsp
== Tips and Advice from the Community ==
==== from Karen Coyle ====
* Don't lean too heavily on Protege. Protege is very OWL-oriented and can lead one far astray. It's easy to click on check boxes without knowing what they really mean. Do as much development as you can without using Protege, and do your development in RDFS not OWL. Later you can use Protege to check your work, or to complete the code.
* Develop in ntriples or turtle but NOT rdf/xml. RDF differs from XML in some fundamental ways that are not obvious, and developing in rdf/xml masks these differences and often leads to the development of not very good ontologies.
==== from Jean-Pierre Evain ====
* I have personally no issue whatsoever with Protégé or RDF/XML for the type of ontology we seem to be aiming at
* I agree that OWL is probably not required. But this doesn't prevent using Protégé. Of course one needs to know what is specific to OWL.
== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.
