[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-44) oslc:instanceShape should explicitly allow multiple values
[ https://issues.oasis-open.org/browse/OSLCCORE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61153#comment-61153 ] David Honey commented on OSLCCORE-44: ------------------------------------- Looking at Core 2.0, it seems that for a service, a creation factory supports zero-or-many for oslc:resourceShape, but zero-or-one for a query capability. That seems inconsistent to me. The "Creating an OSLC Defined Resource" section says:"A client can learn what properties are allowed in a new OSLC Defined Resource via the OSLC specification that defines or, in some cases via a Resource Shape resource.". This implies zero-or-one. I suspect we have existing implementations that assume a resource can only have one oslc:resourceShape. I can see advantages of allowing multiple shapes. Some of the shape may be static and can be shared across multiple instances of resources. A resource that operates in multiple domains can reference multiple standard shapes. In that way, the dynamic content only needs to provide a delta. However, multiple shapes may pose compatibility issues with existing clients consuming OSLC 2.0. > oslc:instanceShape should explicitly allow multiple values > ---------------------------------------------------------- > > Key: OSLCCORE-44 > URL: https://issues.oasis-open.org/browse/OSLCCORE-44 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Bug > Reporter: Martin Pain > Assignee: James Amsden > > With a quick look on both Core 2.0 and the W3C member submission for Resource Shapes, it looks like neither mention whether a client can expect zero-or-one or zero-or-many instanceShape links from a resource. > I would expect zero-or-many. As I can't see any problem with an instance having the properties from multiple shapes. This would help with the question about vendor-specific shapes raised on OSLCCORE-25 - as then the resources can include a link to both the vendor-specific shape and the OSLC TC-minted-URI for the a shape as defined in the spec. > In v3.0 I think we should clarify this to state that a resource can specify zero or more instance shapes. (If we don't already & I missed it). -- 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]