Status: Core 3.0 Draft Specifications
NOTE: Core V3 is targeted to be a collection of compatible specifications endorsed by the Core WG. Active development is occurring on these specification and may change without warning.
This Version
Latest Version
PreviousVersion
Authors
Contributors
Contents
Appendix A: Notices and References
Notation and Conventions
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119. Domain name examples use RFC2606.
Introduction
OSLC Core 3.0 is a collection of specifications that are intended to be independently adopted with minimal interdependencies.
Specifications
| Name |
Description |
Status |
Target SDO |
Notes |
| Terminology |
A glossary of terminology used throughout the specifications. |
Not started |
OASIS |
Lead: SteveSpeicher.
Derived or directly referenced from W3C LDP |
| Resources Definitions and Operations |
Summary of the HTTP and RDF standard techniques and best practices that used, and anti-patterns avoided, when constructing clients and servers that read and write linked data. |
W3C LDP Draft |
W3C |
Lead: SteveSpeicher, John Arwe |
| Partial update |
A partial update (HTTP PATCH) model and representation for web resources. |
Working Draft |
W3C |
Lead: SteveSpeicher |
| Containers |
The resource that allow new resources to be created using HTTP POST and existing resources to be found using HTTP GET. |
W3C LDP Draft |
W3C |
Lead: SteveSpeicher, John Arwe |
| Paging |
A mechanism for splitting the information in large containers into pages whose representation can be requested incrementally. |
W3C LDP Draft |
W3C |
Lead: SteveSpeicher, John Arwe |
| Shapes and Validation |
A mechanism for describing the properties that a particular type of resource must or may have. Semantics defined using SPARQL ASK. Considering also how ‘flipped triples’ are handled. |
Not started |
W3C |
Lead: Arthur?, JohnA, JimC From V2 |
| URL-based Query Model |
URL-based query syntax and semantics defined in SPARQL SELECT, binding SPARQL endpoint to Containers. |
Not started |
OASIS |
Lead: Arthur?, Anamitra? From V2 |
| Links |
Rules and guidance around usage of links and statements on links. |
Working Draft |
OASIS |
Lead: Jim Conallen
Updates as needed from previous link guidance |
| Representation |
Resource representation guidance on Turtle, JSON and RDF/XML. |
Not started |
OASIS |
Lead: SteveSpeicher, MichaelFiedler.
JSON guidance as needed, if not use JSON-LD/RDF. Don’t expect to need this section, need to resolve |
| Authentication and Security |
Requirements and recommendation on authentication models such as OAuth (2.0, 1.0a) and SSO-kind of scenarios. |
Not started |
OASIS |
Lead: TBD Joe Ross? From V2 |
| Error Responses |
Resource definition (vocabulary) that can be used as the basis for forming an error response. |
Not started |
OASIS, W3C |
Lead: SteveSpeicher, MichaelFiedler From V2 |
| Delegated UI DIalogs |
Technique where one provider can embed a creation or selection UI from another server using a combination of an HTML <iframe> and JavaScript code. |
Not started |
OASIS |
Lead: TBD Sam P, Ken P?.
Minimal changes planned From V2 |
| UI Previews |
Technique to show a user in-context information when displaying a link to a resource, and to show more information when the user’s mouse lingers over the link. |
Not started |
OASIS |
Lead: TBD Sam P, Ken P?.
(minimal changes planned, perhaps add json) From V2 |
| Discovery |
how a client can learn about what a server can do and if it is the right kind of server |
Investigating |
OASIS |
Lead: TBD Anamitra? NickCrossley? From V2 |
| Compatibility with Core V2 |
Considerations around V2 compatibility with V2 |
Not started |
OASIS |
Lead: John Arwe |
| Vocabulary |
All the terms defined by Core V3 |
Not started |
OASIS |
Lead: SteveSpeicher From V2 |
| Discussion Resource |
Resource definition for a sequence of comments pertaining to the linked to resource. |
Not started |
OASIS |
Lead: SteveSpeicher, JimConallen.
Since we have a minimal definition from V2, has minimal implementations but no real issues…just republish with improvements From V2 |
Appendix A: Notices and References
Contributors
- SteveSpeicher (IBM, OSLC-Core Lead)
- John Arwe (IBM, OSLC-Core)
- Arthur Ryman (IBM, OSLC-Core)
- Nick Crossley (IBM, OSLC-Core)
- Ian Green (IBM, OSLC-Core)
- Michael Fiedler (IBM, OSLC-Core)
- Samuel Padgett (IBM, OSLC-Core)
- Paul McMahan (IBM, OSLC-Core)
Reporting Issues on the Specification
The working group participants who author and maintain this working draft specification, monitor a distribution list where issues or questions can be raised, see Core Mailing List
Also the issues found with this specification and their resolution can be found at Core 2.0 Issues.
License and Intellectual Property
We make this specification available under the terms and conditions set forth in the site Terms of Use, IP Policy, and the Workgroup Participation Agreement for this Workgroup.
References
Category:Specifications
Category:Specifications 3.0
