CAP-v1.2.xsd: why no global type definitions?

[Matthias Lendholt <matthias.lendholt@gfz-potsdam.de>]

Dear all,

in our tsunami early warning system we are using standards from OGC and 
from OASIS. One of our WPS (Web Processing Service) is responsible for 
calculating affected areas out of simulation results. The list of 
identified administrative units could be represented by a list of 
geocodes (such as ISO-3166 or NUTS). Because we are already using CAP 
and its geocode elements I intended to reuse the cap:geocode element in 
my WPS interface definition. Unfortunately all CAP-*.xsd files available 
online have no global type definitions. Instead all elements are defined 
locally. This makes it impossible to reuse them. Of course I can 
generate my own type definition but for type safety I prefer to import 
the cap xsd and explicitly reuse the geocode element (or others).

If there are no objections I propose to refactor the xsd by defining 
global types. But maybe there are certain reasons not to have them?


Best regards,
Matthias Lendholt

-- 
[matthias.lendholt@gfz-potsdam.de]
GFZ German Research Centre for Geosciences
CeGIT Centre for GeoInformation Technology
Tel +49 331 288-1687; FAX +49 331 288-1703
Telegrafenberg A20, 14473 Potsdam, Germany
Blog http://zeigertelegraph.gfz-potsdam.de
Contact MECARD QR Code: http://goo.gl/488J