Every WMS layer and WFS feature type has a qualified name, that is, a name that has both an XML namespace and a local part. This allows local names to be used for different purposes in different namespaces.
The GeoServer workspace name is the XML namespace prefix and the URI is the XML namespace used for all feature types and layers inside the workspace. For example, the "topp" workspace defines a XML namespace "http://www.openplans.org/topp"; with XML namespace prefix "topp" (same as the workspace name). The "states" feature type inside this workspace is referred to as "topp:states". If you are not required to use a particular namespace, then you are free to use any namespace URI, but you should choose one that will not change because of factors outside your control: You could use an HTTP URI: http://example.org/test/myexample An HTTP URI does not need to resolve to anything, but it could. You could put some useful information on a server at this URL. Some of the XML standard namespaces do this. You could also use a URN: urn:x-test:MyExample In either case, clients using your service may discover the qualified names of your layers and feature types by making a GetCapabilities WMS or WFS request. They will then use the qualified name to make requests. Kind regards, Ben. On 03/03/11 00:44, Mustafa646 wrote: > > when we create new workspace, we have to put the name of the workspace and > the URI. I want to know which URI should I provide ? Also can anybody > explain me why the work space "topp" have this URI: > > http://www.openplans.org/topp. > > can i use this URI as well ? > > What is the purpose of this URI ? -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
