Re: [dss-x] Schema-Changes [was 'Anpassungen am VerificationReport-Schema']

Sorry,

mixed up two mail drafts and nagged you with a german subject ...

In addition see the simplified / adapted core and XAdES schema attached.
They are tailored to build a nice Object modell (using the JAXB
compiler) what in turn defines the JSON structure. The corresponding
JSON schemes are attached, too. A sparse JSON signing request looks
quite promising to me:

{
  "InputDocuments" : {
    "Document" : [ {
      "Base64Data" : {
        "value" : "PD94bWwgdmVyc2lv ... 6Um9vdD4=",
        "MimeType" : "application/xml"
      }
    } ]
  },
  "RequestID" : "TestIdSignXML--5776074688433983709"
}

What's your opinion? Is it a valid approach?

Greetings,

Andreas

> Hi all,
>
>
> I came across some glitches in the core and profile schemas. In the core
> spec there is the element 'UseVerificationTime' defined but no type
> given. This would give an 'any' as the default type. Due to section
> '4.5.2 Optional Input <UseVerificationTime>' and as the schema suggests
> it should have the type 'UseVerificationTimeType':
>
>    <xs:element
> name="UseVerificationTime"type="dss:UseVerificationTimeType"/>
>
>     <xs:complexType name="UseVerificationTimeType">
>         <xs:choice>
>             <xs:element name="CurrentTime" type="xs:dateTime"/>
>             <xs:element name="SpecificTime" type="xs:dateTime"/>
>             <xs:any namespace="##other"/>
>         </xs:choice>
>     </xs:complexType>
>
> The UseVerificationTimeType itself contains the "CurrentTime" element
> without a type, too. The core document doesn't explain it any further.
> In analogy to the 'SpecificTime' element the type 'xs:dateTime' should fit.
>
>   
>
> The XAdES schema uses two elements in an indicator style way (present or
> absent). That may cause problems with JAXB so I would propose to define
> a type of 'xs:boolean' for the use of JSON schema derivation:
>
> SignaturePolicyImplied and AllSignedDataObjects
>
>     <xsd:complexType name="SignaturePolicyIdentifierType">
>         <xsd:choice>
>             <xsd:element name="SignaturePolicyId"
> type="SignaturePolicyIdType" />
>             <xsd:element name="SignaturePolicyImplied" type="xs:boolean"/>
>         </xsd:choice>
>     </xsd:complexType>
>
>
>     <xsd:complexType name="CommitmentTypeIndicationType">
>         <xsd:sequence>
>             <xsd:element name="CommitmentTypeId"
> type="ObjectIdentifierType" />
>             <xsd:choice>
>                 <xsd:element name="ObjectReference" type="xsd:anyURI"
> maxOccurs="unbounded" />
>                 <xsd:element name="AllSignedDataObjects" type="xs:boolean"/>
>             </xsd:choice>
>             <xsd:element name="CommitmentTypeQualifiers"
> type="CommitmentTypeQualifiersListType" minOccurs="0" />
>         </xsd:sequence>
>     </xsd:complexType>
>


-- 
Andreas Kühne 
phone: +49 177 293 24 97 
mailto: 

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612

Director Andreas Kühne

Company UK Company No: 5218868 Registered in England and Wales