Re: [emergency-comment] CAP-v1.2.xsd: why no global type definitions?

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

Am 12.01.2011 17:29, schrieb Jacob Westfall:
>> 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
>
> CAP elements were designed to only be used in the context of a CAP message and not for individual reuse by other schemas.  I'd recommend against creating an alternate schema for CAP which could lead to potential confusion and instead just create your own elements to satisfy your WPS needs.

My intention is not to create an alternate schema for CAP. I'd rather 
propose that the official cap schema is reorganised. Type definitions 
should be introduced for all non-simple elements such as it is done in 
EDXL-DE or in OGC standards. The new schema would be compatible with the 
current one but allows other schema definitions to import them and 
reusing the types.


I see no drawbacks in re-using cap type definitions in other schemas. In 
contrast this enables a better integration of different systems and 
standards. For example in our early warning system the returned geocodes 
of the WPS are used within the generation process of CAP messages. 
Currently we have to programmatically convert the geocode elements from 
one namespace to another one. If our schema includes the cap schema and 
reuses the cap geocode type defintion this conversion will be unnecessary.



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