Brief – Glen says:

1. Brief – Glen says: • Tom (Heath) • A gentle and fun introduction to Linked Data for the uninitiated so try not to make it too technical • Liz • A gentle and fun introduction to the wonderful world of geography • Chris • GeoVation to show how geographic information can be a creative force in the development of the Web (and of course the linked data web) • After the morning coffee break the focus changes to showing how Linked Data is already being used • Tom (Scott) and Silver • Describe what the BBC has been doing and how it can be exploited. Also if you can include plans or intentions for the future • John, Jeni • data.gov.uk and Making Public Data Public but also a little on INSPIRE and the work being done as part of the URI group? • After lunch the emphasis will switch to more technical detail. • Brian • How geography is a link within a local authority • Ian • An overview of Mashups and how they tend to use Geographic information and mapping • Hugh • About 30 mins giving more detail behind the technologies and also about the processes, advantages and pitfalls of linking?

2. Using Linked Data Hugh Glaser Seme4 Ltd. With thanks to many, including Ian Millard

3. I do • I am not a Level 9 Warlock • sameAs.org • A simple part of the Linked Data flora or fauna • Does one thing well, we hope • rkbexplorer.com • A set of services that use Linked Data • Will start on sameAs and move to rkbexplorer if we feel like it/have time

4. sameAs.org • How do you find links? • Backlinks (links to ‘foreign’ URIs) are important • Special sort of backlink • URIa {owl:sameAs, skos:exactMatch, …} URIb

5. E.g. • Plenty of links out there • BBC says BBC-Metallica sameAsdbpedia-Metallica • OpenCyc says OpenCyc-Metallica sameAsdbpedia-Metallica • Hetfield says Hetfield-Metallica sameAs BBC-Metallica • Gathering all the links is a challenge • From Hetfield-Metallica you can find all (iterative) • But from BBC-Metallica never find Hetfield-Metallica • Simple service to gather these assertions to get the network effect promised by Linked Data • Google might have done it (might yet) • Sindice (Semantic Web search engine) might have

6. Some screens

7. More Screens • London • Southampton • http://education.data.gov.uk/id/institution/H-0149 • http://rae2001.rkbexplorer.com/id/resource-H-0068 • http://dbpedia.org/resource/Tim_Berners-Lee

8. Other Facilities • Rollback • Deprecation • Federation

9. FederatingsameAs • Someone can spider/harvest and centralise • Will you trust them? • Etc. • A dataset provider can provide their own sameAs service • Many socio-advantages • Silver’s comments on BBC internal data fusion • British Museum • education.gov.uk could clearly do with this • Requires client middleware to consult trusted sameAs services and provide the equivalence group (class)

10. Enough sameAs Already?

11. rkbexplorer.com • Actually where a lot of sameAs comes from • But first the services • Then the applications

12. Many Technologies • Distributed sameAs • Distributed query • Caching URI resolution • Caching semantic network • Dynamic ontology mapping

13. Concluding Comments • Linked Data, with the right bits of glue, is just a stunning way of performing data fusion

14. What Happens When Authorities Collide? • The Answer to Multiple Authorities is not to Create Another One • What is the Granularity of an Authority? • When we have PIDs, what do we do next? • How do we Manage the Infrastructure? • http://eprints.ecs.soton.ac.uk/18452/

15. Some Assumptions • Authority is established, not bestowed • IDs are URIs and can be resolved • Preferably to RDF, but not necessarily • But they must resolve • otherwise you can’t even guess what they mean • Not just people • the infrastructure should work for publications, institutions, lectures, experiments… • We want to solve problems, not create them • I don’t have long…

16. Barcode on the forehead is a Chimera

17. Each Metadata owner publishes its own identifiers • This is absolutely right • Their workflow depends on them • Their concept of the entity will be unique to them • They own it • If they used someone else’s, how would they deal with a change? • Split of entity • Join of entity • Correction of entity

18. Institutional “Use cases” • What other institutions do my workers work with? • What do my departments know about Jane? • What projects (RCUK, JISC, EU) do we have in photovoltaics? • Why would a University keep project metadata? • Surely they can just “use” the JISC metadata • Give me a snapshot of Jane’s activity • How does the library know who is using which texts?

19. Identity Knowledge • Is different from other knowledge • Goodness about separation • License • Provenance • Trust • Duplication (maintenance) • Internal process • Mistake to combine discovery with service • Simple services that do one set of things well • Do not duplicate/copy data, e.g. names • Creates many problems: coherence, maintenance… • Identity is context-dependent • Use context more than publication context

20. Some requirements • Scalability • Distributed • Metadata publishers should be able to give some authority of their equivalence • These may be context dependent,e.g. • Equivalence as a worker here (Department, JISC?) • Equivalence as a professional (previous inst.) • Equivalence as a person (dbpedia) • Other should be able to make different statements • Essentially anarchy, as the rest of the Web

21. Co-Reference Service (CRS) • How we do it • RESTful service • URIi -> { URI1, …, URIi, …, URIn } • Any metadata owner can publish co-reference to other sources • Multiple “opinions” if required • Others can provide such services • Middleware or simpler can aggregate • From recognised/approved CRSes • “Let the buyer beware”? • “Let the buyer be empowered”

22. For Example

23. Some Other Issues • Deprecation • CRS Discovery • Recommended CRSes from metadata from resolved URI • Aggregating Services • Robustness to failure • Actually CRS is not confined to Linked Data

24. Examples • Running out of time • For the Sceptical • So this is what can be done • http://rkbexplorer.com/ • http://dotac.info/ • http://sameas.org/ • http://jisc.rkbexplorer.com/id/org-77

25. RKBExplorer – The ReSIST Project

26. A Paper

27. Now Look at an Author

28. Or a Couple of People And howthey arelinked

29. And Why are they Linked?

30. Co-Reference Closure

31. Using the CRS Service

32. Solving an Existing Problem

33. Finding Co-reference

34. Many Platforms - Gadgets Mark Borkum did this

35. iPhone App

36. Concluding Remarks • CRS • A service to mediate between authorities • Simple, mature service (5 years+) • Well understood, already deployed • Can be used now, without major coordination • Open • We have http://oai.rkbexplorer.com/

37. What Might JISC Do? • Probably clear what I think • Facilitate CRS deployment • Software • Package CRS software • (They funded a co-reference editor as part of dotAC) • Training • Outreach • Take co-reference discovery initiatives • Publish co-reference data in a CRS • Make their data available as Linked Data • Examples are good • Join the data.gov.uk world • Encourage/help other to do the same

38. URIs • http://sameas.org/ • http://jisc.rkbexplorer.com/id/org-77 • http://rkbexplorer.com/ • http://dotac.info/ • http://oai.rkbexplorer.com/ • http://eprints.ecs.soton.ac.uk/18452/