[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:comment-tabpanel&focusedCommentId=59517#comment-59517 ] 

James Amsden commented on OSLCCORE-4:
-------------------------------------

I updated the content above, and provided some motivation for even treating OSLC Discovery as optional. 

> 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)