Re: [ubl-security] Reminder: UBL-XAdES profile evolving towards anOASIS standard and XAdES plugtest approaching and

[Juan Carlos Cruellas <cruellas@ac.upc.edu>]

Hi Jon,

I guess that I was making incorrect assumptions on how the XAdES profile 
would be integrated within the UBL framework and would be progressed in 
the standardization track. Sorry for any missunderstanding this may have 
caused. I see your point in integrating it within the general framework 
and make it to progress with the rest of the package...which does not 
invalidate the assertion that the XAdES plugtest would be a perfect 
occassion for using the specifications.

Regards

Juan Carlos.
El 28/09/2010 16:32, Jon Bosak escribió:
> Hello Juan Carlos,
>
> I will leave responses to the technical aspects to others, but
> regarding this:
>
>> Finally, I would like to raise an additional issue: the rules
>> for approving a document as an OASIS Standard require "three
>> Statements of Use". I would say that the participation in the
>> would be the perfect occassion for actually making use of such
>> specification in generating UBL signed documents, and get them
>> verified....
>
> We haven't discussed whether to break out XAdES as a separate
> deliverable, but insofar as the mechanism is part of UBL 2.1, it
> simply shares the progress of 2.1 as a Standard (including the use
> statements). Given the time it takes to get anything through
> OASIS Standardization, this is a good reason to consider the XAdES
> profile part of 2.1. I was assuming that the Security SC
> document (which now needs considerable revision) would be included
> as part of PRD2.
>
> If there are political reasons to break out the UBL XAdES profile
> as a separate standard, we will have to consider them, but it will
> make the task quite a bit more difficult, so I am hoping we don't
> have to do that!
>
> Jon