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-47) Cardinality of properties (oslc:occurs)

    [ https://issues.oasis-open.org/browse/OSLCCORE-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61248#comment-61248 ] 

James Amsden commented on OSLCCORE-47:

ResourceShapes should be considered constraints on a resource representation for a specific purpose in a specific context. This purpose or context could be closed-world. But the resources upon which these representations are derived, or other representations of the same resources for other purposes may or may not be subject to the same or different constraints.

For OSLC, the ResourceShapes describe the constraints on resource representations exchanged between conformant tools using the OSLC REST services (or protocol). These constraints say nothing about the underlying mechanisms that are the sources of these representations, and therefore should not make any statement about whether inferencing is one of those mechanisms, or an RDF knowledge base for that matter. If a server does utilize a triple store, allows assertions to be stated or inferred that may not be compliant with the OSLC ResourceShapes, then it would seem to be that server's responsibility to determine how to construct a resource representation from its data sources that is compliant if that data is accessed through OSLC.

Regarding ResourceShapes (or W3C SHACL), it is probably unknown how these constraints should be interpreted when inferencing is involved. The SHACL working group should take this up.

> Cardinality of properties (oslc:occurs)
> ---------------------------------------
>                 Key: OSLCCORE-47
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-47
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Nick Crossley
>            Assignee: James Amsden
>            Priority: Minor
> The oslc:occurs value in a property definition indicates the cardinality of that property. It is not clear if that includes inferred triples, and no guidance is provided about whether clients should assume resources follow the cardinality constraint.
> Where inference is being used, and where shapes or properties include rdfs:subClassOf, rdfs:subPropertyOf, or owl:sameAs, a resource may have inferred triples that do not follow the cardinality rules for a shape, even though the explicitly provided triples do follow those rules. Should the OSLC specification provide any guidance in such cases?

This message was sent by Atlassian JIRA

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