[OASIS Issue Tracker] (OSLCCORE-106) Example might not work on many implementations

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

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

David Honey commented on OSLCCORE-106:
--------------------------------------

I have removed examples using nested properties relating to foaf and replaced with with a simpler use of foaf:name. The current draft spec now uses examples that I tried with real RTC work item OSLC queries but where I have:
1) Changed the hostname to "host".
2) Show a query result container that is an ldp:BasicContainer, only uses ldp:contains. The section on query containers states that all examples assume that a query capability resource shape is defined that declares ldp:contains as oslc:isMemberProperty "true"^^xsd:boolean.

So I think we can close this issue.

> Example might not work on many implementations
> ----------------------------------------------
>
>                 Key: OSLCCORE-106
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-106
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>          Components: Query
>            Reporter: David Honey
>            Assignee: James Amsden
>
> https://open-services.net/bin/view/Main/OSLCCoreSpecQuery has this example of a nested oslc.where:
> http://example.com/bugs?oslc.where=dcterms:creator{foaf:givenName="John"; and foaf:familyName="Smith"}
> However, many implementations might only support foaf:name.
> Should we change this example (see below) so it might be more widely supported?
> http://example.com/bugs?oslc.where=dcterms:creator{foaf:name="John Smith"}



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)