[OASIS Issue Tracker] (OSLCCORE-4) Clarify the meaning of multi-part OSLC Core 3.0 specification re: conformance

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Amsden updated OSLCCORE-4:
--------------------------------

    Proposal: 
I added this paragraph at the end of section 5. OSLC Core 3.0:

These documents comprise the multi-part specification for OSLC Core 3.0. They represent common capabilities that servers MAY provide and that may be discovered and used by clients. Although OSLC Core could be useful on its own, it is intended to specify capabilities that are common across many domains. Servers will generally specify conformance with specific domain specifications, and those domain specifications will describe what parts of OSLC Core are required for conformance. This allows servers to implement the capabilities they need in a standard way without the burden of implementing capabilities that are not required. The OSLC Core Discovery capability may allow clients to determine what capabilities are provided by a server. Any provided capability MUST meet all the conformance criteria for that capability as defined in the OSLC Core 3.0 specifications.

This implies that any capability that is discoverable is essentially optional, and once discovered, the capability is provided as defined in the applicable OSLC specifications. OSLC Discovery itself is also an optional capability as servers could provide other means of informing specific clients of supported OSLC capabilities that could be utilized directly. For example, a server might provide only preview dialogs on specific resources and nothing else.

  was:
I added this paragraph at the end of section 5. OSLC Core 3.0:

These documents comprise the multi-part specification for OSLC Core 3.0. They represent common capabilities that servers MAY provide and that may be discovered and used by clients. Although OSLC Core could be useful on its own, it is intended to specify capabilities that are common across many domains. Servers will generally specifiy conformance with specific domain specifications, and those domain specificaitons will describe what parts of OSLC Core are required for conformance. This allows servers to implement the capabilities they need in a standard without the burden of implementing capabilities that are not required. OSLC Core Discovery may allow clients to determine what capabilities are provided. Any provided capability MUST meet all the conformacne criteria for that capabilitiy as defined in the OSLC Core 3.0 specifications.


> Clarify the meaning of multi-part OSLC Core 3.0 specification re: conformance
> -----------------------------------------------------------------------------
>
>                 Key: OSLCCORE-4
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-4
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: James Amsden
>            Assignee: James Amsden
>            Priority: Minor
>
> It was not clear exactly what OSLC Core is. Is it:
> 1. All of the specifications - any compliant server would be expected to implement all of the capabilities (including those referenced from LDP).
> 2. Any of the specifications - a compliant server could advertise only one of the core capabilities, e.g., Resource Preview.
> The OSLC Core Overview specification should clarify that compliance to OSLC core means with respect to the component specifications.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)