> I think very definitely the answer to that one would be "no." What
> else?
I'm in agreement with this. However it means the accepted definition of an XML profile, which usually results in a new namespace, does not apply, and that's why a good profile definition is needed. So following this course of action, to start, some criteria to help define a CAP profile. Just spit-balling here, please remove/change/add to this list.
Some things a profile "cannot" do are:
- establish a new namespace
- add, make changes, or create subsets of the base CAP schema, its elements, and enumerated/defined values
- extend a CAP message, in the conventional XML sense, through the use of namespaced schemas
--
--
