OGC XML Schemas and FOSS4G Software Distribution

From OSGeo
Jump to: navigation, search

Background

Blogpost: http://www.how2map.com/2015/02/a-good-test-for-ogc-and-osgeo.html

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

This issue is not new, however was raised in the OSGeo Standards mailing list as a result of the pycsw Incubation process

Problem Statement

FOSS4G software may encounter distribution issues when including OGC Schemas as part of the codebase.

Use of OGC XML Schemas in FOSS4G Implementations

Distribution

Debian

Examples of rejection by Debian:

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.

Current Text

Per http://www.opengeospatial.org/ogc/legalfaq#DTD, paragraph 5.10:

Schemas (and DTDs) are frequently part of our specifications and seemingly fall under
the document copyright terms. However, as long as you do not use the same formal namespace
or public identifier to identify that modified OGC schema/DTD (which might confuse
applications), you may treat the schema/DTD under the software terms. This means that you
are permitted to make a derivative or modified OGC schema/DTD, but even under 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.

Document terms: http://www.opengeospatial.org/ogc/document

Software terms: http://www.opengeospatial.org/ogc/software

Proposed Text

Schemas (and DTDs) are frequently part of our specifications and seemingly fall under the
document copyright terms.

Applications may use the schema/DTD for 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. This has no impact on interoperability
between applications and the resulting schema/DTD remains embedded in the application.

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.