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


Help: OASIS Mailing Lists Help | MarkMail Help

bdxr message

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

Subject: Re: [bdxr] BDE-question

At 2015-05-29 09:10 +0000, Martin Forsberg wrote:
I?ve followed the work on BDE carefully and also
presented an update on the project to the
CEN-BII team. The progress and result looks very
good, completely in line with the requirements specification we?ve published.

Thank you for that confirmation!

I?ve understood that the BDE PayloadContent
element now allows for non-xml (but escaped) text such as base64 encoded data.

Indeed.  In the latest draft I have included the
content of the example instance within the body
of the specification so that a reader need not
have to open any of the artefacts to see an illustration of this.

This is very useful if you want to transmit an
ASIC-container or other non-XML based payload.
SBDH doesn?t allow for this (the content type is
?element-only?) and that is a significant
drawback. The implementers of SBDH would need to
create an inner envelope which would allow non-element content .


So, my question is ? would it be useful to have
an attribute or element on the Payload or
PayloadContent indicating the encoding type of
the payload data? Essentially informing the
receiver about the fact that the payload is non-xml (in case non-xml is used)?

Would not the InstanceSyntaxID BIE provide
sufficient information to the recipient?

Payload. Instance Syntax Identifier. Identifier
Identifier. Type
Identifies the syntax that the payload instance is expressed in.

This was intended for the purpose you've identified.

Hmmmmmm ... perhaps I should modify the example
instance as follows, where I personally make the
assumption to use a MIME type (such a decision
would be agreed upon by trading partners in
advance of encoding messages with syntax
identifiers; I wouldn't want my example to be
considered as the only way to identify the payload as being simple text):

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://docs.oasis-open.org/bdxr/ns/bde/1.0/Envelope";
        <myElement>My Content</myElement>
        <myElement>My Content</myElement>
        <myElement>My Content</myElement>
    <ebc:InstanceSyntaxID schemeID="MIME">text</ebc:InstanceSyntaxID>
Non-XML payload here, with sensitive characters
escaped such as &amp;, &lt; and ]]&gt;.

Any text, provided it has been escaped, can be included in a payload.
        <myOtherElement>My Content</myOtherElement>
        <myOtherElement>My Content</myOtherElement>
        <myOtherElement>My Content</myOtherElement>

Per RFC1767 there is a MIME type for EDI content
(an example that was brought up in the meeting
where someone asked if we could put escaped
EDIFACT content in the envelope, which we can):


But, again, MIME isn't obligated to be used

Please let me know if you identify any concerns
regarding our proposed approach.

. . . . . . . . . Ken

Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Free 5-hour lecture:  http://www.CraneSoftwrights.com/links/video.htm |
Crane Softwrights Ltd.             http://www.CraneSoftwrights.com/o/ |
G. Ken Holman                    mailto:gkholman@CraneSoftwrights.com |
Google+ profile:       http://plus.google.com/+GKenHolman-Crane/about |
Legal business disclaimers:     http://www.CraneSoftwrights.com/legal |

This email has been checked for viruses by Avast antivirus software.

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