Thanks for your suggestions, Karen! I have added them to the wiki.

Justin, luckily we have a representative from EBU who is planning to
attend. We are definitely reviewing the EBUCore ontology and are seeing
this hackathon as an opportunity to harmonize EBUCore and PBCore as much
as possible.


On 1/5/15 1:35 PM, "Karen Coyle" <[log in to unmask]> wrote:

>Casey, I have some suggestions:
>1) Everyone should read at least the first chapters of the Allemang
>book, Semantic Web for the Working Ontologist:
>2) Everyone should understand the RDF meaning of classes, properties,
>domain and range before beginning. (cf:
>3) 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.
>4) 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.
>On 1/5/15 9:35 AM, Casey Davis wrote:
>> Hi Code4Libbers,
>> In case you are interested in attending or staying in the know about
>>the PBCore RDF ontology hackathon happening on February 7 & 8 before
>>Code4Lib, check out the Wiki page:
>> This is also where we
>>will provide links to all documentation created during the hackathon. In
>>case you are unable to join us, we will be using the hashtag
>>#PBCoreRDF15 on the days of the event.
>> Best,
>> Casey
>> Casey E. Davis, MLIS | Project Manager, American Archive of Public
>> WGBH Media Library and Archives | WGBH Educational Foundation
>> [log in to unmask]<mailto:[log in to unmask]> | 617-300-5921 | One
>>Guest Street | Boston, MA 02135
>> Subscribe to the American Archive
>> Follow the #AmericanArchive @amarchivepub
>Karen Coyle
>[log in to unmask]
>m: +1-510-435-8234
>skype: kcoylenet/+1-510-984-3600