Behaviour if a property is specified in oslc.select that does not exist

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: Core
    • None
    • Hide

      The spec should be updated to say that the non-existent property MUST be ignored rather than return an error response.

      Show
      The spec should be updated to say that the non-existent property MUST be ignored rather than return an error response.

      The OSLC Query 2.0 spec did not define the expected behaviour if a property is specified in oslc.select that does not exist.

            Assignee:
            James Amsden (Inactive)
            Reporter:
            davidhoney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: