- dfdl-wg - lists.ogf.org

IMF Comments
by Garriss Jr., James P. 02 Apr '13

02 Apr '13

Comments can appear anywhere in the value of an email header. The initiator is an open paren, and the terminator a closed paren. They are meant only for human readers, thus they can be safely ignored by processors. These are equivalent: MIME-Version: 1.0 MIME-Version: 1.0 (produced by MetaSend Vx.x) MIME-Version: (produced by MetaSend Vx.x) 1.0 MIME-Version: 1.(produced by MetaSend Vx.x)0 I don't see comments used in too many headers, but they are used frequently in the Received header: Received: from e06smtp13.uk.ibm.com (e06smtp13.uk.ibm.com [195.75.94.109]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 655301F069B for <jgarriss(a)mitre.org>; Tue, 12 Mar 2013 08:02:00 -0400 (EDT) How would you handle this in DFDL? Does it have a mechanism for saying, "This element can appear anywhere and any number of times inside of this other element?"

2 1

Rescheduled: OGF DFDL WG Call (5 Apr 15:00 GDT in DE3S09)
by Steve Hanson 02 Apr '13

02 Apr '13

OGF DFDL WG weekly call dial-in details. Passcode for Participants: 5381214 Canada Toll-Free 888-426-6840 China Toll-Free 10-800-711-1071 CHINA NETCOM GROUP USERS China Toll-Free 10-800-110-0996 CHINA TELECOM SOUTH USERS France Toll-Free 0800-94-0558 Germany Toll-Free 0800-000-1018 India Toll-Free 000-800-100-1176 Ireland Toll-Free 1-800-943-427 Israel Toll-Free 1-809-417-783 United Kingdom Caller Paid 0-20-30596451 United Kingdom Toll-Free 0800-368-0638 USA Caller Paid 215-861-6239 USA Toll-Free 888-426-6840 Other international numbers available - e-mail smh(a)uk.ibm.com. OGF DFDL Home: http://www.ogf.org/dfdl Redmine DFDL: http://redmine.ogf.org/projects/dfdl-wg Moving to Friday for this week only to accommodate Easter holidays. Extending to 90 mins for this week only as we will be reviewing draft updated spec.

1 0

case insensitivity
by Garriss Jr., James P. 02 Apr '13

02 Apr '13

In IMF, headers are generally case insensitive. Thus these are equivalent: Content-Type: text/html Content-Type: TEXT/HTML Content-Type: Text/Html Content-Type: tExT/hTmL Does DFDL have a way to tell the parser to parse text in a case-insensitive manner? A quick search of the spec didn't reveal anything.

2 1

Encoded Words: A Problem for DFDL
by Garriss Jr., James P. 30 Mar '13

30 Mar '13

The attached PDF file details a feature of email headers known as encoded words. I think DFDL is incapable of modeling this feature, but I'd like to get your feedback. TIA

2 1

AUTO: Sunil Dandamudi is out of the office (returning 04/01/2013)
by Sunil Dandamudi 28 Mar '13

28 Mar '13

I am out of the office until 04/01/2013. Note: This is an automated response to your message "dfdl-wg Digest, Vol 81, Issue 51" sent on 03/28/2013 10:00:02. This is the only notification you will receive while this person is away.

1 0

Multiple asserts on same object
by Steve Hanson 28 Mar '13

28 Mar '13

What's the expected behaviour if I place the following 2 asserts on the same object? <dfdl:assert>{fn:false()}</dfdl:assert> <dfdl:assert>{fn:false()}</dfdl:assert> Do both get evaluated, and the results 'stacked'? Or once the first fails do we not bother with the second? Spec is not clear. My motivation is to use multiple dfdl:asserts to get me out of nested points of uncertainty. I am seeing with IBM DFDL that the second is not evaluated. (The order of evaluation is implementation dependent, but as they are the same that makes no difference.) Regards Steve Hanson Architect, IBM Data Format Description Language (DFDL) Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

1 0

Re: [DFDL-WG] whitespace in DFDL annotations: right now regex is xs:string, expression is xs:token
by Steve Hanson 27 Mar '13

27 Mar '13

Suman Looking at the XML schema-for-schemas, and doing a test in the XSD editor in eclipse, XSD enumeration facets are modelled as xs:NMTOKEN and not xs:string, like DFDL enums. XSD is perfectly happy to strip/collapse white space. I think therefore that we should be doing the same for DFDL enum properties. I don't see any harm in this - an enum is a contiguous sequence of non-whitespace characters anyway, so any leading/trailing whitespace is harmless. Looks like XSD pattern facet is modelled as xs:string, preserving white space. We should do the same for DFDL regex properties. Regards Steve Hanson Architect, IBM Data Format Description Language (DFDL) Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 From: Steve Hanson/UK/IBM To: Suman Kalia <kalia(a)ca.ibm.com>, Cc: dfdl-wg(a)ogf.org, dfdl-wg-bounces(a)ogf.org, Mike Beckerle <mbeckerle.dfdl(a)gmail.com> Date: 19/03/2013 17:41 Subject: Re: [DFDL-WG] whitespace in DFDL annotations: right now regex is xs:string, expression is xs:token The type called DFDLExpressionOrPatternOrNothing only makes sense for use in one place - the element value of an assert or discriminator. Regards Steve Hanson Architect, IBM Data Format Description Language (DFDL) Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848 From: Suman Kalia <kalia(a)ca.ibm.com> To: Mike Beckerle <mbeckerle.dfdl(a)gmail.com>, Cc: dfdl-wg(a)ogf.org, dfdl-wg-bounces(a)ogf.org Date: 19/03/2013 17:29 Subject: Re: [DFDL-WG] whitespace in DFDL annotations: right now regex is xs:string, expression is xs:token Sent by: dfdl-wg-bounces(a)ogf.org Mike - I am not sure but my gut feeling is that it would start with the most restrictive one first. i.e If empty string ( assuming it has length facet 1) - would match Nothing , then xsd:token which is restricted form of xs:string. I think you are going to get string with white spaces collpsed ( xsd:token) if it not empty string. You can run few tests to see the behavior.. Suman Kalia IBM Canada Lab WMB Toolkit Architect and Development Lead Tel: 905-413-3923 T/L 313-3923 Email: kalia(a)ca.ibm.com For info on Message broker http://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.h… From: Mike Beckerle <mbeckerle.dfdl(a)gmail.com> To: dfdl-wg(a)ogf.org, Date: 03/19/2013 12:43 PM Subject: [DFDL-WG] whitespace in DFDL annotations: right now regex is xs:string, expression is xs:token Sent by: dfdl-wg-bounces(a)ogf.org This came up on the call. The schemas I have for DFDL annotations have DFDLRegularExpression as an xs:string, and DFDLExpression as an xs:token. I have no clue what a union of these types behaves like. But we have a union called DFDLExpressionOrPatternOrNothing which is a 3-way union of DFDLExpression, DFDLRegularExpression, and EmptyString (which is also derived from xs:string but has length facet of 0 as well. -- Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com -- dfdl-wg mailing list dfdl-wg(a)ogf.org https://www.ogf.org/mailman/listinfo/dfdl-wg -- dfdl-wg mailing list dfdl-wg(a)ogf.org https://www.ogf.org/mailman/listinfo/dfdl-wg Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

1 0

Are non-native attributes allowed on DFDL annotation elements?
by Mike Beckerle 27 Mar '13

27 Mar '13

In XML Schema you are allowed to throw in attributes even just as documentation i.e., <xs:element xmlns:rtfm="read:the:..manual." name="myElement" rtfm:yo="this element name is general lameness" .../> I.e, in the definition of xs:element there is this wildcard with standard lax validation for any non-native attributes. So, the question is do we want to also allow that on dfdl annotation elements, i.e, <dfdl:format byteOrder="bigEndian" rtfm:yo="it's LE Loser!" /> Given that you cannot nest  inside element syntax, these non-native attributes are the only convenient way to add commentary to the attributes of a XML document. Another perhaps more compelling reason to tolerate this is that I am sure in the next year all the DFDL implementation efforts are going to add some new experimental properties, and we will want to hang them on the same dfdl annotation elements. Schema inter-operation requires us each to tolerate the other's such experimental properties to the extent that they are not essential to the schema being usable at all. So if I have: <dfdl:element dafext:recursive="typesOnly" xmlns:dafext="some.daffodil.urn.for.extensions" ref="someOtherFormat" /> then we will want IBM DFDL and DFDL implementations generally, to perhaps warn that it was there and unrecognized, but not to just SDE on non-validation. Today, the XML Schemas for DFDL Annotations do not allow non-native attributes inside DFDL annotation elements, but the spec is silent on the subject. I was considering adding a couple of experimental properties (not right away, but maybe by year end), and I only realized today that they would break compatibility without a change here. Comments? -- Mike Beckerle | OGF DFDL Workgroup Co-Chair | Tresys Technology | www.tresys.com

2 1

OGF DFDL WG Call Minutes 2013-03-26
by Steve Hanson 26 Mar '13

26 Mar '13

Please find minutes from the above call on Redmine at http://redmine.ogf.org/dmsf_files/13062?download= Errata document is now at v012 here: http://redmine.ogf.org/dmsf_files/8104?download= Action 140 errata addendum at v001 here: http://redmine.ogf.org/dmsf_files/13017?download= Regards Steve Hanson Architect, IBM DFDL, Co-Chair, OGF DFDL Working Group IBM SWG, Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

checkConstraints example?
by Garriss Jr., James P. 26 Mar '13

26 Mar '13

Can you please supply an example of using checkConstraints to valid an enumeration? There's not one in the spec, and none of the tutorials I have demo this. Suppose I have this DFDL: <xsd:element name="DayOfTheWeek"...> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="Mon" /> <xsd:enumeration value="Tue" /> <xsd:enumeration value="Wed" /> ... </xsd:restriction> </xsd:simpleType> </xsd:element> TIA

3 3