Behaviour if neither oslc.where nor oslc.searchTerms are specified

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: Query
    • None
    • Hide

      Modify the draft OSLC Query 3.0 specification to explicitly state that if neither oslc.where nor oslc.searchTerms is specified that a server MAY either return a successful response where the query result container references all artifacts of the RDF type associated with the query capability, or respond with a 400 Bad Request.

      Should the MAY be even stronger and be a MUST instead?

      Show
      Modify the draft OSLC Query 3.0 specification to explicitly state that if neither oslc.where nor oslc.searchTerms is specified that a server MAY either return a successful response where the query result container references all artifacts of the RDF type associated with the query capability, or respond with a 400 Bad Request. Should the MAY be even stronger and be a MUST instead?

      Currently, the OSLC Query 3.0 draft specification does not define the behaviour of OSLC Query when neither oslc.where nor oslc.searchTerms is specified. We should provide more guidance on this.

      Some implementations might want to return all artifacts of the RDF type associated with the query capability. However, when the number of artifacts is very large, and especially when a server does not support paging, such a request could overwhelm a server, or the resultant large response might overwhelm the requesting client.

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

              Created:
              Updated: