HistoryViewLinks to this page Revision from: 2012 November 14 | 02:45 pm
This is the revision from 2012 November 14 at 02:45 pmView the current live version of the article.

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

Creative Commons 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
Terminology A glossary of terminology used throughout the specifications. Not started, 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, Lead: SteveSpeicher, John Arwe
Partial update A partial update (HTTP PATCH) model and representation for web resources. Working Draft, 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, 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, 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. Not started, Lead: Arthur?
URL-based Query Model URL-based query syntax and semantics defined in SPARQL SELECT, binding SPARQL endpoint to Containers. Not started, Lead: Arthur?, Anamitra?
Links Rules and guidance around usage of links and statements on links. Not started, Lead: JimConallen?
Updates as needed from previous link guidance
Representation Resource representation guidance on Turtle, JSON and RDF/XML. 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, Lead: TBD Joe Ross?
Error Responses Resource definition (vocabulary) that can be used as the basis for forming an error response. Not started, Lead: SteveSpeicher, MichaelFiedler
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, Lead: TBD Ken P?.
Minimal changes planned
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, Lead: TBD Ken P?.
(minimal changes planned, perhaps add json)
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 Anamitra? NickCrossley?
Compatibility with Core V2 Considerations around V2 compatibility with V2 Not started, Lead: John Arwe
Vocabulary All the terms defined by Core V3 Not started, Lead: SteveSpeicher
Discussion Resource Resource definition for a sequence of comments pertaining to the linked to resource. Not started, Lead: SteveSpeicher, JimConallen.
Since we have a minimal definition from V2, has minimal implementations but no real issues…just republish with improvements

Category:Specifications


Categories