OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [ebxml-dev] ebxml message schema

Title: FW: ebxml message schema
We have noticed that the xmldsig schema imported in the version 2 of the
message schema has a different location from the one used in the cpa/cpp
schema. This in itself is not a problem, however these schema’s definitions
are different yet both use the same namespace. This plays havoc with our
object mapping tool’s notion that same namespaces means similar schema defs.

>From msg-header-2_0.xsd we get:
<import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/xmldsig-core-schema.xsd"/>

>From above location (snip)
<element name="SignatureValue" type="ds:SignatureValueType"/>
<complexType name="SignatureValueType">
        <extension base="base64Binary">
            <attribute name="Id" type="ID" use="optional"/>

>From cpp-cpa-v1_0.xsd we get
 <import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://ebxml.org/project_teams/transport/xmldsig-core-schema.xsd"/>

>From above location (same snip) ?
<element name="SignatureValue" type="ds:CryptoBinary" />
<simpleType name="CryptoBinary">
    <restriction base="binary">
?       <encoding value="base64" />
? </restriction>

Would you please consider giving a different namespace to the later version.

Regards Ian & Leanne

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC