[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-4) Clarify the meaning of multi-part OSLC Core 3.0 specification re: conformance
[ https://issues.oasis-open.org/browse/OSLCCORE-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59497#comment-59497 ] Nick Crossley commented on OSLCCORE-4: -------------------------------------- I think this part is too weak: "OSLC Core Discovery may allow clients to determine what capabilities are provided." I think we need to design Core Discovery so that it does allow such determination, to at least the SHOULD level if not MUST. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]