Cameron, the schema repository you reference, http:// www.ogcnetwork.net/schemas/, is open for developers to use, subject to the OGC Network administrators' (me!) approval. OGC Network was created exactly for this reason, so developers like you could have a way to publicize your "alpha" OGC-related work without implying that it represents the opinion of OGC. I think a page on OGC Network along with some schema is what you're looking for. If you want publishing permissions on the site let me know.
--- Raj On Oct 20, 2007, at 5:15 PM, Carl Reed OGC Account wrote: > I will be out of the office for two weeks. However, as the proposal > is a good one, I would suggest working with Raj, Greg, and Mark > Reichardt to make this happen. > > Also, FYI, as soon as we get out from under all the changes to > documents and the web site for the new OGC IPR policy, we will be > standing up a public OGC Change Request Proposal system whereby > anyone can submit change requests and track their progress. > > Regards > > Carl > > ----- Original Message ----- From: "Cameron Shorter" > <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; "Kralidis,Tom [Burlington]" > <[EMAIL PROTECTED]> > Cc: <[email protected]>; "openlayers" > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Saturday, October 20, 2007 2:03 PM > Subject: [OSGeo-Standards] OSGeo access to OWS Context specs > > >> OSGeo Standards, >> >> Mapbuilder stores state information inside an OWS Context >> document, and consequently we may be the largests tester of OWS >> Context. >> >> Every few months we have debates over various parts of the OWS >> Context spec as developers implement new things. The latest is a >> discussion shared with Openlayers over how Layer groups should be >> handled. >> >> The current OWS Context spec/schema is globally available at: >> * http://www.ogcnetwork.net/schemas/owc/0.2.0/ >> >> A wiki list of identified issues is at: >> * https://portal.opengeospatial.org/wiki/twiki/bin/view/CGDIPilot/ >> CgdiipOwsContext >> Unfortunately, this is only available to OGC members. My next >> email will be to lobby to make it visible. >> >> >> As part of OGC's mass market strategy, can we please open up >> access to the OWS Context issue list. This should ensure that >> specs would benefit from greater testing and increase adoption. >> >> An alternative I've considered is setting up an issue tracker as >> part of Mapbuilder to address OWS Context. (I'd prefer an issue >> tracker over a wiki as it is easier to manage issues through to >> completion). >> >> -- >> Cameron Shorter >> Systems Architect, http://lisasoft.com.au >> Tel: +61 (0)2 8570 5050 >> Mob: +61 (0)419 142 254 >> >> _______________________________________________ >> Standards mailing list >> [EMAIL PROTECTED] >> http://lists.osgeo.org/mailman/listinfo/standards > > _______________________________________________ > Standards mailing list > [EMAIL PROTECTED] > http://lists.osgeo.org/mailman/listinfo/standards ------------------------------------------------------------------------- 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
