- dfdl-wg - lists.ogf.org

More Date/Time/DateTime Clarifications
by Steve Lawrence 15 Apr '13

15 Apr '13

We need a couple more clarifications on implementing date/time/dateTime in Daffodil. 1) What is the expected infoset output? The spec seems to be silent on this issue. Based on some tests we received from IBM, it looks like this makes sense: xs:date = uuuu-MM-ddxxx xs:time = HH:mm:ss.SSSSSSxxx xs:dateTime = uuuu-MM-dd'T'HH:mm:ss.SSSSSSxxx Points of interest: - uuuu instead of yyyy. The u allows for negative years, which is needed to represent BC dates - There are 6 significant figures for fractional seconds - Timezone is represented as xxx, since UTC is represented as +00:00 instead of 'Z' in the IBM tests we have Does this seem correct? 2) We would like some confirmation on the patterns for calendarPatternKind="implicit"? The current spec has: xs:date = yyyy-MM-dd xs:time = HH:mm:ssZZZ xs:dateTime = yyyy-MM-dd'T'HH:mm:ss The IBM tests we have match these patterns except for the timezone pattern for xs:time. The ZZZ pattern matches -0800, however, the IBM test we have parse -08:00. This could be represented with a few different patterns (e.g. ZZZZZ, XXX, xxx, xxxxx). We're unsure if the IBM tests are incorrect of if the spec needs to be updated. It also seems odd to me that the xs:time pattern has a timezone whereas dateTime does not. I'm not arguing it's wrong, just that it's not intuitive to me. Note that we don't have IBM's tool set up yet, so we can't verify if the tests we have actually represent IBM behavior. Thanks, - Steve

3 2

Cancelled: OGF DFDL WG Call
by Steve Hanson 12 Apr '13

12 Apr '13

Mike is on holiday

1 0

OGF DFDL WG Call 2013-04-09 - cancelled
by Steve Hanson 08 Apr '13

08 Apr '13

Sorry have to cancel the call as I am busy with clients all day. Regards Steve Hanson Architect, IBM DFDL Co-Chair, OGF DFDL Working Group Hursley, UK smh(a)uk.ibm.com tel:+44-1962-815848

1 0

Cancelled: OGF DFDL WG Call
by Steve Hanson 08 Apr '13

08 Apr '13

Cancelled: OGF DFDL WG Call 09/04/2013 - (Repeats) Chair: Steve Hanson/UK/IBM Sent By: Steve Hanson/UK/IBM@IBMGB Location: DE3S09 Steve Hanson/UK/IBM@IBMGB Steve Hanson has cancelled this meeting. Your calendar will be updated to reflect this change. Repeats This entry repeats Required: mbeckerle.dfdl(a)gmail.com, Suman Kalia/Toronto/IBM@IBMCA, Tim Kimber/UK/IBM@IBMGB Optional: dfdl-wg(a)ogf.org, Stephanie Fetzer/Charlotte/IBM@IBMUS

1 0

The length of this element should be more than 1 character
by Garriss Jr., James P. 06 Apr '13

06 Apr '13

Suppose I have a text element whose length must be greater than 1 character. I think an assert should be able to handle this, and there's a string-length() function, so I wrote this for my xPath expression: fn:string-length(.) > 1 But MBTK is telling me: CTDX1100E : XSD: The attribute 'null' is not permitted (This is, BTW, a less-than-helpful error message.) [cid:image001.png@01CE3200.633AA6A0] I added it manually, like so: <xsd:element name="Body" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.ogf.org/dfdl/"> <dfdl:assert message="The length of the body must be more than 1 character"> { fn:string-length(.) > 1 } </dfdl:assert> </xsd:appinfo> </xsd:annotation> </xsd:element> And MBTK gave me this error: CTDV1493E : XPath expression '{ fn:string-length(.) > 1 }' contains a path expression that does not resolve to an element in the schema: 'Found ">" at line 1, column 23. Expected one of "}" "or" "and" "*" "div" "idiv" "mod" "eq" "ne" "lt" "le" "gt" "ge" "[" "-" "+" "/"'. Element: #xmlns(p="http://fileid")xscd(/schemaElement::p:ImfMime/type::0/model::sequence/schemaElement::Body). So this indicates it doesn't like the ">" character. So I changed it to > but got the same message. So am I implementing this wrong? Or does MBTK not support this function? Daffodil is also giving me an error: Schema Definition Error: XPath Compilation Error: net.sf.saxon.trans.XPathException: XPath syntax error at char 20 in {fn:string-length(.) > 1}: Prefix fn has not been declared Schema context: element.Body. Location in file:/C:/Users/jgarriss/daffodil-0.8.1/bin/DetectImfMime.xsd But this is a different issue, a namespace issue. MBTK magically knows about the "fn:" namespace, but Daffodil doesn't. It's not declared in the root element: <?xml version="1.0" encoding="UTF-8"?> <xsd:schema targetNamespace="http://fileid" xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/" xmlns:fmt="http://www.ibm.com/dfdl/GeneralPurposeFormat" xmlns:ibmSchExtn="http://www.ibm.com/schema/extensions" xmlns:ns0="http://fileid" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> Help!

2 1

OGF DFDL WG Call Minutes 2013-04-05
by Steve Hanson 05 Apr '13

05 Apr '13

Please find minutes from the above call on Redmine at http://redmine.ogf.org/dmsf_files/13065?download= Errata document is now at v013 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

OGF DFDL WG Call Agenda 2013-04-05
by Steve Hanson 05 Apr '13

05 Apr '13

Please find agenda for call on Redmine at http://redmine.ogf.org/dmsf_files/13065?download= This is the call rescheduled from Tuesday. 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

1 0

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