Code includes OGC schemas

[kalxas]

Linked with #275

[tomkralidis]

https://github.com/geopython/pycsw/tree/master/pycsw/schemas/ogc
https://github.com/geopython/pycsw/tree/master/pycsw/plugins/profiles/apiso/schemas
https://github.com/geopython/pycsw/tree/master/pycsw/plugins/profiles/ebrim/schemas

[kalxas]

There is this note in the code:
https://github.com/geopython/pycsw/blob/master/pycsw/schemas/ogc/README.txt

[kalxas]

Excellent e-mail from Sebastiaan on this issue:
http://lists.osgeo.org/pipermail/standards/2015-February/000842.html

[kalxas]

Also, this issue did not block us to include pycsw to openSUSE, Fedora and UbuntuGIS.

[kalxas]

I think I have reached to a solution:

By carefully reading this document (paragraph 5.10)
http://www.opengeospatial.org/ogc/legalfaq#DTD

"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."

and by taking into consideration these two links:
Document terms: http://www.opengeospatial.org/ogc/document
Software terms: http://www.opengeospatial.org/ogc/software

I think that we just need to add the OGC Software Notice in our schemas folder. This will solve the problem.

I have made a Pull Request to that direction:
#313

[tomkralidis]

+1

[kalxas]

I have edited our Code Provenance wiki page, downgrading the issue to a warning (from a fixme)