Europeana and schema.org
Presentation at the Dublin Core conference, special session on Schema.org, Sept 5, 2013.
Conference site: http://dcevents.dublincore.org/index.php/IntConf/dc-2013/
6. Why using schema.org?
Europeana tries to disseminate data to reach out to as many users
as possible
Search engines
• Customization of result lists – rich snippets
• Knowledge Graph
• Search Engine Optimization
Developers more comfortable with parsing web pages
7. In fact: schema.org and RDFa
Europeana has been publishing structured metadata via its portal
since a while
One application case: customization of public domain pages by
Creative Commons, with details on the work and Europeana
usage guidelines for public domain works
8. Europeana, Creative Commons and RDFa
http://www.europeana.eu/portal/record/02001/492A0518CA2BDF09B1642B
11FA7317F5FE43B96B.html
9. The Creative Commons Public Domain page triggers a script that harvests mark-up on the Europeana object page
10.
11. Going further
Creative Commons uses 5-6 fields, Agreed upon with the
developer(s) there
What to publish further?
Schema.org as a standardized form of more web page-based data
exchange
And it has a case – several ones in fact
Still quite prototype-ish
13. Current implementation
A glimpse of an object’s full data
http://www.europeana.eu/portal/record/02001/492A0518CA2BDF09
B1642B11FA7317F5FE43B96B.html?format=labels
Anatomy of results from an RDFa parser
http://www.w3.org/2012/pyRdfa/
Several flavors of data in it…
18. Observations
• Schema.org is simple
• Not everything can be mapped
• We’re losing grain, including some of the core benefits of
Europeana moving to the richer EDM!
• But it’s ok, because it matches needs
• And in fact it’s not entirely because of Schema.org
• And we can publish different flavors of the data in RDFa