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
License
This work is licensed under a Creative Commons Attribution License.
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 |
| Resources Definitions and Operations |
a summary of the HTTP and RDF standard techniques and best practices that you should use, and anti-patterns you should avoid, when constructing clients and servers that read and write linked data |
W3C LDP Draft, Lead: SteveSpeicher |
| Partial update |
define a SPARQL Update subset as a HTTP PATCH format |
Working Draft, Lead: SteveSpeicher |
| Containers |
defines resources that allow new resources to be created using HTTP POST and existing resources to be found using HTTP GET |
W3C LDP Draft, Lead: SteveSpeicher |
| Paging |
defines a mechanism for splitting the information in large containers into pages that can be fetched incrementally |
W3C LDP Draft, Lead: SteveSpeicher |
| Shapes and Validation |
defines a mechanism for describing the properties that a particular type of resource must or may have. Semantics defined using SPARQL ASK |
Lead: Arthur? |
| Simple Query |
a simple URL-based query syntax and semantics defined in SPARQL SELECT, binding SPARQL endpoint to Containers |
Not started, Lead: Arthur? |
| Links |
updates as needed from previous link guidance |
Not started, Lead: TBD |
| Representation |
JSON guidance as needed, if not use JSON-LD/RDF. - Lead: SteveSpeicher, MichaelFiedler |
|
| Authentication and Security |
stronger requirements on OAuth (2.0, 1.0a) and guidance to help with SSO-kind of scenarios |
Not started, Lead: TBD |
| Error Responses |
updates as needed |
Not started, Lead: TBD |
| Delegated UI DIalogs |
support a few additional use cases |
Not started (minimal changes planned), Lead: TBD |
| UI Previews |
leverage JSON format, updates as needed |
Not started (minimal changes planned, perhaps add json), Lead: TBD |
| Discovery |
how a client can learn about what a server can do and if it is the right kind of server |
Investigating approaches, Lead: TBD |
| Compatibility with Core V2 |
Considerations around V2 compatibility with V2 |
Not started, Lead: TBD |
| Vocabulary |
All the terms defined by Core V3 |
Not started, Lead: SteveSpeicher |
Category:Specifications
