Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Talis Platform: A Linked Data Engine

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 46 Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Anzeige

Ähnlich wie Talis Platform: A Linked Data Engine (20)

Weitere von Leigh Dodds (20)

Anzeige

Aktuellste (20)

Talis Platform: A Linked Data Engine

  1. 1. The Talis Platform A Linked Data Engine Leigh Dodds Platform Programme Manager SemTech June 2010 http://creativecommons.org/licenses/by/2.0/uk/
  2. 2. Agenda <ul><li>Platform Overview </li></ul><ul><li>Managing RDF in the Platform </li></ul><ul><li>Data Extraction Features </li></ul><ul><li>Current & Recent Projects </li></ul>
  3. 4. Platform Overview
  4. 5. Multi-Tenant Data Storage Service Software as a Service
  5. 6. Self-contained data stores with services that operate on their contents Platform Stores
  6. 7. Store any binary content Unstructured Data Storage
  7. 8. RDF triple store Structured Data Storage
  8. 9. Stores are world-readable by default Configurable access options HTTP Digest Authentication Access Control
  9. 10. Trigger or schedule store management jobs Reset, Snapshot, Restore, Reindex (Future feature: Bulk Load) Job Control
  10. 11. Generic services that operate on any kind of data Aim for design consistency via service checklist RESTful APIs
  11. 12. RDF, SPARQL, HTTP Where there are no standards we create open specifications Standards Compliance
  12. 13. Branded Linked Data Hosting Domain hosting Surfacing of platform services
  13. 14. The Meta Box Managing structured metadata
  14. 15. Create, read, update, delete RDF resources Web-accessible RDF triplestore
  15. 16. Public/Private application data Separate access control options Future Feature: API for managing graphs Partition data into sub-graphs
  16. 17. Support RDF/XML, Turtle, N-Triples Store data with HTTP POST
  17. 18. Vocabulary and protocol for describing changes to RDF triple stores Updates using Changesets
  18. 19. Maintain audit trail of changes to Metabox Support for Versioned Updates
  19. 20. Combine several changesets into single request Applied atomically Batch Update Mechanism
  20. 21. Searching SPARQL Augmentation Data Extraction Features
  21. 22. Full-text index over RDF literals in the Metabox Configurable indexing options Every Store has a Search Index
  22. 23. Paging, Sorting, Relevance Ranking Flexible query syntax (fielded and boolean searches) Standard Search Engine features
  23. 24. /items?query=[query] &max=[10] &offset=[0] &sort=[comma-separated fieldnames] &xsl=[XSLT stylesheet] &content-type=[mimetype for XSLT results]
  24. 25. Includes Open Search extensions: paging, relevance ranking Includes full description of each RDF resource Search Results are RSS 1.0
  25. 26. Group search results by specific fields Simple XML response format Facetted Search
  26. 27. /services/facet ?query=[query] &fields=[comma-separated fieldnames] &top=[10] &format=[xml|html]
  27. 28. Automatic data annotation Pipe an RSS 1.0 feed through a Store and enrich it with available data Augmentation
  28. 29. RSS 1.0 RSS 1.0 Augmenter MetaBox
  29. 30. /services/augment ?data-uri=[url-of-RSS-feed] &xsl=[XSLT stylesheet] &content-type=[mimetype for XSLT results]
  30. 31. Standards compliant SPARQL 1.0 service Early access to draft SPARQL 1.1 features SPARQL Query API
  31. 32. /services/sparql ?query=[query] &output=[syntax (xml, rdf, json)]
  32. 33. Current Projects Quick tour of current & recent projects
  33. 34. Crawling and hosting Linked Data from bbc.co.uk Public SPARQL Endpoint BBC
  34. 35. Community annotation of Linked Data using Twitter Based on BBC Linked Data fanhu.bz
  35. 36. Linked Data from UK Government Domain hosting Public SPARQL and Search APIs data.gov.uk
  36. 37. Explore UK research project funding http://bis.clients.talis.com BIS Research Explorer
  37. 38. Linked Data UK Geography and Gazetteer Domain hosting Public SPARQL and Search APIs Ordnance Survey
  38. 39. Linked Data from EU Government and UK cultural heritage UK & EU Research Projects
  39. 40. Free use of the Platform for Public Domain data http://www.talis.com/cc Talis Connected Commons
  40. 41. Help explore potential of Linked Data Developer workshops, training, data conversions Your Organisation?
  41. 42. Summing Up Summary, Additional Resources
  42. 43. The Talis Platform provides… <ul><li>Cloud based data storage </li></ul><ul><li>Simple API for managing data </li></ul><ul><li>Flexible data extraction features </li></ul><ul><li>Linked Data publishing platform </li></ul>
  43. 44. Additional Resources <ul><li>API Reference </li></ul><ul><li>http://n2.talis.com/wiki/Platform_API </li></ul><ul><li>Mailing List </li></ul><ul><li>http://groups.google.com/group/n2-dev </li></ul><ul><li>Blog </li></ul><ul><li>http://blogs.talis.com/n2/ </li></ul><ul><li>Support Desk </li></ul><ul><li>http://talisplatform.zendesk.com </li></ul>

Hinweis der Redaktion

  • Multiple users Zero install SaaS model: instant access to features We worry about the data management, but leave you in control All new (versions) Talis applications now built on same Platform, e.g. Engage. So can not only build new apps on the service, can also access data underlying existing services
  • i.e. similar to Amazon S3. Can upload and store any kinds of data. May be web site assets, e.g. images, CSS, javascript, etc. May be other documents or collateral.
  • i.e. similar to Amazon S3. Can upload and store any kinds of data. May be web site assets, e.g. images, CSS, javascript, etc. May be other documents or collateral.
  • Main set of features are around the structured data storage. Management of RDF metadata. Resource Description Framework More later but basically a means to capture in a highly structured and flexible way, metadata about anything.
  • As you remain in control of your data, you obviously want to control who has access to it. By default on the platform we allow public read access, but this can be changed. Each store can has its own set of access control options, i.e. which platform users can access which features. There are a useful set of defaults, i.e. public read, admin to add, update or modify configuration
  • Roy Fielding’s thesis, responsible for many of the Internet RFCs. Describes a formal basis for the web architecture. Growing agreement that following these architectural principles is the best way to build internet-scale applications, whether that means web sites or web APIs. Anything else means you’re working against the web architecture meaning that you’re using a sub-optimal solution. This is why the Talis Platform follows these principles rather than using, say, SOAP or some other web services APIs. REST, essentially, involves using HTTP correctly. About understanding and using the HTTP protocol to its fullest extent, because in doing so you allow web browsers, proxy servers, search engines, etc to all interact with you application correctly and in a way that has massive scalability.
  • And al of this is made available through a standards compliant framework. With essentially one exception (which I’ll point out later) everything that we’ll look at is based on open internet standards. The technologies like HTTP, RDF, SPARQL, all of the data formats we generate are open standards. This is part of the Talis ethos. We don’t believe in proprietary software. We use and create a lot of open source software ourselves and believe this is the only viable way for internet services to develop.
  • As well as following the REST architectural guidelines, within the Platform team we have our own set of best practices that apply to the design of new services. The service checklist is online as part of the API documentation, but includes things like ensuring we have a consistent url structure, that there’s a human interface to every API, to make it easy to play with the system. That error messages are human-readable, etc
  • E.g. public data, but also private authentication data.
  • E.g. public data, but also private authentication data.
  • E.g. public data, but also private authentication data.
  • Want to review some basic concepts and technologies that underpin the design and implementation of the Platform. How many people already understand the terms REST, Content Negotation, RDF.
  • E.g. public data, but also private authentication data.

×