Code4Lib - User contributions [en]

2015 Lightning Talks

2015-02-11T22:19:00Z

CaseyDavis: added link to lightning talk slides

==Lightning Talks==
<big>'''Lightning talk signup will begin after the opening session, on a (physical) sign up board. As spots fill, we'll add them here for convenient reference.'''</big>

==Tuesday 14:30 PM to 15:30 PM==
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee
# ResCarta Recap
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre
# Vufind & Worldcat Discovery API - Karen Coombs
# [http://ronallo.com/presentations/ Video Accessibility on the Web] - Jason Ronallo
# [https://docs.google.com/presentation/d/11vBKfYbGzp5_gyksPqK1WKLvMVO_aMk03x2PvK1p_u8/view?usp=sharing ILS and Payment Systems] - Josh Weisman
# Fedora 4 Migration - Adam Wead
# [https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath] - Chris Beer
# [https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data] - Darren Hardy
# [http://matienzo.org/c4l15-lightning-talk Bread (How Baking Bread Made Me a Better Programmer)] - Mx Matienzo

==Wednesday 11:00 AM to 12:00 PM==
# [http://bit.ly/rightspres rights metadata] esmé cowles
# [https://speakerdeck.com/nabeta/2014-2015-activities-of-code4lib-japan 2014-2015 Activities around code4lib Japan] - Kosuke Tanabe
# [https://docs.google.com/presentation/d/1oJtzHWcIie-vLCpU-c_T6GaUCkWrPp0E9QDYqXiiH3M/edit?usp=sharing Arduino as a Learning Platform] - Dominic Bordelon
# [http://ablwr.github.io/c4l_preforma/#/ PreForma (Preservation Formats Project)] - Ashley Blewer
# [http://www.slideshare.net/WGBH_Archives/pbcore-rdf-ontology-hackathon-code4lib-2015 PBEBUCore] - Casey E. Davis
# RDF for relational database developers - Hector Correa
# [http://intro2libsys.info/code4lib-2015 Building a BIBFRAME catalog] - Jeremy Nelson
# [http://www.mukurtu.org Mukurtu CMS] - Alex Merrill
# Drupal, git, and sanity - Charlie M.
# How do we improve as developers? - Trey Terrell

==Thursday 9:30 AM to 10:15 AM ==

# [https://github.com/OpenGeoMetadata/metadatarepository OpenGeoMetadata] : Let's share our geo metadata
# IIIF Image Drupal module
# Clustering moving image works - Kelley McGrath
# Islandora Fedora 4 proof of concept - Danny Lamb
# Measure the future - Jason Griffey
# Low hanging fruit of accessibility - Kate Deibel
# Planning for the data schlep - Adam Constabaris
# Archiving the silenced - Natasha Nunn
# The Great Migration: Fedora 4 - Andrew Woods

[[Category:Code4Lib2015]]

2015 Social Activities

2015-02-10T19:40:21Z

CaseyDavis: adding name to karaoke sign-up

The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!

Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)

== Planned Events ==

=== Newcomer Dinner, Monday, February 9th ===

First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> LibGuides alternatives.

Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!

'''Plans'''
* When: Monday, February 9th
* Time: 6 PM (ish) or whenever you can get your group together
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]

''Guidelines:''
*Max of '''6''' per group
**Please, no waitlisting
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.
*ID yourselves so we can get a good mix of new people and veterans in each group
**New folks - n
**c4l vets - v
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')
**Leader duties
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks
***Herd folks from hotel to restaurant (know where you're going!)
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''

'''[https://docs.google.com/document/d/1rqfdRYxCZe7UrelaULzk8jpjavGGi2PGHUN1hPX7aNI/edit?usp=sharing Restaurant list and dinner sign ups posted on Google Docs]'''

=== LibTechWomen Meetup, Tuesday February 10th ===

When: Tuesday, February 10th - 5:30pm - 7pm

Where: The Veggie Grill -- 508 SW Taylor St. (One block from the hotel.) [http://veggiegrill.com/docs/vg-web-menu.pdf Menu is here.]

An informal meetup for women and their friends in library technology. No need to RSVP. I'll try to make sure there's an announcement ahead of time, and will be in the hotel lobby at 5:15 to point people in the right direction.

Questions? [mailto:sarahsimpkin@gmail.com Sarah Simpkin]

=== Craft Brew Drinkup, Tuesday February 10th ===

When: Tuesday, February 10th - 7pm - 10pm (ish)

Where: eBay Offices - 1400 SW 5th Ave, Portland, OR 97201

The Craft Brew Drinkup at Code4lib 2015 is all about sharing and enjoying good beer with fellow conference attendees. The idea is to bring bottles of your favorite beers or non-alcoholic drinks.

While you're not obligated to bring local brews from wherever you're from, participants are definitely encouraged to bring brews that you think is special and might be somewhat hard for others outside your area to find. Homebrew is especially welcome as are non-alcoholic beverages. Hot water will be provided for those who want to bring tea blends.

This year, eBay has agreed to host the Code4Lib Drinkup at their offices in downtown Portland, a 6 block walk from the conference hotel. Attendees should expect to bring something to share, either drinks or snacks. Cups will be provided by the host.

'''Please Note''': The space must be cleaned up and all folks gone no later than 11pm.

'''[https://www.eventbrite.com/e/code4lib-2015-tickets-14504558525 Space is limited to the first 200 people who register for the event!]'''

Please sign up on the [[2015 Craft Drinkup|Craft Drinkup wiki page]] to share the brews and bottles you're thinking of bringing along and special requests can be made, but don't expect that your wishes will be granted.

=== Run4Lib, Monday-Wednesday, Feb 9-11th ===

When: Monday-Wednesday (February 9th, 10th & 11th) '''leaving at 6:30AM'''

Where: Meet in Conf Hotel Lobby, see routes below.

Running Distance: 5k-ish

Run4Lib is about providing an easy opportunity to get your run on with other runners. We decided to alternate between two routes, both similar in distance.

'''Mon/Wed route''':[http://www.mapmyrun.com/routes/view/616875918 MapMyRun Run4Lib Mon/Wed Route]

'''Tues route''':[http://www.mapmyrun.com/routes/view/616883656 MapMyRun Run4Lib Tues Route]

Questions? : [mailto:wwatkins@stlawu.edu Whitni Watkins]

=== OCLC Developer House Meetup, Wednesday February 11th ===

When: Wednesday, Febraury 11th 5:30pm – 7:00pm

Where: Meet in the hotel lobby at 5:30 and figure out where we want to go (or stay?) for a drink, depending on the will of the group and the whim of the weather.

An informal meetup for alumni and anyone interested in OCLC’s Developer House event. No need to RSVP.

Drop me a note if you have any questions: [mailto:hostetls@oclc.org Shelley Hostetler]

=== Game Night, Wednesday February 11 ===

Games sign up on the [[2015_Game_Night|Game Night page]]
 
Where: ballroom/meeting room(s) at the Hilton.
 
When: February 11, 6pm

=== Karaoke, Wednesday February 11 ===

Interested in singing your face off, and/or enjoying others doing the same?

'''When:''' February 11, 8pm 
'''Where:''' [http://voiceboxpdx.com/ Voicebox PDX] (which location depends on availability) 
'''Cost:''' About $15 (depending on number of people) plus whatever food & drink you order 

# Michael Klein (@mbklein)
# Mark Matienzo (@anarchivist)
# Whitni Watkins (@nimblelibrarian)
# Julie Hardesty (@jlhardes)
# Erin White (@erinrwhite)
# Catelynne Sahadath (@metacatie)
# Rebecca Fraimow (@rhfraim)
# Peggy Griesinger (@peggygriesinger)
# Vicky Steeves (@vickysteeves)
# Sibyl Schaefer (@archivelle)
# Helen Bailey (@helenkbailey)
# Casey E. Davis (@caseyedavis1)

== Social Map - Places of Interest==

== Ideas ==

''Want to see a specific event? Add your own ideas here...''

== Local Food ==
* [http://www.foodcartsportland.com/maps/ Portland Food Carts] - Several in Pioneer Courthouse Square (2 blocks away from conference) and a huge pod off SW 10th & Alder. "Pods" are locations with multiple food carts and a good choice for a large group with different dietary needs, preferences, and budgets. Most meals are under $10. [https://www.google.com/maps/d/viewer?msa=0&mid=zBwrQkvFyvi8.k7T1OA_J6anE Pod Map]. It's rare to find a place to sit, so once you've got your meal check your map for the nearest green square in downtown.

=== Restaurants ===

=== Donuts ===
* [http://www.bluestardonuts.com/ Blue Star Donuts] - Awesome donuts.

=== Desserts ===
* [http://euphoriachocolate.com/ Euphoria Chocolate] - Sold by many gift shops, including the Made In Oregon at PDX Airport. Local chocolate, good stuff.
* [http://www.moonstruckchocolate.com/ Moonstruck Chocolate Company] - Local chocolate. Locations off SW 6th & Alder; NW 23rd between Hoyt and Glisan. NW 23rd also has a number of shops, bars, restaurants, and is good for people watching. Accessible by the Portland Streetcar.

=== Coffee ===
* [http://purringtonscatlounge.com/home/p484/ Purringtons Cat Lounge] - Cat cafe. Reservations required (hour slots, $8/person)

== Local Drinks ==

=== Bars ===

=== Breweries ===
* [http://basecampbrewingco.com/ Base Camp Brewing Co.]
* [http://www.bridgeportbrew.com/home Bridgeport Brewing]
* [http://www.burnsidebrewco.com/ Burnside Brewing Co.]
* [http://www.cascadebrewingbarrelhouse.com/ Cascade Brewing Barrel House]
* [http://www.deschutesbrewery.com/locations/portland Deschutes Brewery and Pub]
* [http://hairofthedog.com/ Hair of the Dog Brewing Co.]
* [http://www.rockbottom.com/ Rock Bottom Restaurant and Brewery]
* [http://www.rogue.com/roguemeetinghalls/ Rogue Distillery and Pub]
* [http://www.d2m.com/Tugwebsite/ Tugboat Brewing Company]
* [http://widmerbrothers.com/ Widmer Brothers Brewing]

The breweries listed above are a few blocks' walk from [http://trimet.org/index.htm Tri-Met MAX] or the [http://www.portlandstreetcar.org/node/4 Portland Streetcar] lines- which are easily accessible from the host hotel.

=== Bottle Shops and Taprooms ===
* [http://www.baileystaproom.com/ Bailey's Taproom] (Downtown)
* [http://www.johnsmarketplace.com/ John's] (SW)
* [http://www.belmont-station.com/ Belmont Station] (SE)
* [http://bazipdx.com/ Bazi Bierbrasserie] (SE)
* [http://thebeermongers.com/ Beer Mongers] (SE)
* [http://www.apexbar.com/ APEX Bar] (SE)
* [http://www.saraveza.com/ Saraveza] (N)

== Portland Events ==

=== Saturday and Sunday, February 7 and 8 ===

* [https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;4c26a341.1412 PBCore RDF ontology hackathon]
* [[PBCore RDF Hackathon]]

=== Monday, February 9 ===
* [http://tickets.orsymphony.org/single/eventDetail.aspx?p=2523 Carmina Burana], 8:00 pm, Arlene Schnitzer Concert Hall
* [http://www.powells.com/events/6382 Nick Hornby in Conversation with Cheryl Strayed], 7:00 pm, Powell's Books at Cedar Hills Crossing

=== Tuesday, February 10 ===
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium

=== Wednesday, February 11 ===

* [http://www.portland5.com/arlene-schnitzer-concert-hall/events/nederlands-dans-theater-2 Nederlands Dans Theater at Arlene Schnitzer Concert Hall], 7:30 pm; Already purchased a block of tickets for those who indicated interest early on. Anyone else buying a ticket late in the game and interested in joining us before the show for a bite to eat contact Andy Mardesich <Andy.Mardesich at ucop.edu>.

=== Thursday, February 12 ===
* [http://www.portland5.com/keller-auditorium/events/carmen Carmen], 7:30 pm, Keller Auditorium
* [http://www.mississippistudios.com/event/724141-catfish-bottlemen-portland/ Catfish and The Bottlemen], 9:00 pm, Mississippi Studios
* [http://thirdangle.org/2014-15-season/mozart-revisted/ Mozart, Revisited], 7:30 pm, Zoomtopia

=== All days ===
* [http://www.nwfilm.org/festivals/piff/ Portland International Film Festival]
* [http://portlandartmuseum.org/exhibitions/masterworks-portland-el-greco/ Masterworks | Portland: El Greco], Portland Art Museum

==Getting Around==

[[Category:Code4Lib2015]]

PBCore RDF Hackathon

2015-02-09T00:26:22Z

CaseyDavis: added github

Here are our notes from day 1 and day 2: https://docs.google.com/document/d/1n6VXxklbSOeGu-b02YGl6HnjlyObYBYzV_OfhxaFQsk/edit

Github: https://github.com/WGBH/pbucore/

 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-08T16:22:46Z

CaseyDavis: removed signup

If you are unable to attend physically, JOIN US VIA GOOGLE HANGOUTS: https://plus.google.com/hangouts/_/gzm2fr54n4wcmvusqqtspmczkua

Here are our notes from day 1 and day 2: https://docs.google.com/document/d/1n6VXxklbSOeGu-b02YGl6HnjlyObYBYzV_OfhxaFQsk/edit

 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-08T16:22:26Z

CaseyDavis: removed sign-up

If you are unable to attend physically, JOIN US VIA GOOGLE HANGOUTS: https://plus.google.com/hangouts/_/gzm2fr54n4wcmvusqqtspmczkua

Here are our notes from day 1 and day 2: https://docs.google.com/document/d/1n6VXxklbSOeGu-b02YGl6HnjlyObYBYzV_OfhxaFQsk/edit

 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-08T16:22:03Z

CaseyDavis: added note

If you are unable to attend physically, JOIN US VIA GOOGLE HANGOUTS: https://plus.google.com/hangouts/_/gzm2fr54n4wcmvusqqtspmczkua

Here are our notes from day 1 and day 2: https://docs.google.com/document/d/1n6VXxklbSOeGu-b02YGl6HnjlyObYBYzV_OfhxaFQsk/edit

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-08T16:06:03Z

CaseyDavis: minor update to google hangout link

If you are unable to attend physically, JOIN US VIA GOOGLE HANGOUTS: https://plus.google.com/hangouts/_/gzm2fr54n4wcmvusqqtspmczkua

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-07T16:28:06Z

CaseyDavis:

If you are unable to attend physically, JOIN US VIA GOOGLE HANGOUTS: https://plus.google.com/hangouts/_/g7cigyc5gz6x6h6lugh6n3dsjqa

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-07T15:23:48Z

CaseyDavis: adding new links

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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 should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-02-07T15:16:47Z

CaseyDavis: added documentation

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== 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 ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== 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 ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-01-13T18:34:34Z

CaseyDavis: new link

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Intellectual Property Working Group ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

Rebecca Fraimow, NDSR and WGBH, [https://twitter.com/rhfraim @rhfraim]

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

Julie Hardesty, Indiana University, [https://twitter.com/jlhardes @jlhardes]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Documentation Working Group ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the 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)
* 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/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.html and 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.

PBCore RDF Hackathon

2015-01-07T15:49:08Z

CaseyDavis: adding more reading material

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, BIBFRAME, PREMIS) to determine what can be used for PBCore. Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Rebecca Guenther, LC and NYU/MIAP, @rguenther52, rguenther52@gmail.com

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Documentation Working Group ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* 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
* 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.html and http://www.ebu.ch/metadata/ontologies/ebucore/ebucore.rdf
** 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

== 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.

PBCore RDF Hackathon

2015-01-05T18:43:24Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 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.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Documentation Working Group ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* 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
* 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/
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html
** 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/

== 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.

== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.

PBCore RDF Hackathon

2015-01-05T18:25:41Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 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.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing vocabularies and harness EBUCore data model when appropriate.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features). Review facets of existing ontologies. Do they meet the needs of PBCore users?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Documentation Working Group ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* Sign up for a WebProtege account: http://protege.stanford.edu/
* 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/
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html
** 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/

== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.

PBCore RDF Hackathon

2015-01-05T18:22:59Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Saturday & Sunday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Saturday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 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.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms that are needed in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts. Use existing classes from other ontologies.
 4:45pm - 5pm - Review and wrap up.

=== Sunday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 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?
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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.

 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.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
This group will focus on the intellectual content part of the knowledge base. Intellectual content in PBCore XML is currently expressed through elements like pbcoreTitle, pbcoreAssetType, pbcoreAssetDate, pbcoreSubject, pbcoreDescription, pbcoreGenre, pbcoreRelation, pbcoreCoverage, pbcoreAudienceLevel, pbbcoreAudienceRating, pbcoreAnnotation, etc.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===
This group will focus on the intellectual property part of the knowledge base. Intellectual property in PBCore XML is currently expressed through elements like pbcoreCreator, pbcoreContributor, pbcorePublisher, pbcoreRightsSummary, and roles.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Instantiation Working Group ===
This group will focus on the instantiation part of the knowledge base, excluding essence tracks.

==== Participants ====
Peggy Griesinger, MoMA/NDSR, [https://twitter.com/peggygriesinger @peggygriesinger]

=== Essence Track Working Group ===
This group will focus on the essence track part of the knowledge base.

==== Participants ====
Name, Institution, Twitter handle/email address

=== Documentation Working Group ===
This group will create, gather and organize documentation produced during the hackathon. One person from each of the other working groups should also work on the documentation working group.

==== Participants ====
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* Sign up for a WebProtege account: http://protege.stanford.edu/
* 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/
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html
** 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/

== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.

PBCore RDF Hackathon

2015-01-05T16:16:41Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T16:15:32Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T16:14:35Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T16:05:45Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T15:55:32Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T15:40:10Z

CaseyDavis:

PBCore RDF Hackathon

2015-01-05T15:37:28Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
Please also fill out this form: http://goo.gl/forms/nAvL52W9MI
 
'''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to [http://goo.gl/forms/nAvL52W9MI fill out this form] so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===

=== Instantiation Working Group ===

=== Essence Track Working Group ===

=== Documentation Working Group ===
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* Sign up for a WebProtege account: http://protege.stanford.edu/
* 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/
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html
** 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/

== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.

PBCore RDF Hackathon

2015-01-05T15:16:00Z

CaseyDavis: suggested reading

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 '''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hackathon, participants are asked to fill out this form so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 [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.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

=== Intellectual Property Working Group ===

=== Instantiation Working Group ===

=== Essence Track Working Group ===

=== Documentation Working Group ===
Casey E. Davis, WGBH, [https://twitter.com/CaseyEDavis1 @caseyedavis1]

== Suggested Reading & Preparation ==
* Sign up for a Code4Lib wiki account (if you don't already have an account)
* Sign up for a WebProtege account: http://protege.stanford.edu/
* 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/
* Review existing ontologies
** EBUCore: http://www.ebu.ch/metadata/ontologies/ebucore/index.html
** 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/

== Need more info? ==
If you have questions or need more information, feel free to contact Casey Davis at casey_davis [at] wgbh [dot] org.

PBCore RDF Hackathon

2015-01-05T15:06:10Z

CaseyDavis: inserted links

PBCore RDF Hackathon

2015-01-05T14:59:57Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 '''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hack day, participants are asked to fill out this form so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, MODS, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 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 American Archive of Public Broadcasting and the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

=== Intellectual Property Working Group ===

=== Instantiation Working Group ===

=== Essence Track Working Group ===

=== Documentation Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

== Suggested Reading & Preparation ==

PBCore RDF Hackathon

2015-01-05T14:59:30Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 '''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hack day, participants are asked to fill out this form so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 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 American Archive of Public Broadcasting and the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

=== Intellectual Property Working Group ===

=== Instantiation Working Group ===

=== Essence Track Working Group ===

=== Documentation Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

== Suggested Reading & Preparation ==

PBCore RDF Hackathon

2015-01-05T14:59:05Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 '''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hack day, participants are asked to fill out this form so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 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 American Archive of Public Broadcasting and the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee.

 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.

== Working Groups ==
Participants should sign up for a working group. On the days of the event, these sections will be filled with suggestions and links to documentation created by the working groups.

=== Intellectual Content Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

=== Intellectual Property Working Group ===

=== Instantiation Working Group ==

=== Essence Track Working Group ===

=== Documentation Working Group ===
Casey E. Davis, WGBH, @caseyedavis1

== Suggested Reading & Preparation ==

PBCore RDF Hackathon

2015-01-05T14:52:29Z

CaseyDavis:

SIGN UP HERE: https://docs.google.com/spreadsheets/d/1R4cSuYCrkQWx0IJZzBrWu_vc9_TSK_5Z-SqQY8ZwYqY/edit?usp=sharing
 '''>>> When, Where, What time?'''
 Date: '''Friday & Saturday, February 7-8, 2015'''
 Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
 Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
 hashtag: '''#PBCoreRDF15'''

== What will be the format of the event? ==

In advance of the hack day, participants are asked to fill out this form so that we can get a sense of the experience and skills of those who plan to attend. On the first day of the event, we will begin with welcome and introductions, review the agenda, and then break into groups to work on a variety of tasks. Groups may be identified as those working on intellectual content, intellectual property, technical, etc.
 
The days themselves will be structured something like this. Coffee/tea will be provided. Lunch is on your own.
=== Friday, February 7 ===
8:30am – Welcome, introductions
 9am - 9:45am - Discuss and determine the domain and scope of the ontology
 9:45am - noon - Review of existing ontologies (DC terms, EBUCore, etc.). Snacks and coffee to be served.
 Noon - 1pm – Lunch on your own.
 1pm - 2pm - Generate a comprehensive list of terms in the ontology. Snacks and coffee will be served.
 2pm - 4:45pm - Begin developing the class hierarchy and defining properties of concepts.
 4:45pm - 5pm - Review and wrap up.

=== Saturday, February 8 ===
8:30am - Review progress to date; introductions of new participants
 8:45am - noon - Continue working on class hierarchy and properties
 noon - 1pm - Lunch on your own
 1pm - 3:00pm -- Define the facets of the properties (value type, allowed values, number of values/cardinality, and other features)
 3:00pm - 4:30pm -- As a larger group, review progress and suggestions of smaller groups
 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 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 requires that metadata be stored in RDF. This is where the need for a PBCore RDF ontology comes in.

 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 American Archive of Public Broadcasting and the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee.

 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.

PBCore RDF Hackathon

2015-01-05T13:52:00Z

CaseyDavis:

SIGN UP HERE:
'''>>> When, Where, What time?'''
Date: '''Friday & Saturday, February 7-8, 2015'''
Time: '''~8:30am-5pm''' (with option of continued work throughout the conference at the same location)
Location: '''4104 Northeast 73rd Avenue, Portland, Oregon, 97218'''
hashtag: '''#PBCoreRDF15'''

PBCore RDF Hackathon

2015-01-05T13:45:19Z

CaseyDavis: test

testing