[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-110) oslc.where syntax differs from Lyo reference implementation
[ https://issues.oasis-open.org/browse/OSLCCORE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68080#comment-68080 ] James Amsden commented on OSLCCORE-110: --------------------------------------- That would seem quite useful, but we should check to see what is implemented by current products and/or make it a MAY. > oslc.where syntax differs from Lyo reference implementation > ----------------------------------------------------------- > > Key: OSLCCORE-110 > URL: https://issues.oasis-open.org/browse/OSLCCORE-110 > 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 description of the syntax of oslc.where only supports: > value ::= uri_ref_esc | literal_value > uri_ref_esc ::= /* an angle bracket-delimited URI reference in which > and \ are \-escaped. */ > However, when I plaigerised the Antlr definition of this from Lyo, I found it also accepted prefixed names. For example, the following was supported: > oslc.where=dcterms:creator=jtsuser:John > providing that the prefix jtsuser was defined. This seems useful, so should we adopt that in the spec? -- 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]