September 2005 - dfdl-wg

Wednesday's telcon
by Martin Westhead 21 Sep '05

21 Sep '05

9am PDT Wednesday 21st September 2005 Preliminary Agenda ------------------ - Agenda for sessions/F2F at GGF - Tracking document modifications - Issues list (starting from item 16) Conference call instructions: Number: 1-800-664-0771 At the automated answering system, press 0 for the operator. Ask for the "Daffodil working group" call.

1 0

minutes of call 2005-09-14
by Mike Beckerle 20 Sep '05

20 Sep '05

Who: Jim Myers, Mike Beckerle, Tara Talbott, Steve Hanson, Geoff Judd, Bob McGrath Agenda: GGF plans - we will have F2F at GGF15. The schedule of our WG sessions at the GGF15 are not yet set, but we'll have F2F meetings during the non-scheduled times. We're counting on the fact that most of our DFDL WG members are focused on DFDL and won't mind the conflict with the rest of GGF15 much. People should make travel plans for all 3 days M, T, W. GridForge Forums - these seem to be working now. Will try them when one of our subcommittees reports back to the broader WG. E.g., scoping or arrays. Issues list - we made it through items 5 to 15 Issue 5 - resolution. No built-in set of defaults. If you need a property and your configuration doesn't have one specified then it is an error. There is a small set of named configurations provided with DFDL each of which is a self-consistent set of properties. This is probably the set that we find useful in the primer and other WG docs. Issue 6 - resolution. change attribute name from 'base' to 'extends' Issue 7 - belongs on same tracker as 8, 9, 10 Issue 11 - resolution: add an attribute 'byteOrderMarkPolicy' values are: required, notAllowed, optionalButGenerateOnOutput, optionalButOmitOnOutput (the generate on output control aspect was not discussed on the call. I thought of that just now while typing.) Issue 12 - fix diagram - omission of these types was unintentional. Better diagram next draft Issue 13 and 14 - new tracker item - Steve Hanson, Geoff Judd and someone from MikeB's team at IBM to address Issue 15 - resolution: each delimiter will grow an extra rep-property for its regexp variant. E.g., separator will have corresponding separatorRegexp property. Only one of the two may be specified. We discussed that separator (or any delimiter) can be a text string, and we had previously decided that the separatorEncoding attribute would go away to be replaced by a syntax for expressing hex bytes (not hex character codes, real non-charset transformed hex bytes) as part of delimiter strng literals. This same way of putting hex bytes would also be supported as part of the regexp language so that the regexp language remains able to include any non-regular expression for a delimiter into a regular expression. (Editor's Note: this is a bit tricky. We now have in string literals 3 different escape mechanisms that are different. 1) XML character code specifiers e.g., 'abc,def' which is the normal XML way of specifying the unicode #x2C character code. (This is an XML standard escape convention.) Used inside a delimiter string this means take the unicode #x2c code point, figure out what character it corresponds to in the charset of the data element and use that character. Note that this is the same thing that 'a' means. Take the 'a' unicode code point, figure out what character corresponds to 'a' in the charset of the data element, and look for that. 2) nonXML character code specifiers e.g., 'abc\#x00;def' which is the way we allow you to put XML-disallowed unicode character codes like #x00 into a string literal. (This is a DFDL convention). The interpretation here is exactly like the above. I.e., '\#x2c;' is exactly equivalent to ',' and the charset mapping applies as above. This rule is only needed because of the XML restriction disallowing certain unicode character codes from the XML infoset. 3) non-character byte specifiers. E.g., 'abc\%01;\%02;def' which is a proposed escape syntax that means put the bytes #x01 and #x02 into the string literal bypassing any considerations of charset, i.e., without considering them to be character codes in any character set. That is, these byte values have nothing to do with unicode codepoint values. (This is a DFDL convention.) The other characters of the string would be treated as per (1) and/or (2) above. )

2 2

Fw: [dfdl-wg] minutes of call 2005-09-14
by Steve Hanson 15 Sep '05

15 Sep '05

Hi Mike Re the three escape mechanisms. It is unfortunate that we need a separate mechanism for the second case (as discussed in the draft spec section 26). Re the third mechanism for escaping hex literals. An alternative syntax could be \#0x2C; using 0x to indicate hex. &#0x2C; would be even better - but does it cause XML problems? Regards, Steve ----- Forwarded by Steve Hanson/UK/IBM on 15/09/2005 09:33 ----- Mike Beckerle <beckerle(a)us.ibm. com> To Sent by: dfdl-wg(a)gridforum.org owner-dfdl-wg@ggf cc .org Subject [dfdl-wg] minutes of call 14/09/2005 22:18 2005-09-14 Who: Jim Myers, Mike Beckerle, Tara Talbott, Steve Hanson, Geoff Judd, Bob McGrath Agenda: GGF plans - we will have F2F at GGF15. The schedule of our WG sessions at the GGF15 are not yet set, but we'll have F2F meetings during the non-scheduled times. We're counting on the fact that most of our DFDL WG members are focused on DFDL and won't mind the conflict with the rest of GGF15 much. People should make travel plans for all 3 days M, T, W. GridForge Forums - these seem to be working now. Will try them when one of our subcommittees reports back to the broader WG. E.g., scoping or arrays. Issues list - we made it through items 5 to 15 Issue 5 - resolution. No built-in set of defaults. If you need a property and your configuration doesn't have one specified then it is an error. There is a small set of named configurations provided with DFDL each of which is a self-consistent set of properties. This is probably the set that we find useful in the primer and other WG docs. Issue 6 - resolution. change attribute name from 'base' to 'extends' Issue 7 - belongs on same tracker as 8, 9, 10 Issue 11 - resolution: add an attribute 'byteOrderMarkPolicy' values are: required, notAllowed, optionalButGenerateOnOutput, optionalButOmitOnOutput (the generate on output control aspect was not discussed on the call. I thought of that just now while typing.) Issue 12 - fix diagram - omission of these types was unintentional. Better diagram next draft Issue 13 and 14 - new tracker item - Steve Hanson, Geoff Judd and someone from MikeB's team at IBM to address Issue 15 - resolution: each delimiter will grow an extra rep-property for its regexp variant. E.g., separator will have corresponding separatorRegexp property. Only one of the two may be specified. We discussed that separator (or any delimiter) can be a text string, and we had previously decided that the separatorEncoding attribute would go away to be replaced by a syntax for expressing hex bytes (not hex character codes, real non-charset transformed hex bytes) as part of delimiter strng literals. This same way of putting hex bytes would also be supported as part of the regexp language so that the regexp language remains able to include any non-regular expression for a delimiter into a regular expression. (Editor's Note: this is a bit tricky. We now have in string literals 3 different escape mechanisms that are different. 1) XML character code specifiers e.g., 'abc,def' which is the normal XML way of specifying the unicode #x2C character code. (This is an XML standard escape convention.) Used inside a delimiter string this means take the unicode #x2c code point, figure out what character it corresponds to in the charset of the data element and use that character. Note that this is the same thing that 'a' means. Take the 'a' unicode code point, figure out what character corresponds to 'a' in the charset of the data element, and look for that. 2) nonXML character code specifiers e.g., 'abc\#x00;def' which is the way we allow you to put XML-disallowed unicode character codes like #x00 into a string literal. (This is a DFDL convention). The interpretation here is exactly like the above. I.e., '\#x2c;' is exactly equivalent to ',' and the charset mapping applies as above. This rule is only needed because of the XML restriction disallowing certain unicode character codes from the XML infoset. 3) non-character byte specifiers. E.g., 'abc\%01;\%02;def' which is a proposed escape syntax that means put the bytes #x01 and #x02 into the string literal bypassing any considerations of charset, i.e., without considering them to be character codes in any character set. That is, these byte values have nothing to do with unicode codepoint values. (This is a DFDL convention.) The other characters of the string would be treated as per (1) and/or (2) above. )

2 1

Re: [dfdl-wg] Telcon Summary 2005-09-07
by Martin Westhead 08 Sep '05

08 Sep '05

> who are members of DFDL. To get membership you have to go to the DFDL > page and click on "Request membership" in the top right. Can Tara and > Bob, and anyone else who might lead a team do this please? I just double checked this. It turns out that tracker artifacts can only be assigned to site administrators. So, we could make everyone administrators, but for now, I have added a custom field "Team leader" which we can set the options for. Martin

1 0

Issues list update
by Martin Westhead 07 Sep '05

07 Sep '05

Since the issues list seems to be useful. I have updated it after today's discussion. I have also tidied up a few formating glitches. Please let me know if there are any further problems (strange characters etc.) with the way it is displayed. I have added an Issues List Master document which is the Open Office version (.sxc) of this document. Unfortunately Gridforge adds a .unknown extension when you download it, this may need to be deleted to get open office to accept it. In future if you are constructing a list of comments for the group that you believe are likely to end up as issues it would be very helpful if you could arrange them in something close to this format. i.e. a table in some format (Excel, Word, HTML, Open Office, etc) with some of these columns. Then the relevant columns can be cut and pasted into place. Thanks, Martin

1 0

Fw: [dfdl-wg] Opaque/BLOB/Uninterpreted/Raw - also hexBinary - (was Re: split into multiple topics - Re: [dfdl-wg] Issues: additional data types)
by Steve Hanson 07 Sep '05

07 Sep '05

I prefer the hexBinary approach. The disadvantage Mike observes with the array of bytes approach is not limited to conversion to XML. It would also apply to any in-memory tree (SDO etc) built by the DFDL parser. And the element unnecessarily becomes eligible to take the dfdl:occurs annotation. Regards, Steve Steve Hanson WebSphere Business Integration Brokers, IBM Hursley, England Internet: smh(a)uk.ibm.com Phone (+44)/(0) 1962-815848 ----- Forwarded by Steve Hanson/UK/IBM on 07/09/2005 11:23 ----- Mike Beckerle <beckerle(a)us.ibm. com> To Sent by: Mike Beckerle <beckerle(a)us.ibm.com> owner-dfdl-wg@ggf cc .org dfdl-wg(a)gridforum.org, "Robert E. McGrath" <mcgrath(a)ncsa.uiuc.edu>, owner-dfdl-wg(a)ggf.org 06/09/2005 21:21 Subject [dfdl-wg] Opaque/BLOB/Uninterpreted/Raw - also hexBinary - (was Re: split into multiple topics - Re: [dfdl-wg] Issues: additional data types) re: Opaque or uninterpreted or raw fields. These are sometimes called Blobs, though database people reserve that term for the acronym "BLOB" which stands for Binary Large Object, which has to do with size being too large for the smaller binary SQL type objects. I.e., there's no such thing as a small BLOB in databases. I think in our mailing list we've used blob to mean "opaque bytes" of any size at all. I believe use of the 'hexBinary' type is also probably this same topic. I.e., how to deal with data where you don't know its proper interpretation, though you can express how big it is so that we can at least copy it from place to place. I think there are two choices here. One is just use "occuring" bytes. E.g., here's uniterpreted data of length 1234 bytes: <element name="ignoreMe" type="byte" minOccurs="1234" maxOccurs="1234" dfdl:repType="binary"/> This is a basic binary byte array. I think this works fine as a blob/opaque type. I believe we do not need any other kind of raw/opaque type. If we had one, we'd have to have a way to express its length, and be specific about the units of that length, and the above accomplishes that with pretty much minimum baggage. You name it what you want, i.e, "unused" or "dummy" or "ignore" or whatever you want. We might want an annotation to indicate that this data should not be accessed, to distinguish this case from an actually array of bytes that you DO want to access, but I'm not sure that's worth it. Note that the OMG CAM model does have an access control attribute. Perhaps we can use that. However, I doubt it allows distinguishing copy from access. The alternative is to use the "hexBinary" type for this. In that case we need to express the size in the DFDL annotation: <element name="ignoreMe" type="hexBinary" dfdl:repLength="1234" dfdl:repType="binary"/> I can think of one advantage of hexBinary over the occuring bytes approach, which is suppose you do want to use DFDL in the obvious way to convert data into XML format. Never mind that DFDL is supposed to enable avoiding this, suppose it's what you want to do. Then my above byte array for the "ignoreMe" element ends up as: <ignoreMe>0</ignoreMe><ignoreMe>0</ignoreMe><ignoreMe>0</ignoreMe><ignoreMe>0</ignoreMe><ignoreMe>0</ignoreMe><ignoreMe>0</ignoreMe>....<ignoreMe>0</ignoreMe> Which is big compared to: <ignoreMe>000000000000...00</ignoreMe> which is what we'd get if we allow hexBinary as a type. Note that if we add the hexBinary type, you'll still be able to do it the other way, so the hexBinary notion is not strictly speaking necessary or minimalist. ...mikeb Mike Beckerle Architect, Scalable Computing IBM Software Group Information Integration Solutions Westborough, MA Mike Beckerle/Worcester/IBM@IBMUS Sent by: To owner-dfdl-wg(a)ggf.org "Robert E. McGrath" <mcgrath(a)ncsa.uiuc.edu> cc 09/02/2005 04:34 PM dfdl-wg(a)gridforum.org, owner-dfdl-wg(a)ggf.org Subject split into multiple topics - Re: [dfdl-wg] Issues: additional data types I'd like to split this topic into several distinct ones: Arrays - I have a placeholder for this in the doc. Opaque and "code" types are separate. This is related also to the concept of "open content". Enums Bitfields Pointers Mike Beckerle Architect, Scalable Computing IBM Software Group Information Integration Solutions Westborough, MA "Robert E. McGrath" <mcgrath(a)ncsa.uiuc.edu> Sent by: owner-dfdl-wg(a)ggf.org To dfdl-wg(a)gridforum.org 09/02/2005 03:13 PM cc Subject [dfdl-wg] Issues: additional data types Greetings, Here is an "issue" for the DFDL: additional data types that should be considered. Please see attached. --- Robert E. McGrath National Center for Supercomputing Applications University of Illinois, Urbana-Champaign Champaign, Illinois 61820 (217)-333-6549 mcgrath(a)ncsa.uiuc.edu (See attached file: DT.htm)

1 0

Telcon Summary 2005-09-07
by Martin Westhead 07 Sep '05

07 Sep '05

Present ------- Mike Bekerle Robert McGrath Steve Hanson Tara Talbott Martin Westhead Geoff Judd Plans for F2F at GGF -------------------- - we should get the schedule for the DFDL sessions at GGF15 at end of this week. - we'll schedule DFDL WG F2F sessions around these time slots on the other days of the conference. - we have booked a conf. room (seats 10) at an IBM facility a short distance (walkable, quick cab ride) from the GGF15 event for DFDL WG F2F discussions on the other days. (I have all 3 days held now.) Trackers vs. issues list ------------------------ Discussed value of trackers against the issues list. It was thought that trackers should be used for tracking large scale actions, the list for small grained issues. Email vs. Forums ---------------- Some are still unhappy about the difficulty of reading unthreaded discussions. However, notification on Grid Forge is still broken on the Forums. The group was unable to come up with anything better than email. We will put pressure, GGF to fix this and progress with email for now. IBM will also look at using alternative mail readers that with display threads. Choosing topics/issues for discussion ------------------------------------- Ideally topics will be chosen in the previous meeting. However, for now an item by item review of the issues list seems to be our current process. Issues list review ------------------ Reviewed items 1-4. Set up new trackers: - Arrays [Bob McGrath] - Scoping (including Selector) [Mike Bekerle] - Layers [Tara Talbott] All to report by Face to Face Oct 3rd. Notes on trackers: - The assignments are not as above. I can only assign projects to people who are members of DFDL. To get membership you have to go to the DFDL page and click on "Request membership" in the top right. Can Tara and Bob, and anyone else who might lead a team do this please? - I made a mistake and submitted the Layers item twice. I have not worked out how to delete it so I moved it to "Dead items" tracker...

1 0

Fw: [dfdl-wg] Issues List
by Steve Hanson 07 Sep '05

07 Sep '05

The tracker system looks to be exactly what we want. Regards, Steve Steve Hanson WebSphere Business Integration Brokers, IBM Hursley, England Internet: smh(a)uk.ibm.com Phone (+44)/(0) 1962-815848 ----- Forwarded by Steve Hanson/UK/IBM on 07/09/2005 09:04 ----- Martin Westhead <martinwesthead@y ahoo.co.uk> To Sent by: Martin Westhead owner-dfdl-wg@ggf <martinwesthead(a)yahoo.co.uk> .org cc dfdl-wg(a)gridforum.org Subject 07/09/2005 07:32 Re: [dfdl-wg] Issues List Martin Westhead wrote: > - This is an excel file generated with Open Office please let me know > if there are problems with the document. It turns out this does not work well in Excel. I have replaced it with an HTML version that can be found here: https://forge.gridforum.org/projects/dfdl-wg/document/Issues_List/en/1 Let me know what you think: - is this too fine grained - should we be using trackers instead (e.g. see: https://forge.gridforum.org/projects/dais-wg) Cheers, Martin

1 0

Discussing DFDL spec issues via email
by Steve Hanson 07 Sep '05

07 Sep '05

I don't know what others think, but this is not working for me. My inbox is a sea of mail, some of which are replies with history, some of which are not; some have replies in-line, some have not. We definitely need an alternative place to post discussions. If the forum notification system does not work properly then maybe we need to get into the habit of checking the forums regularly? Regards, Steve Steve Hanson WebSphere Business Integration Brokers, IBM Hursley, England Internet: smh(a)uk.ibm.com Phone (+44)/(0) 1962-815848

1 0

Issues List
by Martin Westhead 07 Sep '05

07 Sep '05

Hi Folks, I have published an issues list at: https://forge.gridforum.org/projects/dfdl-wg/document/Issues_List/en/1 There are currently 69 issues taken from the draft IBM spec, the comments from IBM Hursley and Robert McGrath's recent email. This was (by necessity) a rough cut n' paste exercise so there will be bugs. Please take a look. I'd like to have a brief discussion about whether this is the correct format/approach etc. tomorrow. No doubt there will be some rationalization of the issues required please could those who generated them look them over and suggest modifications/duplicate issues etc. Notes: - At this point I have ignored issues associated with the appendices of the draft. - This is an excel file generated with Open Office please let me know if there are problems with the document. Cheers, Martin

1 1