oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Proposed OSLC Core Conformance section
- From: "Jim Amsden" <jamsden@us.ibm.com>
- To: OASIS (oslc-core@lists.oasis-open.org) <oslc-core@lists.oasis-open.org>
- Date: Thu, 21 Jun 2018 15:32:32 -0400
This is what I propose to add to the OSLC
Core Overview specification in order to address the missing Conformance
section:
6. Conformance
OSLC Core defines a set of HTTP REST
services for a set of capabilities that facilitate flexible, loosely coupled
tool integration. These services may be augmented by varous OSLC domain
specifications that specify the capabilities, vocabularies and constraints
that define specific resources managed by these integration capabilities.
OSLC Servers mustimplement standard HTTP protocals and mustat least support GETrequests that respond with resources in some RDF serialization format.
OSLC Servers mustimplement all the mandatory requirements in the normative sections of specification,
and shouldfollow all the guidelines and recommendations in these specifications.
OSLC Servers mayimplement any of the capabilities described in this specification, and
if a capability is supported, all of the mandatory requirements specified
in the normative sections of the multi-part specification elaborating the
capability mustbe implemented.
OSLC Servers mustimplement the OSLC Core vocabulary as defined in OSLC
Core Version 3.0. Part 7: Vocabulary.
Part
2 of this document defines
the mandatory requirements for the OSLC discovery capability. OSLC Servers
shouldprovide the discovery capability in order for clients to determine what
services are supported by the server and how to access them. OSLC Servers
that implement discovery mustimplement all of the mandatory requirements specified in the normative
sections of part 2 of this multi-part specification.
Part
3 of this document defines
the mandatory requirements for the OSLC resource preview capability. OSLC
Servers that implement resource preview mustimplement all of the mandatory requirements specified in the normative
sections of part 3 of this multi-part specification.
Part
4 of this document defines
the mandatory requirements for the OSLC delegated creation and selection
dialog capability. OSLC Servers that implement delegated dialogs mustimplement all of the mandatory requirements specified in the normative
sections of part 4 of this multi-part specification.
Part
5 of this document defines
the mandatory requirements for the OSLC attachents capability. OSLC Servers
that implement attachments mustimplement all of the mandatory requirements specified in the normative
sections of part 5 of this multi-part specification.
Part
6 of this document defines
the mandatory requirements for the OSLC resource shape constraints capability.
OSLC Servers shouldsupport resource shapes in order to describe OSLC server managed resources,
and validate creation and update requests. OSLC Servers that implement
resources shapes mustimplement all of the mandatory requirements specified in the normative
sections of part 6 of this multi-part specification.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]