> Tom, > I know we have discussed putting an id inside a <Layer> in an > OWS Context document before and to date I think that we have > decided not to mandate it? >
It's not in the current schema, from what I can see. > My question now is, > Is it ok to optionally allow an id in layers in an OWS > Context document? > Inserting an id makes it much easier to write transactions on > the Context. This would probably be best in AbstractResourceType. Having said this, I haven't heard much on our current schema and whether it's being used in OWS5 at all w.r.t. KML integration. ..Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
