[OASIS Issue Tracker] (BDXR-27) XHE 1.0 uses only relative namespace URIs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/BDXR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=77828#comment-77828 ] 

Philip Helger commented on BDXR-27:
-----------------------------------

The requirement to use absolute URIs is part of the C14N spec: [https://www.w3.org/TR/2001/REC-xml-c14n-20010315]

Quote from section 2.1:
{quote}**Note: This specification supports the recent XML plenary decision to deprecate relative namespace URIs as follows: implementations of XML canonicalization MUST report an operation failure on documents containing relative namespace URIs. XML canonicalization MUST NOT be implemented with an XML parser that converts relative URIs to absolute URIs.
{quote}
Link to the plenary decision: [https://lists.w3.org/Archives/Public/xml-uri/2000Sep/0083.html]

Â

> XHE 1.0 uses only relative namespace URIs
> -----------------------------------------
>
>                 Key: BDXR-27
>                 URL: https://issues.oasis-open.org/browse/BDXR-27
>             Project: OASIS Business Document Exchange (BDXR) TC
>          Issue Type: Bug
>          Components: XML Schema
>            Reporter: Philip Helger
>            Priority: Major
>
> The namespace URI of the XHE 1.0 scheme is currently
> {{oasis-cefact-xhe-1.0-ExchangeHeaderEnvelope}}
> Also aggregate components ({{oasis-cefact-xhe-1.0-AggregateComponents}}), basic components ({{oasis-cefact-xhe-1.0-BasicComponents}}) etc. use relative XML schemas.
> Unfortunately relative namespace can cause problems when using XMLDsig with the [http://www.w3.org/2001/10/xml-exc-c14n#] algorithm.
> [~gkholman] has the details on the why and how :)



--
This message was sent by Atlassian Jira
(v8.3.3#803004)