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] Groups - Draft Meeting Notes 12-27-2005.docuploaded


The schema I sent for inclusion to the EDXL-DE is not the one which was
included in the document.  I am glad people are reviewing the document
but do not know why the change we discussed and I inputted where not
included in the standard and a new signature element was created.

David E. Ellis
Information Management Architect
(505) 844-6697

-----Original Message-----
From: Renato Iannella [mailto:renato@nicta.com.au] 
Sent: Sunday, January 08, 2006 9:25 PM
To: Emergency_Mgt_TC TC
Subject: Re: [emergency] Groups - Draft Meeting Notes 12-27-2005.doc

The meeting notes say:

"The key change is that the ANY element has been put back in. With 

the addition of the choice statement, signatures will no longer 

automatically work. The ANY element will be required at the end of a 

sequence in order to sign a content object."

I could not see the "ANY" element in the new XSD released - can 

someone explain it purpose?

I also do not understand where it says that "signatures will no 

longer automatically work"
How is this? and what does it mean by "automatically"?

(NOTE: my impression is that XML Signatures can apply to any XML 

construct and that there is no
need for a "signature" element - as you will get one of these from 

XML Signature anyway)

The meeting notes say:

"Renato's issue is the only one remaining"

I assume you are referring to the issue of having BOTH keyXMLContent 

and embeddedXMLContent elements?

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

This email and any attachments may be confidential. They may contain
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
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or
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

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