See:
http://www.opengeospatial.org/blog/1597
-----Original Message-----
From: [...] On Behalf Of Kevin Stegemoller
Sent: Thursday, 21 June 2012 14:09
Subject: 11-025 and XLink transition changes for gml/*
Hello,
My apologies for the X-posting.
The XLink beta transition and 11-025 changes are complete. Additional
changes were made. Please test the beta schemas [1] available in zip [2].
1. http://beta.schemas.opengis.net/
2. http://beta.schemas.opengis.net/BETA.SCHEMAS.OPENGIS.NET.zip
The Changes:
* v2.0.0 - v3.2.1 WARNING XLink change is NOT BACKWARD COMPATIBLE.
* changed OGC XLink (xlink:simpleLink) to W3C XLink (xlink:simpleAttrs)
per an approved TC and PC motion during the Dec. 2011 Brussels meeting.
see http://www.opengeospatial.org/blog/1597
* implement 11-025: retroactively require/add all leaf documents of an
XML namespace shall explicitly <include/> the all-components schema
* v3.3: no changes
* v3.2.1: added gml.xsd as the all-components document (06-135r11 #14)
* v3.2.1: updated xsd:schema:@version to 3.2.1.2 (06-135r7 s#13.4)
* v3.1.1: updated xsd:schema:@version to 3.1.1.2 (06-135r7 s#13.4)
* v3.1.1: added gml.xsd as the all-components document (06-135r11 #14)
* v3.1.0: ignored
* v3.0.1: ignored
* v3.0.0: ignored
* v2.1.2.x: gml/2.1.2.x schema were removed and archived
* v2.1.2.0: removed gml/2.1.2.0 and now redirected to 2.1.2
* v2.1.2.2: removed gml/2.1.2.1 and now redirected to 2.1.2
* v2.1.2: added gml.xsd as the all-components document (06-135r11 #14)
* v2.1.2: updated xsd:schema:@version to 2.1.2.2 (06-135r7 s#13.4)
* v2.1.1: updated xsd:schema:@version to 2.1.1.1 (06-135r7 s#13.4)
* v2.0.0: updated xsd:schema:@version to 2.0.7.1 (06-135r7 s#13.4)
There remain outstanding questions and your help is appreciated.
* Any reason against including an all-components document for gml/3.3?
Otherwise I will include one.
* With these XLink changes, should OGC continue to use our copy of ISO
schema or some other copy?
gml/3.2.1/coordinateOperations.xsd
<import namespace="http://www.isotc211.org/2005/gmd"
schemaLocation="http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd"/>
* gml/3.0.0 and others use non-standard W3C SMIL2
Please test and let us know _now_ if these changes cause any unexpected
problems. These changes will go live 21 July 2012 so it is critical for
any issues to be handled now.
Regards,
kevin
OGC 11-025 Summary
All 'leaf' documents describing part of an XML namespace shall
explicitly <include> the 'all-components' schema document. In
this way use of any schema document will automatically result in
all-components being imported.
--
-------------------------------------------------------
Kevin Stegemoller <kstegemoller@anonymised.com>
The OGC: Making location count.
http://www.opengeospatial.org/contact
-------------------------------------------------------
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
On Thu, Jun 21, 2012 at 8:27 AM, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:
See:
http://www.opengeospatial.org/blog/1597
I’d say, we do the change on the new trunk, once we have it, and when we have the funding to do so.
I’m not going to waste my Sundays on OGC decisions to break their existing standards.
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
+1.
On 21/06/12 14:54, Andrea Aime wrote:
I'd say, we do the change on the new trunk, once we have it, and when we
have the funding to do so.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Just to chime in that outside of app-schema (who actually needs xlink) i don’t see this as been too far reaching. The latest versions of the cite tests which we now run against requires the new xlink schemas and we didn’t have to change anything for them.
So I think outside of app-schema all that has to change is that we update the schemas in the geotools xsd modules and then the ones we ship inside of geoserver as well.
Ben, what other tasks do you forsee?
On Thu, Jun 21, 2012 at 12:57 AM, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:
+1.
On 21/06/12 14:54, Andrea Aime wrote:
I’d say, we do the change on the new trunk, once we have it, and when we
have the funding to do so.
–
Ben Caradoc-Davies Ben.Caradoc-Davies@anonymised.com
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
I think that is about it.
Even for app-schema, we might just have to update test dependencies (like rebuilding all the schema-bundle jar artifacts). It might be more of an impact for GeoServer app-schema users, who will have to purge their schema caches and catalogs or risk validation inconsistencies.
I think the biggest task will be user education; I might put a notice in the app-schema manual about the change, to explain that yes, there are two versions of GML 3.1.1, and two versions of GML 3.2.1.
app-schema validation unit tests will check that everything is good.
On 22/06/12 03:32, Justin Deoliveira wrote:
Just to chime in that outside of app-schema (who actually needs xlink) i
don't see this as been too far reaching. The latest versions of the cite
tests which we now run against requires the new xlink schemas and we
didn't have to change anything for them.
So I think outside of app-schema all that has to change is that we
update the schemas in the geotools xsd modules and then the ones we ship
inside of geoserver as well.
Ben, what other tasks do you forsee?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre