OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[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=61183#comment-61183 ] 

Martin Pain commented on OSLCCORE-44:

Re: Nick,

Yes, your example does demonstrate adding semantics.

I perhaps might modify my assertion/position to be that only shapes that describe a specific RDF type (i.e. that have an oslc:describes property) should be used to add to the semantics. So in your example, it's a shape that is written into the spec as the description of all instances of a given type. Therefore resources do not need to use instanceShape in order to use those semantics, they just need the appropriate rdf:type value.

In other words, I would be uneasy about an instance shape (that doesn't also have an oslc:describes property) adding semantics that can't also be determined (by a human reader) by looking at the rdf:type of that instance and reading the OSLC spec that defines/describes that type. (Or, for non-OSLC types, whatever document defines that type - which may well be a shape with an oslc:describes value).

But this is now getting to be a much more complicated distinction, which I expect we would not all agree on.

Having said that, you could always have two rdf:type values, whose shapes (linked via oslc:describes) give incompatible semantics for properties with the same predicate - which is the same problem that can occur if you have tow oslc:instanceShape values. So I still don't see that allowing for multiple instanceShape values would add any additional problem that we don't already have.

> 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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]