OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [emergency] RE: Question on EDXL-DE schema



Here are the definitions for the valid values of the namespace attribute:


##any – This is the default setting for the namespace attribute which implies that elements from any namespace are allowed to exist in the placeholder specified by the ‘any’ element.


##other – Specifying this value for the namespace attribute allows elements from any namespace except the namespace of the parent element (i.e., not the ‘targetNamespace’ of the parent).


##local – The substituted elements must come from no namespace.


##targetNamespace – Only elements from the namespace of the parent element can be contained.



Here are the definitions for the valid values of the ‘processContents’ attribute:


Strict – This is the default value in the absence of any ‘processContents’ attribute.  The XML processor must have access to the schema for the namespaces of the substituted elements and fully validate those elements against that schema.


Lax – This is similar to strict, with the exception that if no schema can be located for substituted elements, then the XML parser simply checks for well-formed XML.


Skip – This is the least taxing validation method, which instructs the XML processor not to validate any elements from the specified namespaces.



The ##other is an acceptable replacement for the ##any value located in the any element following the xsd:choice element.  The intent of this element in the EDXL-DE schema is to provide a mechanism for signing our contentObjects.  The signing process (refer to http://www.w3.org/TR/xmldsig-core/) uses a different namespace than EDXL-DE.


Additionally, the use of the xsd:any element allows us to attach location information to sensor contentObjects, which we are currently testing.  For EDXL-SS (Sensor System, which is similar to EDXL-RM), we will need to make the location information part of the EDXL-DE header to allow for the distribution of the EDXL messages to the appropriate recipient(s).  We may have to explore making this a different namespace or adding additional specific contentObjects elements in EDXL-DE 1.1 for message delivery to subscribers in the proper area of their responsibility.




David E. Ellis

Information Management Architect

(505) 844-6697


From: Ham, Gary A [mailto:hamg@BATTELLE.ORG]
Sent: Thursday, January 19, 2006 10:08 AM
To: Aymond, Patti; Mark Carlson - Conneva, Inc.
Cc: Emergency_Mgt_TC TC
Subject: RE: [emergency] RE: Question on EDXL-DE schema


Folks. I have the same issues using Architag X-Ray I get the error "Schema is non-deterministic."  Changing from namespace="##any"  to namespace="##local"  Validates.  So does namespace="##other" which is what was used for <anyXMLType> further along in the schema. For the experts out there: What is the technical difference between namespace="##any" , namespace="##local" , and namespace="##other" ??






Gary A. Ham

Senior Research Scientist

Battelle Memorial Institute

540-288-5611 (office)

703-869-6241 (cell)

"You would be surprised what you can accomplish when you do not care who gets the credit." - Harry S. Truman



From: Aymond, Patti [mailto:Patti.Aymond@iem.com]
Sent: Thursday, January 19, 2006 11:18 AM
To: Mark Carlson - Conneva, Inc.
Cc: Emergency_Mgt_TC TC
Subject: [emergency] RE: Question on EDXL-DE schema



I am no schema expert, but I did not have any problems getting the EDXL-DE to validate in tools that I have (XML Spy is not one of them). Maybe someone on the TC can offer some suggestions for you.


Welcome to the TC.




Patti Iles Aymond, PhD
Senior Scientist
Bioterrorism Preparedness & Response

Innovative Emergency Management, Inc.

Managing Risk in a Complex World

8555 United Plaza Blvd.   Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)

From: Mark Carlson - Conneva, Inc. [mailto:conneva@gmail.com]
Sent: Friday, January 13, 2006 10:34 AM
To: Aymond, Patti
Subject: Question on EDXL-DE schema




I'm a new TC member and am taking my first look at the various documents and schemas.  When I open version 7 of the EDXL-DE schema in XML Spy, I receive an error stating that


The content model contains the elements <element name="nonXMLContent"> and <any namespace="any##"> which can not be uniquely determined.


When I remove the "<any namespace="any##"> or change it to <any namespace="local##"> the schema validates successfully. 


I understand that this change was introduced recently to support XML signatures.  Do I have something setup incorrectly in XML Spy or is there something else we need to do to the schema to make it valid.


Mark Carlson

Conneva, Inc.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]