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

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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


Subject: Re: [office] Digital Signature proposal


Jomar,

Jomar Silva wrote:
> I just would like to remember that an application that support XAdES 
> will also support XMLDsig (XAdES is an extension of it).
> 
> I also believe that an application that support only XMLDsig, will be 
> (or may be) able to validate just the XMLDsig portion of the XAdES 
> signature.

Both is my understanding as well.

When looking at your proposal: Is the <dsig:signature-type> element 
really required, or could an application guess that a signature is a 
XAdes signature by analyzing the content of the signature's <object> 
element?

If the <dsig:signature-type> element is not required, is it them 
required to list XAdes in the specification? Or can we simply say ODF 
supports XML DSig. XAdes signatures are an extension of XML DSig. ODF 
therefore automatically supports XAdes signatures.

Michael
> 
> There are diagrams here (http://www.w3.org/TR/XAdES/) that demonstrate 
> the differences between XMLDsig and XAdES.
> 
> Best,
> 
> Jomar
> 
> Dave Pawson escreveu:
>> 2008/7/31 Ming Fei Jia <jiamingf@cn.ibm.com>:
>>   
>>> Thanks explanation although that can not convince me completely. You said
>>> "...if the application developer choose to only support XMLDsig, it will
>>> still being compliant with ODF 1.2...". Is that true? XMLDsig and XAdES are
>>> as different options in the proposal. If the application only implements
>>> XMLDsig, could the application claim to be compliant with ODF standard? I
>>> think at most it can claim partial compliant. This is the conformance issue.
>>>
>>> Another is the interoperability issue. Assume one application only
>>> implements XMLDsig, another application only implements XAdES. How does the
>>> first application validate the signed document with XAdES format generated
>>> by the second application? Seems no way,even both the two applications claim
>>> to be compliant with the same ODF standard.
>>>     
>>
>>
>> A conformance issue for ODF?
>> Seems the TC has to choose one or the other if interoperability is
>> to work for signed documents.
>>
>>
>> regards
>>
>>
>>
>>
>>
>>
>>   
> 


-- 
Michael Brauer, Technical Architect Software Engineering
StarOffice/OpenOffice.org
Sun Microsystems GmbH             Nagelsweg 55
D-20097 Hamburg, Germany          michael.brauer@sun.com
http://sun.com/staroffice         +49 40 23646 500
http://blogs.sun.com/GullFOSS

Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1,
	   D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering


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