Re: [emergency-msg] Signing and Encryption of contentObject

[Art Botterell <acb@incident.com>]

Would it be cruelty to a dead horse to suggest that we spell out what  
we're trying to accomplish and how in the Data Dictionary before we  
try to implement it in the Schema?

Seems like we've been going in circles on this particular point since  
last spring, and I can't help but suspect that having both the Schema  
and the Data Dictionary under revision in parallel has had something  
to do with that.

When last I checked, we had a proposal from Renato which he thought  
might address everyone's concerns, but Dave had some reservations.   
Did we settle that?  If not, seems like we need to get to an  
architectural decision one way or the other, document it in the spec,  
and then edit the Schema to implement it.

I'm totally on board regarding the need to move quickly... I just  
think we'll get done faster if we do things in order.

- Art


On Dec 26, 2005, at 12/26/05 3:56 PM, Rex Brooks wrote:

> I think these are oversights, and should be put back into the spec,  
> especially as this is the "any" element and optional as well. But,  
> necessary, as Dave explains.
>
> Regards,
> Rex
>
> At 1:58 PM -0700 12/26/05, Ellis, David wrote:
>> All
>>
>> I have been in a series of meetings the last two weeks and the  
>> requirement to sign and encrypt EDXL contentObject is now  
>> critical. In the last TC telecom meeting I was surprised to find  
>> the ability to add an optional namespace attribute to  
>> contentObject and the optional signature element had been removed  
>> in the series of updates/revisions to the EDXL Distribution  
>> Element Schema.  We need to return these as originally outlined in  
>> the Schema proposed last May.
>>
>> In meeting DNDO and USNORTHCOM, the proposal to expose and encypt  
>> embeddedXMLContent on an element by element basis will not meet  
>> operational security requirements.
>>
>> Also, We need to add "<xsd:any namespace="##any"  
>> processContents="lax" minOccurs="0" maxOccurs="unbounded" />" to  
>> the sequence defined in "contentObjectType" to allow for signing.   
>> The current structure of embeddedXMLContent allows the encryption  
>> elements to be included already.  I have attached a revised Schema  
>> with signing element included for your consideration.
>>
>> There is a need to get the Distribution Element out as a Standard  
>> as soon as possible.
>>
>> David E. Ellis
>> Information Management Architect
>> (505) 844-6697
>>
>>
>> Content-Type: application/octet-stream;
>>  name=edxl-de.xsd
>> Content-Description: edxl-de.xsd
>> Content-Disposition: attachment;
>>  filename=edxl-de.xsd
>>
>> Attachment converted: Macintosh HD:edxl-de.xsd (    /    ) (000CD96E)
>> ---------------------------------------------------------------------
>> 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
>
>
> -- 
> Rex Brooks
> President, CEO
> Starbourne Communications Design
> GeoAddress: 1361-A Addison
> Berkeley, CA 94702
> Tel: 510-849-2309
>
> ---------------------------------------------------------------------
> 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