Hello, I use Openlayers in my proyect, but I don't use INSPIER, so for me
2) *add the extra INSPIRE items to the default WMS* building blocks of OpenLayers provided they don't break anything I*s an extra overload in files* that I don't want. Some people can think the same thing. So, the third option: 3) *create INSPIRE classes* which extend the default building blocks and include them in OpenLayers *I think is the best option* as if I don't want them, I can extract them in my final openlayers compressed javascript file. 2009/12/9 Bart van den Eijnden <bart...@osgis.nl> > Hi list, > > as some of you may know, currently Europe is very active with INSPIRE, an > SDI based on OGC standards, but with a few differences here and there > compared to the standard OGC specification. > > For example, a View Service (=WMS) has an extra parameter LANGUAGE for all > requests to deal with internationalization. Also, there is an extra section > in the GetCapabilities response for the language support. > > What would be the best way to deal with this in OpenLayers: > > 1) keep INSPIRE outside of OpenLayers > 2) add the extra INSPIRE items to the default WMS building blocks of > OpenLayers provided they don't break anything > 3) create INSPIRE classes which extend the default building blocks and > include them in OpenLayers > > I would be interested to hear opinions on this. > > An example GetCapabilities document is: > > http://dev.openlayers.org/sandbox/bartvde/inspire/openlayers/examples/xml/inspire_capabilities_1_3_0.xml > > http://dev.openlayers.org/sandbox/bartvde/inspire/openlayers/examples/xml/inspire_capabilities_1_3_0.xsd > > Best regards, > Bart > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev >
_______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
