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] Signatures etc


All,

This may be actually be the reason some of our schema validators are not
liking the <any> tag.  It actually is "non-deterministic".  If we change
it to namespace="##other" Renato's example would not validate properly
since the extra "stuff" is in the originating namespace. 

R/s


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

-----Original Message-----
From: Aymond, Patti [mailto:Patti.Aymond@iem.com] 
Sent: Thursday, January 19, 2006 12:40 PM
To: Renato Iannella; David Ellis; Emergency_Mgt_TC TC
Cc: Nelson, Brian Dale; Babb, Charles
Subject: RE: [emergency] Signatures etc

Well, this is a bad thing. I'm going to play around with this some. Does
anyone have suggestions to work around this problem?

Patti

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)

-----Original Message-----
From: Renato Iannella [mailto:renato@nicta.com.au]
Sent: Monday, January 16, 2006 9:39 PM
To: David Ellis; Emergency_Mgt_TC TC
Cc: Nelson, Brian Dale; Babb, Charles
Subject: Re: [emergency] Signatures etc


First of all, there seems to be an error in the current document as  
it defines an element called
"any" (on page 26) but the XML Schema has an element called  
<signature> (page 32).
I am assuming the correct version is the (placeholder) "any" element.

Second, when I say you cannot "truly validate" the contentObject, it  
is because with the "any"
element, I can include EDXL:

<contentObject>
     <contentDescription> ....
     <incidentID>....
     <confidentitality>....
     <xmlContent>....
     <incidentID>....
     <confidentitality>....

As you can see the last two elements are repeated - but they are  
technically *valid*
because the "any" element allows this.


Cheers...  Renato Iannella
National ICT Australia (NICTA)



------------------------------------------------------------------------
--
This email and any attachments may be confidential. They may contain
legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete
both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or
unauthorised
amendment. This notice should not be removed.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
http://www.ieminc.com/e_mail_confidentiality_notice.html


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



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