52north/common-xml

A set of commonly used OGC schemas compiled to xmlbeans bindings

common-xml's Issues

Change group id of 52n-xml-wps-v20 module

Currently the group id is org.n52.wps. This should be changed to org.n52.sensorweb for consistency reasons.

Add Travis build job

The build runs really long, but maybe it can still be useful to have it run on Travis?

Update README

From version 2.0.0 the artifacts are available from Maven Central ... no extra repository to add

Adjust versioning of OGC schema module

OGC uses only two digit versioning and overrides the schema files available for one version (e.g. 2.0) if there is a corrigendum to it (e.g. 2.0.1). This is a pity as one cannot "see" which schema/corrigendum version is compiled actually and packaged as Java artifact.

Using semantic versioning, we should reflect such changes to the version of the commons-xml project. However, this includes manual checks triggered by an RSS notification of several ReadMe.txt files and---perhaps sometimes---guessing if the API will break or not. If others have a better solution to this, I'd be very interested!

Anyway, at least the OGC module should be versioned by the datum when the schemas were downloaded to trace the history of the project.

Add license to pom.xml and repository

We should add a license to the pom, in the best case we should publish this under two licenses: GPL v2 and Apache 2.0.

@simonjirka FYI

Redeclare package names for GML

GML versions before 3.2 did not include the version in its target namespace. This results in identical package names and type clashes. A simple xsdconfig file would help out here so that e.g. gml version 3.1.1 would end up with package names net.opengis.gml.x311. Not backward compatible, though.

Restructure artifacts

Currently all artifacts are under the org.n52.sensorweb groupId. However, as the xml schemas are not all directly related to Sensor Web, we should think about moving and in parallel restructuring the modules so that they meet issue #4 as well. This includes an agreement how to version the artifacts (see issue #4 for details) and how to track changes.

Update to XmlBeans 4

XmlBeans 4.0.0 was released and requires a recompilation of all schemas with the new version

Create new Release with WPS 2.0 schema bindings included

Since PR #10 WPS 2.0 schema bindings are included ... there should be a new release to be made and deployed on both 52n repository and maven central.