[CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb.wordpress.com/ Follow the #AmericanArchive @amarchivepub
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
Casey, I have some suggestions: 1) Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist: http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667 2) 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) 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. kc 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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb.wordpress.com/ Follow the #AmericanArchive @amarchivepub -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
Very good suggestions Karen. I'd also recommend attendees study the EBU core ontology http://www.ebu.ch/metadata/ontologies/ebucore/. While I will be unable to attend, I'm extremely interested in where you find this existing solution to be deficient. Justin On Mon, Jan 5, 2015 at 12:35 PM, Karen Coyle li...@kcoyle.net 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: http://www.worldcat.org/title/semantic-web-for-the-working- ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667 2) 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) 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. kc 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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb. wordpress.com/ Follow the #AmericanArchive @amarchivepub -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
On Jan 5, 2015, at 1:35 PM, Karen Coyle li...@kcoyle.net wrote: 1) Everyone should read at least the first chapters of the Allemang book, Semantic Web for the Working Ontologist: http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effective-modeling-in-rdfs-and-owl/oclc/73393667 +2 because it is a very good book 2) 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) +1 for knowing the distinctions between these things, yes 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. +1 but at the same time workshops are good places to see how things get done in a limited period of time. 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. +1 -1 because each of the RDF serializations have its own advantages and disadvantages — Eric Morgan
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
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. Best, Casey On 1/5/15 1:35 PM, Karen Coyle li...@kcoyle.net 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: http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effe ctive-modeling-in-rdfs-and-owl/oclc/73393667 2) 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) 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. kc 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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb.wordpress.com/ Follow the #AmericanArchive @amarchivepub -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
Also check out the *Working Ontologist* website for example files, etc.: http://workingontologist.org/ –Tod On Mon, Jan 5, 2015 at 11:04 AM, Casey Davis casey_da...@wgbh.org wrote: 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. Best, Casey On 1/5/15 1:35 PM, Karen Coyle li...@kcoyle.net 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: http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effe ctive-modeling-in-rdfs-and-owl/oclc/73393667 2) 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) 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. kc 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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb.wordpress.com/ Follow the #AmericanArchive @amarchivepub -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600 -- Tod Robbins Digital Asset Manager, MLIS todrobbins.com | @todrobbins http://www.twitter.com/#!/todrobbins
Re: [CODE4LIB] PBCore RDF Ontology Hackathon Wiki page
Great! I'm glad to hear everyone is working together on the same problem rather than rejecting the existing solutions outright. -Justin On Mon, Jan 5, 2015 at 1:04 PM, Casey Davis casey_da...@wgbh.org wrote: 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. Best, Casey On 1/5/15 1:35 PM, Karen Coyle li...@kcoyle.net 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: http://www.worldcat.org/title/semantic-web-for-the-working-ontologist-effe ctive-modeling-in-rdfs-and-owl/oclc/73393667 2) 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) 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. kc 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: http://wiki.code4lib.org/PBCore_RDF_Hackathon. 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 Broadcasting WGBH Media Library and Archives | WGBH Educational Foundation casey_da...@wgbh.orgmailto:casey_da...@wgbh.org | 617-300-5921 | One Guest Street | Boston, MA 02135 Subscribe to the American Archive bloghttp://americanarchivepb.wordpress.com/ Follow the #AmericanArchive @amarchivepub -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
