[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-147) Behaviour if a property is specified in oslc.properties that does not exist
[ https://issues.oasis-open.org/browse/OSLCCORE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68532#comment-68532 ] David Honey commented on OSLCCORE-147: -------------------------------------- I've changed the uncomitted spec as per the proposal, reflecting our discussions. Requiring that a query can only reference a property defined in the resource shape might be unnecessarily constraining on open systems that allow arbitrary RDF content without necessarily exposing it in a resource shape. Also, the absence of a resource shape may still mean that an implementation does not know how to query for an arbitrary RDF property. WIth RDF-based persistence and SPARQL, it should not be a problem. But an RDF-based persistence, it's a bit like specifying an undefined table or column name in SQL. You cannot execute the query, and SQL implementations will always report such usage as an error. > Behaviour if a property is specified in oslc.properties that does not exist > --------------------------------------------------------------------------- > > Key: OSLCCORE-147 > URL: https://issues.oasis-open.org/browse/OSLCCORE-147 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Bug > Components: Core, Query > Reporter: David Honey > Assignee: James Amsden > > Neither the OSLC Core 3.0 nor the OSLC Query 2.0 spec define the expected behaviour if a property is specified in oslc.properties that does not exist. -- 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]