{"@context":"https:\/\/schema.org\/","@type":"CollectionPage","@id":"https:\/\/www.dataliberate.com\/tag\/w3c\/#CollectionPage","headline":"W3C Tag","description":"","url":"https:\/\/www.dataliberate.com\/tag\/w3c\/","hasPart":[{"@type":"BlogPosting","@id":"https:\/\/www.dataliberate.com\/2015\/06\/05\/schema-org-2-0\/","headline":"Schema.org 2.0","url":"https:\/\/www.dataliberate.com\/2015\/06\/05\/schema-org-2-0\/","datePublished":"2015-06-05","dateModified":"2015-06-05","mainEntityOfPage":"https:\/\/www.dataliberate.com\/2015\/06\/05\/schema-org-2-0\/","author":{"@type":"Person","@id":"https:\/\/www.dataliberate.com\/author\/richard-wallis\/#Person","name":"Richard Wallis","url":"https:\/\/www.dataliberate.com\/author\/richard-wallis\/","identifier":1,"image":{"@type":"ImageObject","@id":"https:\/\/secure.gravatar.com\/avatar\/dfc30377fdeb159bbd38ccbec398d54c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/dfc30377fdeb159bbd38ccbec398d54c?s=96&d=mm&r=g","height":96,"width":96}},"publisher":{"@type":"Organization","name":"Data Liberate","logo":{"@type":"ImageObject","@id":"https:\/\/dev.dataliberate.com\/wp-content\/uploads\/2011\/12\/Data_Liberate_Logo-200.png","url":"https:\/\/dev.dataliberate.com\/wp-content\/uploads\/2011\/12\/Data_Liberate_Logo-200.png","width":600,"height":60}},"image":{"@type":"ImageObject","@id":"https:\/\/www.dataliberate.com\/wp-content\/uploads\/2015\/06\/schemaorg1_thumb1.jpg","url":"https:\/\/www.dataliberate.com\/wp-content\/uploads\/2015\/06\/schemaorg1_thumb1.jpg","height":101,"width":244},"keywords":["RDF","RDFa","schema.org","vocabularies","W3C"],"commentCount":"16","comment":[{"@type":"Comment","@id":"https:\/\/www.dataliberate.com\/2015\/06\/05\/schema-org-2-0\/#Comment1","dateCreated":"2015-07-07 11:40:46","description":"Hi Tom, Sorry for delay in responding.\n\nThe answer to your question about libraries needing to produce external extensions depends on the need and purpose for richer description.  \n\nYou mention archives which I also believe needs some attention.  So much so that I am in the process of setting up a <a href=\"https:\/\/www.w3.org\/community\/architypes\/\" rel=\"nofollow\">W3C community Group<\/a> specifically to address this hopefully as a reviewed\/hosted extension.\n\nBeyond archives there will almost certainly be need to extend things further, this may well be by adding more terms to the bib.schema.org extension beyond its initial proposal.   It could be via creating or adding to external vocabularies such as <a href=\"http:\/\/bibliograph.net\" rel=\"nofollow\">BiblioGraph.net<\/a> which has provided input into the bib.schema.org proposal.\n\nThe question becomes where to draw the line between extending a general purpose vocabulary for sharing information across the web and with the search engines, and a domain specific one used to describe the internal idiosyncrasies of a specific domain such as libraries.\n\nBy externally extending Schema you will be creating terms that are less likely to be recognised by the search engines, but nevertheless be encouraging the use of a combined vocabulary, the majority of which will be, recognised by them.  My expectation is that such vocabularies will emerge in several domains, but I can not see them successfully replacing domain specific vocabularies\/ontologies used in the heart of those domains.  Fortunately the practice in the Linked Data world is to use terms from more than one vocabulary at a time.  Using both Schema.org and its extensions together will satisfy the parallel descriptive needs of sharing\/discovery and detailed domain specific management of resources.","author":{"@type":"Person","name":"Richard Wallis","url":""}},{"@type":"Comment","@id":"https:\/\/www.dataliberate.com\/2015\/06\/05\/schema-org-2-0\/#Comment2","dateCreated":"2015-06-28 21:11:03","description":"Hi Richard,\n\nIt's great to see the bib extensions nearing official status. Here's a question for you:\n\nThe 2.0 spec has two types of extension mechanism -\n\n1) Reviewed \/ hosted extensions (such as bib will become) that acquire a slice of schema.org namespace (bib.schema.org in this case)\n\n2) External extensions that you create and host yourself (e.g., at schema.mysite.org)\n\n(more on https:\/\/schema.org\/docs\/extension.html)\n\nDo you think libraries have a use for the second type, if they want to describe content in a richer way (e.g., for archives)? Or should they stick to established vocabularies separate from schema.org? All that richer vocab can still be linked and expressed on your pages in RDFa or JSON-LD or whatever, for anyone who understands it - and they are more likely to understand it than my self-hosted schema extension.\n\nThe second type seems to conflict with the text on http:\/\/schema.org\/docs\/datamodel.html -\n\n\"The type hierarchy presented on this site is not intended to be a 'global ontology' of the world. It only covers the types of entities for which we (Microsoft, Yahoo!, Google and Yandex), think we can provide some special treatment for, through our search engines, in the near future.\"\n\nThere's a thread on public-vocabs@w3.org that addresses this (somewhat): https:\/\/lists.w3.org\/Archives\/Public\/public-vocabs\/2015Feb\/thread.html#msg52\n\nTom","author":{"@type":"Person","name":"Tom Crane","url":"http:\/\/wellcomelibrary.org"}}]},{"@type":"BlogPosting","@id":"https:\/\/www.dataliberate.com\/2011\/10\/26\/w3c-library-linked-data-final-report-published\/","headline":"W3C Library Linked Data Final Report Published","url":"https:\/\/www.dataliberate.com\/2011\/10\/26\/w3c-library-linked-data-final-report-published\/","datePublished":"2011-10-26","dateModified":"2011-10-26","mainEntityOfPage":"https:\/\/www.dataliberate.com\/2011\/10\/26\/w3c-library-linked-data-final-report-published\/","author":{"@type":"Person","@id":"https:\/\/www.dataliberate.com\/author\/richard-wallis\/#Person","name":"Richard Wallis","url":"https:\/\/www.dataliberate.com\/author\/richard-wallis\/","identifier":1,"image":{"@type":"ImageObject","@id":"https:\/\/secure.gravatar.com\/avatar\/dfc30377fdeb159bbd38ccbec398d54c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/dfc30377fdeb159bbd38ccbec398d54c?s=96&d=mm&r=g","height":96,"width":96}},"publisher":{"@type":"Organization","name":"Data Liberate","logo":{"@type":"ImageObject","@id":"https:\/\/dev.dataliberate.com\/wp-content\/uploads\/2011\/12\/Data_Liberate_Logo-200.png","url":"https:\/\/dev.dataliberate.com\/wp-content\/uploads\/2011\/12\/Data_Liberate_Logo-200.png","width":600,"height":60}},"image":{"@type":"ImageObject","@id":"https:\/\/www.dataliberate.com\/wp-content\/uploads\/2012\/01\/w3c_home.png","url":"https:\/\/www.dataliberate.com\/wp-content\/uploads\/2012\/01\/w3c_home.png","height":61,"width":91},"keywords":["Libraries","Linked Data","W3C"]}]}