[OASIS Issue Tracker] (OSLCCORE-147) Behaviour if a property is specified in oslc.properties that does not exist

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Honey updated OSLCCORE-147:
---------------------------------

    Proposal: 
The spec should be updated to say:

If oslc.where> specifies a property that has an defined namespace prefix, but the property is not known, for 		example not defined in the resource shape for that type of resource, an implementation MAY do either of:

1) Respond with a 400 Bad Request/code. This is appropriate for implementations that have finite and enumerable properties of resources that cannot determine how to query for undefined properties.

2) Execute the query and return a normal query response. This is appropriate for implementations that have open sets of properties, not all of which might be in a resource shape.

  was:
The spec should be updated to say that the response MAY be either of:



> 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)