Issue List for SWS 1.0

Issue ID

Summary

Description

Priority

Justification

Resolution

farrukh-1

XCQL: Do we need it

See here

P3

Adds significant complexity

farrukh-2

Encode operation in URL not URL option

See here

P2

Makes HTTP interface more RESTFul

farrukh-3

Define standard mechanism for returning non-XML records

See here

P2

Enables client to extract non-XML records in response in a standard manner. Note that ATOM format will allow links to non-XML content

farrukh-4

Need to support parameterized query invocation model

See here

P1

Provides a more more general, flexible and extensible.query invocation model that better meets the needs of spec such as ebXML RegRep, OGC Catalog, OGC Web Registry Service etc. A possible solution is described in the Parameterized Query discussion document wich has no formal standing.

farrukh-5

Server should never be asked to maintain client state

See here

P3

Violates "Statelessness" principal of REST.

farrukh-6

Use ATOM 1.0 as default canonical responseFormat

See here

P1

supports feed, more RESTful, allows links to non-XML records (solution to farrukh-3), supports related links, supports metadata such as author, created, updated, title, supports extensiblity to handle custom needs of our spec, Reduces our spec content. An example of what this may look like is described in section 4.2.1 of the Parameterized Query discussion document wich has no formal standing.

levan-1

Support multiple query types

See here

P1

We need to support multiple query types. This was an issue for MXG. Parameterized Query is clearly an example of a new query type that we should not be forcing into CQL

ray-1

Eliminate Scan Operation

See here andhere

P1

Scan can be modeled within the Search/Retrieve operation

ray-2

Eliminate Version Parameter (encode it in base URL)

See here

P1

See farrukh-2

memberid-NN

See [ here]

P1-P3