Hi colleagues,
I finally managed to build the mapping lists of XML & JSON
name of elements that were really used within the spec. See the
generated document attached.
Some JSON names map to multiple XML names. This can be
perfectly valid (e.g. 'msg' -> 'ResultMessage' and
'Message'). I updated the shady cases listed below:
di: changed to 'dis' to map to DigestInfos
result: changed to 'results'
to map to VerifyManifestResults
signedRef:
changed
to 'results' to
map to VerifyManifestResult
value:
all JSON names should follow the same style.
Renamed to 'val'
IDREF:
changed to 'idref'
ID:
problems with JAXB framework. Changing the
JSON name to 'id' breaks the reference
mechanism. Not changed.
val:
the lowercase 'value' was introduced to
circumvent the 'mixed' attribute of the
'ds:TransformType'. The lowercase name was
introduced for technically introduced
elements. Does this provide any
clarification for the user or is it just
irritating?
The
XML to JSON mapping is one-to-one, no
problems to fix here
Greetings,
Andreas
--
Andreas Kühne
phone: +49 177 293 24 97
mailto: kuehne@trustable.de
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
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php