[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [oslc-domains] Reconciling 2.0 domain specification base requirements with OSLC Core 3.0
CM 3.0 Requirement | Level | Meaning | AM 2.0 Differences |
Unknown properties and content | may/ must | OSLC servers mayignore unknown content and OSLC clients mustpreserve unknown content | Client MUST is in a separate entry. |
Resource Operations | must | OSLC service mustsupport resource operations via standard HTTP operations | |
Resource Paging | may | OSLC servers mayprovide paging for resources but only when specifically requested by client | Paging is SHOULD for query results, MAY on large resource entity response bodies. |
Partial Resource Representations | must | OSLC servers mustsupport request for a subset of a resource’s properties via the oslc.properties URL parameter retrieval via HTTP GET | AM is MAY support selective properties |
Partial Update | may | OSLC servers maysupport partial update of resources using [LDPPatch], or via HTTP PUT. | |
Discovery | may/ should | OSLC servers shouldprovide a ServiceProvider resource for Core v2 compatibility, mayprovide a ServiceProviderCatalog, and mayprovide other forms of discovery described in Core 3.0 Discovery. | Specifically states MUST provide ServiceProvider resource. Servers MAY support ServiceProviderCatalog |
Creation Factories | must | OSLC servers mustprovide LDPC creation factories to enable resource creation of Change Management resources via HTTP POST | Creation factory capability is MAY, and also servers MAY support creation factories in other resource serialization formats indicated with oslc:usage. |
Query Capabilities | should | OSLC servers shouldprovide query capabilities to enable clients to query for resources | query capability is a MUST |
Query Syntax | should/ may | OSLC query capabilities shouldsupport the OSLC Core Query Syntax and mayuse other query syntax | |
Delegated UI Dialogs | must/ should | OSLC Services mustoffer delegated UI dialogs (creation and selections) specified via OSLC Core 3.0 Delegated Dialogs and shouldinclude discovery through a ServiceProvider resource for OSLC v2 compatibility | Delegated selection UI is SHOULD, delegated creation dialog is separate entry and MAY. |
UI Preview | should | OSLC Services shouldoffer UI previews for resources that may be referenced by other resources specified via OSLC Core 3.0 Preview and shouldinclude discovery through a server resource for OSLC v2 compatibility | |
Authentication | may | OSLC Services shouldfollow the recommendations for Authentication specified in [OSLCCore3] | SHOULD support one of the OSLC Core recommendations, Has separate MAY for each one (HTTP Basic, OAuth, Form) |
Error Responses | should | OSLC Services shouldprovide error responses using OSLC Core 3.0 defined error formats | |
Turtle Representations | must | OSLC servers mustprovide a Turtle representation for HTTP GET requests and shouldsupport Turtle representations on POST and PUT requests. | |
RDF/XML Representations | should | OSLC servers shouldprovide an RDF/XML representation for HTTP GET requests and shouldsupport RDF/XML representations on POST and PUT requests for compatibility with Change Management 2.0. | RDF/XML is MUST |
XML Representations | should | OSLC servers shouldprovide a XML representation for HTTP GET, POST and PUT requests that conform to the Core 2.0 Guidelines for XML. | |
JSON Representations | must | OSLC servers mustprovide JSON-LD representations for HTTP GET, POST and PUT requests that conform to the Core Guidelines for JSON-LD | |
HTML Representations | should | OSLC servers shouldprovide HTML representations for HTTP GET requests |
Other Differences:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]