29 lines
1.3 KiB
Plaintext
29 lines
1.3 KiB
Plaintext
|
---+ Current Open Issues
|
||
|
|
|
||
|
|
The list of open issues being discussed right now. There are plenty of more things to discuss, but these are the ones being worked on right now.
|
||
|
|
|
||
|
|
|
||
|
|
1 FilterEncoding. How do we represent filters in the protocol?
|
||
|
|
* see discussion about FilterOperators
|
||
|
|
* add SpatialOperators to work with coordinates?
|
||
|
|
|
||
|
|
* ProtocolHeader. Do we need to address resources in the protocol? What is an AccessPoint?
|
||
|
|
|
||
|
|
* RequestMethods. What kind of requests are needed?
|
||
|
|
* PingRequest: do a simple 'ping' to see whether a resource is online.
|
||
|
|
* CapabilitiesRequest: list capabilities of the respective (provider)software...
|
||
|
|
* MetadataRequest: give human readable metadata about a provider/resource
|
||
|
|
* SearchRequest: search is subtyped?
|
||
|
|
* InventoryRequest: select distinct values or value arrays...
|
||
|
|
* CountRequest: count is a seperate request or just a flag?
|
||
|
|
|
||
|
|
* ConceptualBinding. How do we address a concept of a ConceptualSchema?
|
||
|
|
|
||
|
|
* ResponseStructure: How to define the structure of the returned records?
|
||
|
|
|
||
|
|
* RecordDefinition: Do we need to define a "record" for a concetpual schema? Do we need a 'root' table?
|
||
|
|
|
||
|
|
* ErrorCodes: Do we need to define a standard set of error codes?
|
||
|
|
|
||
|
|
* An alternative ThirdProposal based on the SoapProtocol ?
|