Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Incomplete
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: geometry, main, xsd extensions
-
Labels:None
Description
We have both some text parsing (CQL and WKT) and XML parsing (filter, gml) incoming. This proposal outlines how we can be consistent in terms of package structure.
- CQL - Catalogue Query Language - currently an unsupported module
- XML - Extensible Markup Language - we are forced to run our own parser due to scaling issues
- WKT - Well Known Text - we already support CRS definition, we need one for Parsing Geometry
For details please see the wiki:
Discussion welcome.
Activity
Gabriel Roldan
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | core xml [ 11176 ] | |
| Component/s | ext xml-xsd [ 13122 ] |
Jody Garnett
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Incomplete [ 4 ] |
Jody Garnett
made changes -
| Component/s | core filter [ 11601 ] |
+1 on the xml packing naming structure. One question though is how to do versions. Shall the version number just be tacked onto the end. Examples being:
org.geotools.xml.filter.v1_0
org.geotools.xml.filter.v1_1
org.geotools.xml.gml.v2
org.geotools.xml.gml.v3
Or shall the version be incorporated in one level up like:
org.geotools.xml.filter1_0
org.geotools.xml.filter1_1
org.geotools.xml.gml2
org.geotools.xml.gml3