OGC XML Schemas and FOSS4G Software Distribution - Revision history

Tomkralidis at 01:34, 17 February 2015

2015-02-17T01:34:18Z

Tomkralidis at 01:18, 17 February 2015

2015-02-17T01:18:48Z

Wiki-Sebastic: Link to Debian post in standards@ thread

2015-02-16T22:27:14Z

Link to Debian post in standards@ thread

Jive: /* Proposed Text */

2015-02-16T21:59:59Z

Proposed Text

Jive: /* Proposed Text */

2015-02-16T21:57:17Z

Proposed Text

Tomkralidis at 20:12, 16 February 2015

2015-02-16T20:12:29Z

Tomkralidis at 20:06, 16 February 2015

2015-02-16T20:06:54Z

Tomkralidis at 20:00, 16 February 2015

2015-02-16T20:00:20Z

Tomkralidis at 19:55, 16 February 2015

2015-02-16T19:55:46Z

Tomkralidis: Created page with "=Background= Discussion on OSGeo-Standards mailing list: http://osgeo-org.1560.x6.nabble.com/OGC-XML-schemas-and-FOSS4G-software-distribution-td5186023.html =Current Text= =Pr..."

2015-02-16T19:44:43Z

Created page with "=Background= Discussion on OSGeo-Standards mailing list: http://osgeo-org.1560.x6.nabble.com/OGC-XML-schemas-and-FOSS4G-software-distribution-td5186023.html =Current Text= =Pr..."

New page

=Background=

Discussion on OSGeo-Standards mailing list: http://osgeo-org.1560.x6.nabble.com/OGC-XML-schemas-and-FOSS4G-software-distribution-td5186023.html

=Current Text=

=Proposed Text=

← Older revision		Revision as of 01:34, 17 February 2015
Line 66:		Line 66:
	further appreciate a couple sentences regarding who made the modifications, when, and what		further appreciate a couple sentences regarding who made the modifications, when, and what
	changes were made in the original DTD -- a common software documentation practice.</pre>		changes were made in the original DTD -- a common software documentation practice.</pre>
		+
		+	[[Category:Standards]]

@@ Line 27: / Line 27: @@
 * TinyOWS: http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-January/017321.html
-For clearification of the problems the Debian project has with the OGC Document & Software Notice terms see:
+For clarification of the problems the Debian project has with the OGC Document & Software Notice terms see:
 http://lists.osgeo.org/pipermail/standards/2015-February/000842.html and the links referred to in that message.
@@ Line 44: / Line 44: @@
 Document terms: http://www.opengeospatial.org/ogc/document
 Software terms: http://www.opengeospatial.org/ogc/software

@@ Line 26: / Line 26: @@
 * pycsw: http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-November/024520.html
 * TinyOWS: http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-January/017321.html
 =Current Text=

@@ Line 48: / Line 48: @@
 document copyright terms.
-Applications may use the schema/DTD for internal validation under the software license. We ask
+Applications may use the schema/DTD for under the software license. We ask that care be taken
-that care be taken when making a derivative or modified schema/DTD to preserve interoperability.
+when making a derivative or modified schema/DTD to preserve interoperability.
 As an example a schema/DTD used for internal validation may be modified to validate additional
-optional vendor options without affecting interoperability.
+optional vendor options without affecting interoperability. This has no impact on interoperability
 If publishing a modified schema/DTD it no longer qualifies as an OGC schema/DTD and we ask

← Older revision		Revision as of 21:57, 16 February 2015
Line 45:		Line 45:
	=Proposed Text=		=Proposed Text=

−	<pre>~~TBD~~</pre>	+	<pre>Schemas (and DTDs) are frequently part of our specifications and seemingly fall under the
		+	document copyright terms.
		+
		+	Applications may use the schema/DTD for internal validation under the software license. We ask
		+	that care be taken when making a derivative or modified schema/DTD to preserve interoperability.
		+
		+	As an example a schema/DTD used for internal validation may be modified to validate additional
		+	optional vendor options without affecting interoperability.
		+
		+	If publishing a modified schema/DTD it no longer qualifies as an OGC schema/DTD and we ask
		+	that a unique formal namespace or public identifier be used to prevent application confusion.
		+	This request is based on the restrictions of XML technology rather than a license restriction.
		+
		+	When using the software terms you are obligated to include/retain the OGC copyright notice. We
		+	further appreciate a couple sentences regarding who made the modifications, when, and what
		+	changes were made in the original DTD -- a common software documentation practice.</pre>

@@ Line 9: / Line 9: @@
 ==Problem Statement==
-FOSS4G software may encounter distribution issues when including OGC Schemas as part of the codebase.
+FOSS4G software may encounter distribution issues when including [http://schemas.opengis.net OGC Schemas] as part of the codebase.
 ==Use of OGC XML Schemas in FOSS4G Implementations==
@@ Line 27: / Line 27: @@
 * TinyOWS: http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2014-January/017321.html
-=Current Text=
+Per http://www.opengeospatial.org/ogc/legalfaq#DTD, paragraph 5.10:
 =Proposed Text=

@@ Line 1: / Line 1: @@
 =Background=
 Discussion on OSGeo-Standards mailing list: http://osgeo-org.1560.x6.nabble.com/OGC-XML-schemas-and-FOSS4G-software-distribution-td5186023.html
 ==Problem Statement==
@@ Line 12: / Line 16: @@
 ** XML responses cite <code>xsi:schemaLocation</code> of pointing to locally cached OGC schemas
 *** e.g. <code>xsi:schemaLocation="http://www.opengis.net/cat/csw/2.0.2 http://HOST/csw/2.0.2/CSW-discovery.xsd"></code>
-* used to validate XML based HTTP requests
+* used within software to perform XML schema validity of XML based HTTP requests
 =Current Text=
 =Proposed Text=