Hi,
working on the WCS 2.0 we've made a very sad discovery: the spec writers
decided that
NCName was a good fit for coverage names...
http://books.xmlschemata.org/relaxng/ch19-77215.html
This basically means, we cannot use our usual namespace qualified names as
coverage
names. Now, we either make WCS 2.0 work only inside workspaces, where
prefixes are not necessary or... I'm afraid some sort of euristics will be
required.
The first thing that comes to mind, given that we basically don't have any
reserved char,
is to replace : with _ and then perform first an unqualified lookup,
followed by
a "longest prefix" match when the coverage names come in and we have to
figure
out what coverage is actually being requested
For example, if we have test workspace with raster_rain inside and a
test_raster
workspace with rain inside, test_raster_rain would be matched to the
workspace
with the longest name.
Or we could just adopt any other ordering, like random matching,
alphabetical...
Opinions?
Cheers
Andrea
--
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
