1 / 44

Data Access Service Specification: RDF(S ) Ontology Access Draft

Data Access Service Specification: RDF(S ) Ontology Access Draft. Access Services for RDF(S) Data Resources . Miguel Esteban Gutiérrez Ontology Engineering Group Dpto. Inteligencia Artificial Facultad de Informática Universidad Politécnica de Madrid. Outline. Introduction Overview

courtney
Download Presentation

Data Access Service Specification: RDF(S ) Ontology Access Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Access Service Specification: RDF(S) Ontology AccessDraft Access Services for RDF(S) Data Resources Miguel Esteban GutiérrezOntology Engineering Group Dpto. Inteligencia Artificial Facultad de InformáticaUniversidad Politécnica de Madrid

  2. Outline Introduction Overview Current status Outstanding issues Future work Conclusions

  3. Outline • Introduction • Scope • Goals & Objectives • Overview • Current status • Outstanding issues • Future work • Conclusions

  4. IntroductionScope • The WS-DAI-RDF(S) Ontology specification extends the interfaces defined in WS-DAI, to allow access to and provide descriptions of RDF(S) data resources. • RDF(S) data resources are assumed to contain data defined using the RDF(S) model defined in [RDF Concepts, RDF Schema]. • This data is accessed using a set of ontology handling primitives based on the RDF(S) model.

  5. IntroductionGoal & Objectives • Goal: “To provide access to RDF(S) data sources in a grid fashion, without constraining what the user could manually do (specially when serializing a local RDF/XML file), and facilitating common tasks, providing a highly flexibleand adaptable access mechanism that hides technicalities of RDF(S) to the user, whilst transparently exploits its fullsemantics” • Objectives: • Full RDF(S) coverage • R+W capabilities • Granular data access • Resource centric API

  6. Outline • Introduction • Overview • Concepts • Data Resources • Interfaces • Profiles • Current status • Outstanding issues • Future work • Conclusions

  7. OverviewConceptsMerging RDF(S) and WS-DAI Concepts Object Object B B E E Predicate Predicate Object B E F F Predicate s p A A C C A Resource Literal F Subject t . . . . . . . . . C q Subject Subject D D G G r n D M Repository Data Resource RDF Resource Data Resource RepositoryCollection Data Resource

  8. OverviewData ResourcesTypes & Organization Convenience abstractions Class placeholders Class placeholder

  9. OverviewConcepts, revisitedRDF Resource lifecycle • Creation: • Explicit: a triple is created with the resource as subject. • Implicit: a triple is created with the resource as predicate or object. • (Property value) Attachtment: • Explicit: adding a new triple which uses an already existing resource as subject. • Implicit: adding a triple which uses an existing resource as predicate or object, and due to RDF(S) entailment rules, new property values are automatically attached. • (Property value) Detachment: • Explicit: removing a triple which has the resource as subject. • Implicit: removing a triple that has the resource as predicate or object, and as a result inferred property values are lost (no longer explicit). • Removal: • No triples using the resource exist.

  10. OverviewData ResourcesLifecycle example scenario “A”.remove (“C”, “t”, “F”) B B E s p p F t A t F C C q q A r r n . . . t D M A B

  11. OverviewInterfacesOrganization Primitive interfaces Utility interfaces

  12. OverviewInterfacesSummary

  13. OverviewProfiles WS-DAI-RDF(S) Ontology Realization StatementAccess ContainerAccess ContainerFactory ContainerIterator AltAccess ListAccess ListFactory ListIterator Statement Container List Profile 2: Full RDF(S) Support Profile 1: RDF Schema Support ClassAccess PropertyAccess Class Property Profile 0: Basic RDF Support RepositoryCollectionAccess RepositoryCollectionFactory RepositoryAccess RepositoryFactory ResourceAccess RepositoryCollection Repository Resource

  14. Outline • Introduction • Overview • Current status • Profile 0 • Profile 1 • Profile 2 • Outstanding issues • Future work • Conclusions

  15. Current StatusProfile 0

  16. Current StatusProfile 0RepositoryCollectionAccess

  17. Current StatusProfile 0RepositoryCollectionFactory

  18. Current StatusProfile 0RepositoryAccess

  19. Current StatusProfile 0RepositoryFactory

  20. Current StatusProfile 0ResourceAccess

  21. Current StatusProfile 0Summary

  22. Current StatusProfile 1

  23. Current StatusProfile 1RepositoryFactory update

  24. Current StatusProfile 1ClassAccess

  25. Current StatusProfile 1PropertyAccess

  26. Current StatusProfile 0Summary 21 2

  27. Current StatusProfile 1

  28. Current StatusProfile 2RepositoryFactory update

  29. Current StatusProfile 2StatementAccess

  30. Current StatusProfile 2ListAccess

  31. Current StatusProfile 2ListFactory

  32. Current StatusProfile 2ListIteratorAccess

  33. Current StatusProfile 2ContainerAccess

  34. Current StatusProfile 2ContainerFactory

  35. Current StatusProfile 2ContainerIteratorAccess

  36. Current StatusProfile 2AltAccess

  37. Current StatusProfile 2Summary 32 6

  38. Outline Introduction Overview Current status Outstanding issues Future work Conclusions

  39. Outstanding issues • WS-DAI-RDF(S) related: • Not fully aligned with the glossary. • WS-DAI-RDF(S) Ontology specific • List + Container serialization vs. abstract model modification paradox. • RDF(S) data resources lifecycle still obscure in the document. • Missing configurable properties.

  40. Outline Introduction Overview Current status Outstanding issues Future work Conclusions

  41. Future work Update from the paper • Include missing configurable properties. • Make clear the data resources lifecycle: • Introduction. • Messages. • Update the introduction of the document. • Review the terminology used & align it with the glossary.

  42. Outline Introduction Overview Current status Outstanding issues Future work Conclusions

  43. Conclusions • Profile based approach followed to favour community adoption. • Specification almost completed: • Interfaces cleaned • Messages normalized (inputs + outputs + faults) • An stable version to release has been finally reached.

  44. Thanks for your attention, questions? 46

More Related