Object elements for XAdES

[John Haug]

So, recommend making the same explicit allowance in OPC as in MS-OFFCRYPTO for placing a Reference element that specifies a digest of a SignedProperties element inside a Manifest element inside an Object element which has id=”idXAdESReferenceObject”, as specified at the very end of 2.5.2.6 in MS-OFFCRYPTO?

Since at least MS Office and possibly others currently do this when using XAdES, it seems a good idea for compatibility.

John

From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: Thursday, January 15, 2015 5:12 AM
To: SC34
Subject: Re: Object elements for XAdES

Miyachi-san (an attendee of the Kyoto meeting) agrees
with me.  We do not have to mention
<Object id="idOfficeObject"> but we should
allow <Object id="idXAdESReferenceObject"> as
a XAdES reference Object element.

Regards,
Makoto

2014-12-26 11:09 GMT+09:00 MURATA Makoto <eb2m-mrt at asahi-net.or.jp<mailto:eb2m-mrt at asahi-net.or.jp>>:
Dear colleagues,

ISO/IEC 29500-2 distinguishes Object elements having
Id="idPackageObject"and those not having it.  The former is a
package-specific Object element (see 12.3.5.14) while the latter is an
application-defined Object element (see 12.3.5.15).

OFF-CRYPTO introduces two other values of Object/@Id.  They are
"idOfficeObject" and "idXAdESReferenceObject". It appears that
"idOfficeObject" are used as containers of SignatureInfoV1, which we
is not going to be introduced to OPC.

Thus, it reamins to introduce "idXAdESReferenceObject" as XAdeES
reference Object in the revision of Part 2.  Am I correct?

Regards.
Makoto



--

Praying for the victims of the Japan Tohoku earthquake

Makoto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20150115/2c370ff8/attachment-0001.html>