The Web and SKOS, ISKO July 2008

1,903 views

Published on

This talk introduces SKOS, a soon-to-be-completed W3C standard for publishing thesauri, classification schemes and subject headings as linked data in the Web. It presents SKOS in the context of the W3C\'s Semantic Web Activity, and in the wider context of the Web where standardization doesn\'t mean \"getting everybody to do it exactly the same way\" but rather means providing a platform for innovation and diversity, to unlock new markets and new opportunities. Finally, this talk takes a mildly inquisitive look at the value propositions for linked data in the Web, and how knowledge organisation systems might be deployed as linked data for better information discovery.

Published in: Business, Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,903
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
45
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

The Web and SKOS, ISKO July 2008

  1. 1. The Web and SKOS Alistair Miles ISKO London, July 2008
  2. 2. Outline <ul><li>SKOS in 5 minutes </li></ul><ul><li>The Web and SKOS </li></ul><ul><li>Design issues </li></ul>
  3. 3. SKOS IN 5 MINUTES
  4. 4. Source: http://www.ukat.org.uk Term: Economic cooperation Used For: Economic co-operation Broader terms: Economic policy Narrower terms: Economic integration European economic cooperation European industrial cooperation Industrial cooperation Related terms: Interdependence Scope Note: Includes cooperative measures in banking, trade, industry etc., between and among countries.
  5. 5. <ul><li>SKOS is a data model </li></ul><ul><li>Use SKOS to represent a KOS as data </li></ul><ul><li>Those data can be serialised... </li></ul><ul><li>Those data can also be rendered as a graph... </li></ul>
  6. 6. Source: http://www.ukat.org.uk/downloads/data.php <rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:rdfs=&quot;http://www.w3.org/2000/01/rdf-schema#&quot; xmlns:skos=&quot;http://www.w3.org/2004/02/skos/core#&quot;> <skos:Concept rdf:about=&quot;http://www.ukat.org.uk/thesaurus/concept/1750&quot;> <skos:prefLabel>Economic cooperation</skos:prefLabel> <skos:altLabel>Economic co-operation</skos:altLabel> <skos:scopeNote>Includes cooperative measures in banking, trade, industry etc., between and among countries.</skos:scopeNote> <skos:broader rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/4382&quot;/> <skos:narrower rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/2108&quot;/> <skos:narrower rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/9505&quot;/> <skos:narrower rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/15053&quot;/> <skos:narrower rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/18987&quot;/> <skos:related rdf:resource=&quot;http://www.ukat.org.uk/thesaurus/concept/3250&quot;/> <skos:inScheme rdf:resource=&quot;http://www.ukat.org.uk/thesaurus&quot;/> </skos:Concept> </rdf:RDF>
  7. 8. <ul><li>Those data can be published in the Web... </li></ul><ul><li>...linked with other data in the Web... </li></ul><ul><li>...shared between software applications... </li></ul>
  8. 9. Source: http://rodos.zoo.ox.ac.uk/flyweb/search/flyted-bdgp/
  9. 10. <ul><li>SKOS Primer </li></ul><ul><ul><li>http://www.w3.org/TR/skos-primer </li></ul></ul><ul><li>SKOS Reference </li></ul><ul><ul><li>http://www.w3.org/TR/skos-reference </li></ul></ul><ul><li>About to publish Last Call Working Draft </li></ul><ul><li>If there are issues, raise them now! </li></ul><ul><li>[email_address] – comments </li></ul><ul><li>[email_address] – informal discussion </li></ul>
  10. 11. THE WEB AND SKOS
  11. 12. <ul><li>SKOS is not trying to re-invent knowledge organisation... </li></ul><ul><li>...rather, provide a framework for porting KOS to a shared space: the Web </li></ul><ul><li>SKOS born of... </li></ul><ul><ul><li>Knowledge Organisation </li></ul></ul><ul><ul><li>The Web </li></ul></ul><ul><li>SKOS is being developed as a Web Standard (i.e. W3C Recommendation) </li></ul>
  12. 13. <ul><li>Testimony of Sir Timothy Berners-Lee CSAIL Decentralized Information Group Massachusetts Institute of Technology </li></ul><ul><li>Before the United States House of Representatives Committee on Energy and Commerce Subcommittee on Telecommunications and the Internet </li></ul><ul><li>http://dig.csail.mit.edu/2007/03/01-ushouse-future-of-the-web.html </li></ul>
  13. 14. FOUNDATIONS OF THE WEB <ul><li>The Web and SKOS </li></ul>
  14. 15. I. Foundations of the Web <ul><li>“ The success of the World Wide Web, itself built on the open Internet, has depended on three critical factors: </li></ul><ul><ul><li>unlimited links from any part of the Web to any other; </li></ul></ul><ul><ul><li>open technical standards as the basis for continued growth of innovation applications; and </li></ul></ul><ul><ul><li>separation of network layers , enabling independent innovation for network transport, routing and information applications.” </li></ul></ul>
  15. 16. I.A. Universal Linking: Anyone can connect to anyone... <ul><li>“ In simple terms, the Web has grown because it's easy to write a Web page and easy to link to other pages.” </li></ul><ul><li>“ What makes it easy to create links ... is that there is no limit to the number of pages or number of links possible on the Web.” </li></ul><ul><li>“ Adding a Web page requires no coordination with any central authority , and has an extremely low, often zero, additional cost.” </li></ul>
  16. 17. <ul><li>“ Adding a page provides content, but adding a link provide the organization, structure and endorsement to information on the Web which turn the content as a whole into something of great value .” </li></ul>
  17. 18. <ul><li>“ The universality and flexibility of the Web's linking architecture has a unique capacity to break down boundaries of distance, language, and domains of knowledge .” </li></ul><ul><li>“ These traditional barriers fall away because the cost and complexity of a link is unaffected by most boundaries that divide other media.” </li></ul>
  18. 19. <ul><li>“ The Web's ability to allow people to forge links is why we refer to it as an abstract information space , rather than simply a network.” </li></ul>
  19. 20. THE FUTURE OF THE WEB <ul><li>The Web and SKOS </li></ul>
  20. 21. II. Looking Forward <ul><li>“ First, the Web will get better and better at helping us to manage, integrate, and analyze data .” </li></ul><ul><li>“ Today, the Web is quite effective at helping us to publish and discover documents, but the individual information elements within those documents ... cannot be handled directly as data .” </li></ul>
  21. 22. <ul><li>“ Today you can see the data with your browser, but can't get other computer programs to manipulate or analyze it without going through a lot of manual effort yourself.” </li></ul><ul><li>“ As this problem is solved, we can expect that Web as a whole to look more like a large database or spreadsheet , rather than just a set of linked documents.” </li></ul>
  22. 23. II.A. Data Integration <ul><li>“ Locked within all of this data is the key to knowledge about how to cure diseases, create business value, and govern our world more effectively.” </li></ul><ul><li>“ The good news is that a number of technical innovations... </li></ul><ul><li>... RDF which is to data what HTML is to documents , and the Web Ontology Language (OWL) which allows us to express how data sources connect together ... </li></ul><ul><li>... along with more openness in information sharing practices are moving the World Wide Web toward what we call the Semantic Web .” </li></ul>
  23. 24. <ul><li>“ Progress toward better data integration will happen through use of the key piece of technology that made the World Wide Web so successful: the link .” </li></ul><ul><li>“ The power of the Web today, including the ability to find the pages we're looking for , derives from the fact that documents are put on the Web in standard form, and then linked together .” </li></ul>
  24. 25. <ul><li>“ The Semantic Web will enable better data integration by allowing everyone who puts individual items of data on the Web to link them with other pieces of data using standard formats.” </li></ul>
  25. 26. FROM THE WEB TO SKOS <ul><li>The Web and SKOS </li></ul>
  26. 27. <ul><li>“ The success of the World Wide Web ... has depended on ... separation of network layers , enabling independent innovation for network transport, routing and information applications.” </li></ul><ul><li>“ The Web's ability to allow people to forge links is why we refer to it as an abstract information space , rather than simply a network.” </li></ul>
  27. 28. http://purl.org/net/aliman http://www.w3.org/2007/Talks/1211-whit-tbl/
  28. 29. Layers in the Web <ul><li>http://www.w3.org/2007/Talks/1211-whit-tbl/#(23) </li></ul><ul><li>Third layer is network (graph) of links between... </li></ul><ul><li>... people, organisations, diseases, genes, proteins, concepts ... </li></ul><ul><li>... capture these data in the Web </li></ul><ul><li>I.e. The Web as a platform for Linked Data </li></ul>
  29. 30. KOS as Linked Data <ul><li>Knowledge Organisation Systems can be viewed as a network of linked concepts </li></ul><ul><li>e.g. Library of Congress Subject Headings </li></ul>
  30. 31. http://purl.org/net/aliman
  31. 32. http://purl.org/net/aliman
  32. 33. http://purl.org/net/aliman
  33. 34. http://purl.org/net/aliman
  34. 35. <ul><li>Publish KOS as linked data in the Web </li></ul><ul><ul><li>Make their concepts and their interconnections part of the Web of data </li></ul></ul><ul><li>Why? </li></ul><ul><li>How? (SKOS...) </li></ul>
  35. 36. WHY KOS IN THE WEB? <ul><li>The Web and SKOS </li></ul>
  36. 37. The Value of Links <ul><li>The Web showed, links between documents are really useful </li></ul><ul><li>Google’s pagerank showed, link structure of network means something (and is worth something!) </li></ul><ul><li>Social networking Web sites showed, how much we value other kinds of links </li></ul><ul><li>KOS link ideas ... If those links are in the Web, can be exploited by anyone, anywhere ... </li></ul>
  37. 38. Quality (and Openness) <ul><li>The Web values quality and openness </li></ul><ul><ul><li>E.g. Wikipedia, very high search rank </li></ul></ul><ul><li>Most KOS are high-quality resources </li></ul><ul><ul><li>Both concepts and links </li></ul></ul><ul><li>In emerging Web of data, KOS are natural hubs ... attractors ... high gravity ... attract links </li></ul><ul><li>KOS act as firm foundations for growth of Web of data ... </li></ul>
  38. 39. Value Proposition <ul><li>Links are paths to discovery (of documents, data, ...) </li></ul><ul><li>Links can be exploited in useful and surprising ways (serendipity) </li></ul><ul><li>Well-established KOS like LCSH can be hubs in the Web of linked data </li></ul>
  39. 40. The Web Gives You... <ul><li>A globally unambiguous point of reference (URI) for each concept </li></ul><ul><li>A linking architecture that... </li></ul><ul><ul><li>...makes linking virtually free... </li></ul></ul><ul><ul><li>...requires no central coordination... </li></ul></ul><ul><ul><li>...has unlimited scalability... </li></ul></ul>
  40. 41. Why KOS in the Web? <ul><li>The Web and KOS are deeply complementary </li></ul>
  41. 42. Demo <ul><li>Linked library metadata... </li></ul><ul><li>http://inkdroid.org/bzr/lcsh/docs/slides/ -- Ed Summers </li></ul>
  42. 43. http://purl.org/net/aliman
  43. 44. http://purl.org/net/aliman
  44. 49. HOW TO PUT KOS IN THE WEB <ul><li>How SKOS? </li></ul>
  45. 50. Publishing KOS in the Web? <ul><li>RDF </li></ul><ul><ul><li>Basic data formalism for describing “graphs” of data </li></ul></ul>
  46. 51. Publishing KOS in the Web? <ul><li>SKOS </li></ul><ul><li>Standard set of... </li></ul><ul><ul><li>Resource types (Classes) </li></ul></ul><ul><ul><li>Link types (Properties) </li></ul></ul><ul><li>... For representing KOS as RDF data </li></ul>http://purl.org/net/aliman
  47. 52. SKOS Resource Types (Classes) <ul><li>skos:Concept </li></ul><ul><ul><li>E.g. LCSH concept of US Presidents </li></ul></ul><ul><li>skos:ConceptScheme </li></ul><ul><ul><li>E.g. LCSH itself </li></ul></ul>
  48. 53. SKOS Link Types (Properties) <ul><li>For labeling concepts </li></ul><ul><ul><li>skos:prefLabel, skos:altLabel, skos:hiddenLabel </li></ul></ul><ul><li>For documenting concepts </li></ul><ul><ul><li>skos:note, skos:scopeNote, skos:definition, skos:editorialNote... </li></ul></ul><ul><li>For linking concepts </li></ul><ul><ul><li>skos:broader, skos:narrower, skos:related </li></ul></ul>
  49. 54. “ SKOSIFY” <ul><li>Create a SKOS representation of a KOS e.g. LCSH </li></ul>
  50. 55. http://purl.org/net/aliman
  51. 56. Publishing SKOS Data in the Web <ul><li>Serve data file from a Web/file server </li></ul><ul><li>As linked data in the Web </li></ul><ul><ul><li>E.g. http://lcsh.info/sh85106459#concept </li></ul></ul><ul><ul><li>Content-negotiable </li></ul></ul><ul><ul><li>HTML or RDF/XML or N3 or JSON </li></ul></ul><ul><li>Via a SPARQL endpoint in the Web </li></ul><ul><ul><li>E.g. http://sparql.lcsh.info/ </li></ul></ul><ul><li>Via other Web API </li></ul>
  52. 57. DESIGN ISSUES
  53. 58. Scope of SKOS? <ul><li>SKOS will be an all-encompassing standard for the lossless representation and exchange of all varieties of knowledge organisation system...? </li></ul><ul><li>http://lists.w3.org/Archives/Public/public-swd-wg/2008Feb/0116.html -- Antoine Isaac </li></ul>
  54. 59. <ul><li>“ Yet, it happens, looking at the way these things are used now and will be in the near future (with more and more links established between them), that (i) some standardisation has to take place, and that (ii) this standardisation can be actually grounded on some observed practical similarities ( http://www.w3.org/TR/skos-ucr/ )” </li></ul><ul><li>“ Our aim is not to replace the original objects in their initial context of use, but to allow to port them to a shared space , based on a simplified model , enabling wider re-use and better interoperability .” </li></ul>http://purl.org/net/aliman
  55. 60. Lessons from the Web <ul><li>The Web is a platform for innovation </li></ul><ul><li>Web standards promote innovation and diversity </li></ul><ul><ul><li>(unlocking new markets & opportunities) </li></ul></ul><ul><li>In the Web, you can never predict all uses </li></ul><ul><li>SKOS should capture a small amount of common ground ... Just enough to enable KOS’s valuable concepts and connections to be deployed in the Web and be linked to/from </li></ul><ul><li>SKOS is infinitely extensible </li></ul><ul><ul><li>Easy to mix & match </li></ul></ul><ul><ul><li>Easy to refine </li></ul></ul>http://purl.org/net/aliman
  56. 61. Representation of Lexical Entities <ul><li>SKOS Reference includes a new, optional, extension called “SKOS eXtension for Labels (XL)” </li></ul><ul><li>Provide a foundation for finer-grained extensions... BS8723? </li></ul><ul><li>N.B. Read carefully, some subtleties! </li></ul>
  57. 62. Living in an Open World <ul><li>SKOS is an “open world” data model </li></ul><ul><li>... Why? </li></ul><ul><li>... What does it mean? </li></ul><ul><li>... What is different? </li></ul>
  58. 63. Inference & Integrity <ul><li>SKOS data model support some simple inferences </li></ul><ul><li>SKOS data model also supports some simple integrity checks </li></ul><ul><li>...but, N.B. Open world! </li></ul>
  59. 64. Linking & Mapping <ul><li>SKOS Reference defines properties for mapping between concepts in different schemes... </li></ul><ul><ul><li>skos:exactMatch, skos:closeMatch, skos:broadMatch, skos:narrowMatch, skos:relatedMatch </li></ul></ul><ul><li>In an open world, hard to draw a sharp distinction between linking two schemes and mapping two schemes </li></ul>
  60. 65. Linking & Mapping <ul><li>Where two schemes are complementary but have little overlap in scope ... Link them to create a single “virtual” scheme </li></ul><ul><ul><li>Use skos:broader, skos:narrower, skos:related </li></ul></ul><ul><li>Where two schemes have significant overlap in scope... Map them to allow translation of queries and/or metadata </li></ul><ul><ul><li>Use skos:exactMatch, skos:broadMatch etc. </li></ul></ul>
  61. 66. Linking & Mapping <ul><li>In an open world, the “boundaries” between concept schemes become optional </li></ul><ul><li>Freedom to observe or ignore boundaries </li></ul><ul><li>What is “linking” and “mapping” depends on point of view... </li></ul><ul><li>Hence SKOS Reference currently takes the view that mapping is a special type of linking (rather than that they are absolutely distinct) </li></ul>
  62. 67. SKOS & OWL <ul><li>Beginning to explore design patterns </li></ul><ul><li>We’ve been careful to leave the options open... </li></ul><ul><ul><li>Why some aspects of SKOS data model may appear counterintuitive </li></ul></ul>
  63. 68. Challenges <ul><li>SKOS is pulled in many different directions... </li></ul><ul><li>Sits between “semi-formal” knowledge organisation, informal & socially-mediated information organisation, formal knowledge representation, text-mining, the Web, ... </li></ul><ul><li>We’ve tried to support as many of “core” functionalities of “traditional” KOS applications ... </li></ul><ul><li>... without closing the door on exploring new interactions, hybrid applications ... </li></ul><ul><li>SKOS as a platform for innovation and diversity </li></ul>
  64. 69. Thank You <ul><li>All members of [email_address] </li></ul>
  65. 70. Final Word <ul><li>KOS are natural hubs, through which many things are (and can be) connected </li></ul><ul><li>The Web is a cheap, scalable, ubiquitous and open platform for linking things together </li></ul><ul><li>The Web and KOS are natural partners... </li></ul><ul><li>“ ... a unique capacity to break down boundaries of distance, language, and domains of knowledge .” </li></ul>

×