Issue raised concerning 2.1 schema maintenance change to use attributeFormDefault of "unqualified"

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

http://lists.oasis-open.org/archives/ebxml-cppa/200603/msg00004.html

 

Samples in the ebCPPA spefication version 2.0 that show elements from

the Digital Signature namespace have prefixes for the attributes. XML

Schema validating [1] a CPA that is signed and has attributes of the

digital signature namespace being prefixed fails. The Digital Signature

XML Schema does not include a "attributeFormDefault" attribute which

implies that the attributes must not be prefixed. So we think all the

samples in the CPA that show ds:Reference elements etc are not valid.

wrong:

<ds:Reference ds:URI="abc"> ...</ds:Reference>

correct:

<ds:Reference URI="abc"> ... </ds:Reference>

Digitally signed ebXML Messages also do not have the prefixes for the

Digital Signature namespaced elements attributes.

 

 

Comment:

 

Yes, it was recognized that version 2.0 instances would need some minor modifications when used with the 2.1 schema (in addition to the namespace change!)

 

One maintenance issue was to change the attributeFormDefault value (which was “qualified” in version 2.0) to “unqualified” in 2.1

 

In part, this change was motivated so that when using xmldsig constructs within a CPP or CPA, we would not run into difficulties from mixing  modes(which is, as you say, effectively “unqualified” for its attributeFormDefault).

 

There is an easy style sheet transform for converting to attributes without prefixes. I think the only things to watch is to avoid removing the “xml:” prefix on “xml:lang” and to watch out for removing a prefix for xlink.

 

I will hunt up the transform which much be somewhere on my disk and post it to the list.

 

The examples to be used for the maintenance release have already been converted to work.

 

Is there any other action you wish to recomment for the 2.1 release?

 

Thanks

Dale Moberg

Acting editor