- dfdl-wg - lists.ogf.org

DFDL V1 Draft 45 and Proposed Recomendation Published version are available
by Alan Powell 23 Dec '10

23 Dec '10

The final versions for DFDL V1 are available on gridforge DFDL V1 Proposed Recommendation Published version as submitted to OGF http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.dfdl-wg/d… DFDL V1 Draft 45 (internal version of the Proposed Recommendation Published version) http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.dfdl-wg/d… Version Author/ Contributor History Date(yyyy-mm-dd) 045 Alan Powell LengthKind 'implicit' only uses xs:maxLength. xs:length no longer used Clarified lengthKind 'endOfParent' description. Minor typographical corrections Prefixed length allowed to have a prefix Removed restriction of one discriminator in a sequence fixed precedence table for arrays Correct hiddenGroupRef and escapeSchemeRef to be a union of QName and empty string Clarified that default properties can be in short, attribute or element form DFDL namespace changed from http://www.ogf.org/dfdl/dfdl-1.0 to http://www.ogf.org/dfdl/dfdl-1.0/ 2010-12-21 Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Fw: instructions on use of the Daffodil demo site
by Alan Powell 22 Dec '10

22 Dec '10

Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com ----- Forwarded by Alan Powell/UK/IBM on 22/12/2010 16:35 ----- From: Joe Futrelle <futrelle(a)ncsa.uiuc.edu> To: Alan Powell/UK/IBM@IBMGB Cc: "Robert E. McGrath" <remcgrat(a)illinois.edu> Date: 22/12/2010 16:20 Subject: instructions on use of the Daffodil demo site For the WG. Instructions on use of the demo site Three things to note about the demo: 1. It is running at a temporary location and may not be up at any given time. 2. It demonstrates Daffodil in its current, not-minimally-conforming state. 3. If you upload a schema, it may not remain in the demo site because we may reset the database. How to use it: Go to http://rift.ncsa.uiuc.edu:9999/public/ You should see an interface with a list of test cases under the "schemas" tab. Clicking on an entry in the list will show you information about the test case including links to the schema and the example input document. Below there are two controls. The "translate example" link will run Daffodil on the example input document. The "use" button lets you upload a document to translate. In either case you will need to authenticate. The username and password for the demo site are "dfdlwg" and "dfdlwg". After a successful translation, you will see two links appear under "translation results". The "document" link shows the result document. The "provenance" link shows a provenance trace graphic, with clickable links, showing the derivation of the result document from the schema and the input document (which the demo site identifies with freshly-minted URI's). The interface is not so helpful if the translation is unsuccessful (which it likely will be, for any schema you supply, until I fix numerous issues with Daffodil). In most cases you will just see "internal error: Could not generate translation". This is unfortunate, as the server logs contain pretty detailed error messages, e.g., for a schema definition error, the log describes the error and shows where in the schema it was detected. I plan to improve the error reporting on the demo site so that these messages are shown to the user. To upload a schema, click the "upload new schema" button. You'll see a form with the following fields, described below: 1. Format. This is simply a descriptive name you can give the test case and has no other meaning. 2. Schema. Click and select the schema file you want to upload 3. Example. Click and upload an example input file. 4. Example root. Which DFDL element to treat as the root element for the example input. 5. GRDDL. Optionally, a GRDDL transform to use to produce RDF (optional) 6. Author. You can type whatever you want here. 7. Description. You can type whatever you want here. Once uploaded, your test case will appear in the list of test cases, where you can select and invoke it. If for some reason it doesn't appear, click the "refresh" button. -- Joe Futrelle Cyberenvironments and Technologies National Center for Supercomputing Applications http://www.ncsa.uiuc.edu/People/futrelle 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

Minutes for OGF DFDL Working Group Call, 22 December 2010
by Alan Powell 22 Dec '10

22 Dec '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, 22 December 2010 Attendees Steve Hanson (IBM) Alan Powell (IBM) Apologies Suman Kalia (IBM) Bob McGrath (NCSA) Joe Futrelle (NCSA) Stephanie Fetzer (IBM) 1. Current Actions Updated below. 2. QName does not allow empty space Change property type of dfdl:escapeSchemeRef and dfdl:hiddenGroupRef from "Qname" to "QName or empty Space" (Not needed for prefixLengthType as it is controlled by lengthKind "prefix") Agreed 3. DFDL namespace URI Should the DFDL namespace URI be changed to http://www.ogf.org/dfdl/dfdl-1.0/ (add trailing /) Agreed 4. Status of OGF DFDL V1 review OGF concerns related to confusion over IBM patents. IBM has clarified that no patents need to be declared Expecting approval soon. Updated version of spec will be uploaded this week. 5. AOB - Next call Jan 12th 2011. There are new dial in numbers for WG calls next year 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 Meeting closed, 15:35 Next call Wednesday 12 January 2011 15:00 UK (10:00 ET) Next action: 133 Actions raised at this meeting No Action Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 12/05: Work still progressing 02/06: Work still progressing on technical and legal considerations ... 25/08: Will chase to allow Daffodil access to test cases. The WG should define how implementation confirm that they 'conform to DFDL v1' 01/09: IBM still progressing the legal aspect. Intends to publish 100 or so tests as soon as it can, ahead of a full compliance suite. 08/09: IBM still progressing 15/09: IBM still progressing, expect tests to be available within a few weeks 22/09: IBM still progressing, expect tests to be available within a few weeks 29/09:Test cases are being prepared. 06/10: Some test cases should be available next week. Steve would like to be able to show the test case information at OGF 30. 13/10: Still progressing 10/11: Legal issues cleared, IBM in process of collecting 100 example test cases, ideally ones that fit the 'extended conformance' of NCSA Daffodil 17/11: Work is progressing on verifying the test cases. It should be possible to distribute to the WG in 2 weeks. 24/11: About half the test cases have been completed and are being reviewed internally. 01/12: Test cases should be available shortly 08/12: The test cases are in internal IBM review. Probably need a bit of reorganising before publication Stephanie gave a brief overview of the format of the test cases. 15/12: Ruth joined the call to provide the latest status. The test cases have been updated and a draft read.me produced. Although not ready for public distribution Ruth will send them to Joe for feedback. 22/12: Test cases were sent to Joe for initial testing which found some problems in the Daffodil parser 111 Daffodil DFDL parser 11/08: Bob and Alejandro described the new implementation that they have developed. It is a new code base and is not based on the Deffudle prototype. It is written in scala and implements approximately 80% of the features in the public comments draft of DFDL V1. Alejandro will send a list of the features not implemented. We discussed the scenarios that motivated the development which was to extract data from various sources and transform into canonical formats. Bob offered to make Daffodil available for the WG to assess the functionality. IBM WG members will get approval the company to allow them to receive Daffodil. Bob raised the question that if Daffodil becomes the public implementation of DFDL then we will need to work out how that would be funded and managed. It would be helpful if IBM test cases were available to Daffodil. IBM will investigate 25/08: Alejandro had sent a list of the functions that he has implemented and Steve ahd responding indicating the extra functions he thought were essential. Since then Alejandro has implemented some of the missing functions, such as escape schemes, pre-defined variables, binary decimal numbers, etc, and will update his list. Bob is planning to make the parser available on the internet to allow testing. His organisation is being reorganised and he doesn't know what the priority of Daffodill will be so it is essential that we move quickly. It would help if IBM could indicate its support for Daffodil in some semi-formal way. 01/09: Alejandro updating Daffodil to include escape schemes, unordered sequences and ignoreCase. Daffodil being placed under formal source control in anticipation of external release. Bob has a start October deadline to create a report on what has been done for his sponsors. It would be great if we could get Daffodil on the web and have run some IBM tests so it could be highlighted at OGF 30 at end October. 08/09: Alejandro is marking up Spec draft 42 to indicate which features Daffodil implement. Bob expects Daffodil to be available on the web soon. 15/09: Alejandro had indicated in the specification which functions were implemented in Daffodill. Steve had reviewed and identified which function need to be implemented and which could be considered optional (see action 099). Alejandro is implementing the missing core functions. There was some discussion about the limitations on unordered groups. (stop value and expression not supported). It was agreed that it should be a schema definition error if dfdl:occursCountKind is 'stopValue' on any element within an unordered sequence and a floating element. 22/09: not discussed 29/09: not discussed 06/10: Alejandro has left NCSA. Bob is making the case for continuing and having a replacement. Bob to agree with Steve what can be said at OGF30. 13/10: Bob still progressing project funding and making Daffodil publically available. 10/11: NCSA internal & sponsor (US National Archive in Washington DC - Electronic Records Administration) reviews passed. NCSA have new resource allocated - Joe Futrelle. Bob has started open source paperwork. ETA end December. 17/11: Joe has started coming up to speed with Daffodil. Bob is waiting for signoff from the university to open source the code. 24/11: not discussed 01/12: Joe is becoming familiar with the code. Waiting for university to give permission to make available. 08/12: Disclosure process in progressing. Bob has permission to make the web page available so hopefully that will be soon. The US National Archive have an article on their website about DFDL. Unfortunately it is a little out of date. 15/12: Hope to get permission to make the source code available within days. Web demo page will be available when resources have been identified. 22/12: An internal demonstration web page has been made available. Initial testing highlight some problems. Joe investigating. 112 DFDL certification process 25/08: Discussed how to certify DFDL implementations. Alan to investigate if OGF have a defined process. 01/09: In progress, spec needs to state what conformance means, as part of this work 08/09: Discussed what needs to be said in the spec and agreed that details of a conformance test suite should be in another document. Alan to draft conformance section. 15/09: Alan had look at the conformance sections in XML and Schema specifications both of which indicate sections which must be implemented. None just say 'execute the test suite'. They talk in terms of conformance of document, schema and processors.. 22/09: no progress 22/09: Alan has added short Conformance and Optional Features sections to spec which was briefly discussed. Discussed naming for processors that don't implement optional features and those that implement all features. 06/10: Need to decide what/how test cases and certification process should occur 13/10: no progress ... 08/12: no progress 15/12: no progress 22/12: no progress 123 DFDL tutorial 13/10: Draft of first 3 chapters has been written and will be distributed to WG 10/11: Posted to grid forge here ( http://forge.gridforum.org/sf/go/doc16106?nav=1) work continuing at IBM to define a standard example-based chapter framework and to author additional chapters. Contributors welcome! 17/11: Steve, Stephanie and Alan had a meeting to discuss the best structure for the tutorial and decide which examples to use throughout. The meeting raised more questions. Further discussions will be held. 24:11: The list of topics to be covered in the remaining lessons has been produced and a lesson template. Alan will write lesson 4 01/12: Alan has started lesson 4 which covers fixed and variable fields and arrays. 08/12: Alan has almost completed lesson 4. Will send out for review. 15/12: First draft of lesson 4 is available for review. Alan to send to Bob and Joe. 22/12: Alan has distributed drafts for tutorials on Basic Structure and Optional/Repeating elements. Please review 124 DFDL web content on OGF standards pages 13/10: no progress 10/11: no progress 17/11: Alan has looked at the OGF web pages and there aren't many standards listed. Some of the links point to very short primers rather than the specification 08/12: Alan to produce some information to be ready for when spec is approved. Still no word about is it was discussed/approved at OGF meeting 15/12: no progress 22/12: Steve has developed a summary web page for DFDL which will be sent to OGF when spec is approved. 129 Press release to publicise DFDL Steve is pulling together a press release at IBM. Want to include as many contributors and interested parties as possible.NCSA are keen to be included. Also likely that US National Archive will want to be included. Mike has indicated OCO are too. 17/11: no progress 08/12: Still no response from IBM press office 15/12: no progress 22/12: no progress 131 Transformation of dfdl properties to a canonical form 08/12: Joe has produced a XSLT to transform a DFDL schema to a canonical element form. When tested it should be made available on the WG gidforge site. 15/12: Alan tested against test dfdl schema which worked correctly (after fixing some errors in the schema) 22/12: no update 132 Publishing DFDL xsd 08/12: Agreed that it should be made available. Suman has started the approval process in IBM 15/12: no progress 22/12: no update Closed actions No Action Work items: No Item target version status 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

DFDL Boolean properties
by Alan Powell 22 Dec '10

22 Dec '10

Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com ----- Forwarded by Alan Powell/UK/IBM on 21/12/2010 17:44 ----- From: Joe Futrelle <futrelle(a)ncsa.uiuc.edu> To: Alan Powell/UK/IBM@IBMGB Cc: "Robert E. McGrath" <remcgrat(a)illinois.edu> Date: 21/12/2010 17:01 Subject: Re: [DFDL-WG] Agenda for OGF DFDL WG call 22 December 2010 15:00UK I have another issue for the WG. A number of annotation properties are in effect booleans, but they're declared as enums of {yes,no}. Why are they not represented as XSD booleans? I raise this because in various XML-based standards, extra work will have to be done to convert these values to booleans. For example, XPath and XQuery provide a number of boolean functions that operate on xs:boolean, and declare what is called the "effective boolean value" of a value that is not of type xs:boolean. Unfortunately, the effective boolean value of "no" is true: http://www.w3.org/TR/xpath20/#id-ebv -- Joe Futrelle Cyberenvironments and Technologies National Center for Supercomputing Applications http://www.ncsa.uiuc.edu/People/futrelle ----- Original Message ----- > 1. Current Actions > > 2. QName does not allow empty space > Change property type of dfdl:escapeSchemeRef, dfdl:hiddenGroupRef and > dfdl:prefixeLengthType to QName or empty Space > > 3. DFDL namespace URI > Should the DFDL namespace URI be changed to > http://www.ogf.org/dfdl/dfdl-1.0 / (add trailing /) > > 4. Status of OGF DFDL V1 review > OGF concerns related to confusion over IBM patents. IBM has clarified > that no patents need to be declared > > 5. AOB > - Next call Jan 5th 2011. > > > Current Actions: > No Action > > 066 Investigate format for defining test cases > 25/11:IBM to see if it is possible to publish its test case format. > 04/12: no update > ... > 17/02: IBM is willing in principle to publish the test case format and > some of the test cases. May need some time to build a 'compliance > suite' > 24/03: No progress > 03/03: Discussions have been taking place on the subset of tests that > will be provided. > 10/03: work is progressing > 17/03: work is progressing > 31/03: work is progressing > 14/04: And XML test case format has been defined and is being tested. > 21/04. Schema for TDML defined. Need to define how this and the test > cases will be made public > 05/05: Work still progressing > 12/05: Work still progressing > 02/06: Work still progressing on technical and legal considerations > ... > 25/08: Will chase to allow Daffodil access to test cases. The WG > should define how implementation confirm that they 'conform to DFDL > v1' > 01/09: IBM still progressing the legal aspect. Intends to publish 100 > or so tests as soon as it can, ahead of a full compliance suite. > 08/09: IBM still progressing > 15/09: IBM still progressing, expect tests to be available within a > few weeks > 22/09: IBM still progressing, expect tests to be available within a > few weeks > 29/09:Test cases are being prepared. > 06/10: Some test cases should be available next week. Steve would like > to be able to show the test case information at OGF 30. > 13/10: Still progressing > 10/11: Legal issues cleared, IBM in process of collecting 100 example > test cases, ideally ones that fit the 'extended conformance' of NCSA > Daffodil > 17/11: Work is progressing on verifying the test cases. It should be > possible to distribute to the WG in 2 weeks. > 24/11: About half the test cases have been completed and are being > reviewed internally. > 01/12: Test cases should be available shortly > 08/12: The test cases are in internal IBM review. Probably need a bit > of reorganising before publication > Stephanie gave a brief overview of the format of the test cases. > 15/12: Ruth joined the call to provide the latest status. The test > cases have been updated and a draft read.me produced. Although not > ready for public distribution Ruth will send them to Joe for feedback. > > 111 Daffodil DFDL parser > 11/08: Bob and Alejandro described the new implementation that they > have developed. It is a new code base and is not based on the Deffudle > prototype. It is written in scala and implements approximately 80% of > the features in the public comments draft of DFDL V1. Alejandro will > send a list of the features not implemented. > We discussed the scenarios that motivated the development which was to > extract data from various sources and transform into canonical > formats. > Bob offered to make Daffodil available for the WG to assess the > functionality. IBM WG members will get approval the company to allow > them to receive Daffodil. > Bob raised the question that if Daffodil becomes the public > implementation of DFDL then we will need to work out how that would be > funded and managed. > It would be helpful if IBM test cases were available to Daffodil. IBM > will investigate > 25/08: Alejandro had sent a list of the functions that he has > implemented and Steve ahd responding indicating the extra functions he > thought were essential. > Since then Alejandro has implemented some of the missing functions, > such as escape schemes, pre-defined variables, binary decimal numbers, > etc, and will update his list. > Bob is planning to make the parser available on the internet to allow > testing. > His organisation is being reorganised and he doesn't know what the > priority of Daffodill will be so it is essential that we move quickly. > It would help if IBM could indicate its support for Daffodil in some > semi-formal way. > 01/09: Alejandro updating Daffodil to include escape schemes, > unordered sequences and ignoreCase. > Daffodil being placed under formal source control in anticipation of > external release. > Bob has a start October deadline to create a report on what has been > done for his sponsors. > It would be great if we could get Daffodil on the web and have run > some IBM tests so it could be highlighted at OGF 30 at end October. > 08/09: Alejandro is marking up Spec draft 42 to indicate which > features Daffodil implement. Bob expects Daffodil to be available on > the web soon. > 15/09: Alejandro had indicated in the specification which functions > were implemented in Daffodill. Steve had reviewed and identified which > function need to be implemented and which could be considered optional > (see action 099). Alejandro is implementing the missing core > functions. There was some discussion about the limitations on > unordered groups. (stop value and expression not supported). It was > agreed that it should be a schema definition error if > dfdl:occursCountKind is 'stopValue' on any element within an unordered > sequence and a floating element. > 22/09: not discussed > 29/09: not discussed > 06/10: Alejandro has left NCSA. Bob is making the case for continuing > and having a replacement. Bob to agree with Steve what can be said at > OGF30. > 13/10: Bob still progressing project funding and making Daffodil > publically available. > 10/11: NCSA internal & sponsor (US National Archive in Washington DC - > Electronic Records Administration) reviews passed. NCSA have new > resource allocated - Joe Futrelle. Bob has started open source > paperwork. ETA end December. > 17/11: Joe has started coming up to speed with Daffodil. Bob is > waiting for signoff from the university to open source the code. > 24/11: not discussed > 01/12: Joe is becoming familiar with the code. Waiting for university > to give permission to make available. > 08/12: Disclosure process in progressing. Bob has permission to make > the web page available so hopefully that will be soon. > The US National Archive have an article on their website about DFDL. > Unfortunately it is a little out of date. > 15/12: Hope to get permission to make the source code available within > days. Web demo page will be available when resources have been > identified. > > 112 DFDL certification process > 25/08: Discussed how to certify DFDL implementations. Alan to > investigate if OGF have a defined process. > 01/09: In progress, spec needs to state what conformance means, as > part of this work > 08/09: Discussed what needs to be said in the spec and agreed that > details of a conformance test suite should be in another document. > Alan to draft conformance section. > 15/09: Alan had look at the conformance sections in XML and Schema > specifications both of which indicate sections which must be > implemented. None just say 'execute the test suite'. They talk in > terms of conformance of document, schema and processors.. > 22/09: no progress > 22/09: Alan has added short Conformance and Optional Features sections > to spec which was briefly discussed. Discussed naming for processors > that don't implement optional features and those that implement all > features. > 06/10: Need to decide what/how test cases and certification process > should occur > 13/10: no progress > ... > 08/12: no progress > 15/12: no progress > > 123 DFDL tutorial > 13/10: Draft of first 3 chapters has been written and will be > distributed to WG > 10/11: Posted to grid forge here ( > http://forge.gridforum.org/sf/go/doc16106?nav=1 ), work continuing at > IBM to define a standard example-based chapter framework and to author > additional chapters. Contributors welcome! > 17/11: Steve, Stephanie and Alan had a meeting to discuss the best > structure for the tutorial and decide which examples to use > throughout. The meeting raised more questions. Further discussions > will be held. > 24:11: The list of topics to be covered in the remaining lessons has > been produced and a lesson template. Alan will write lesson 4 > 01/12: Alan has started lesson 4 which covers fixed and variable > fields and arrays. > 08/12: Alan has almost completed lesson 4. Will send out for review. > 15/12: First draft of lesson 4 is available for review. Alan to send > to Bob and Joe. > > 124 DFDL web content on OGF standards pages > 13/10: no progress > 10/11: no progress > 17/11: Alan has looked at the OGF web pages and there aren't many > standards listed. Some of the links point to very short primers rather > than the specification > > 08/12: Alan to produce some information to be ready for when spec is > approved. Still no word about is it was discussed/approved at OGF > meeting > 15/12: no progress > > 129 Press release to publicise DFDL > Steve is pulling together a press release at IBM. Want to include as > many contributors and interested parties as possible.NCSA are keen to > be included. Also likely that US National Archive will want to be > included. Mike has indicated OCO are too. > 17/11: no progress > > 08/12: Still no response from IBM press office > 15/12: no progress > > 131 Transformation of dfdl properties to a canonical form > 08/12: Joe has produced a XSLT to transform a DFDL schema to a > canonical element form. When tested it should be made available on the > WG gidforge site. > 15/12: Alan tested against test dfdl schema which worked correctly > (after fixing some errors in the schema) > > 132 Publishing DFDL xsd > 08/12: Agreed that it should be made available. Suman has started the > approval process in IBM > 15/12: no progress > > > Regards > > > Alan Powell > > Development - MQSeries, Message Broker, ESB > IBM Software Group, Application and Integration Middleware Software > ------------------------------------------------------------------------------------------------------------------------------------------- > IBM > MP211, Hursley Park > Hursley, SO21 2JN > United Kingdom > Phone: +44-1962-815073 > e-mail: alan_powell(a)uk.ibm.com > > > > > > > > > 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 > > > > > > > > -- > dfdl-wg mailing list > dfdl-wg(a)ogf.org > http://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

2 1

Agenda for OGF DFDL WG call 22 December 2010 15:00UK
by Alan Powell 21 Dec '10

21 Dec '10

1. Current Actions 2. QName does not allow empty space Change property type of dfdl:escapeSchemeRef, dfdl:hiddenGroupRef and dfdl:prefixeLengthType to QName or empty Space 3. DFDL namespace URI Should the DFDL namespace URI be changed to http://www.ogf.org/dfdl/dfdl-1.0/ (add trailing /) 4. Status of OGF DFDL V1 review OGF concerns related to confusion over IBM patents. IBM has clarified that no patents need to be declared 5. AOB - Next call Jan 5th 2011. Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 12/05: Work still progressing 02/06: Work still progressing on technical and legal considerations ... 25/08: Will chase to allow Daffodil access to test cases. The WG should define how implementation confirm that they 'conform to DFDL v1' 01/09: IBM still progressing the legal aspect. Intends to publish 100 or so tests as soon as it can, ahead of a full compliance suite. 08/09: IBM still progressing 15/09: IBM still progressing, expect tests to be available within a few weeks 22/09: IBM still progressing, expect tests to be available within a few weeks 29/09:Test cases are being prepared. 06/10: Some test cases should be available next week. Steve would like to be able to show the test case information at OGF 30. 13/10: Still progressing 10/11: Legal issues cleared, IBM in process of collecting 100 example test cases, ideally ones that fit the 'extended conformance' of NCSA Daffodil 17/11: Work is progressing on verifying the test cases. It should be possible to distribute to the WG in 2 weeks. 24/11: About half the test cases have been completed and are being reviewed internally. 01/12: Test cases should be available shortly 08/12: The test cases are in internal IBM review. Probably need a bit of reorganising before publication Stephanie gave a brief overview of the format of the test cases. 15/12: Ruth joined the call to provide the latest status. The test cases have been updated and a draft read.me produced. Although not ready for public distribution Ruth will send them to Joe for feedback. 111 Daffodil DFDL parser 11/08: Bob and Alejandro described the new implementation that they have developed. It is a new code base and is not based on the Deffudle prototype. It is written in scala and implements approximately 80% of the features in the public comments draft of DFDL V1. Alejandro will send a list of the features not implemented. We discussed the scenarios that motivated the development which was to extract data from various sources and transform into canonical formats. Bob offered to make Daffodil available for the WG to assess the functionality. IBM WG members will get approval the company to allow them to receive Daffodil. Bob raised the question that if Daffodil becomes the public implementation of DFDL then we will need to work out how that would be funded and managed. It would be helpful if IBM test cases were available to Daffodil. IBM will investigate 25/08: Alejandro had sent a list of the functions that he has implemented and Steve ahd responding indicating the extra functions he thought were essential. Since then Alejandro has implemented some of the missing functions, such as escape schemes, pre-defined variables, binary decimal numbers, etc, and will update his list. Bob is planning to make the parser available on the internet to allow testing. His organisation is being reorganised and he doesn't know what the priority of Daffodill will be so it is essential that we move quickly. It would help if IBM could indicate its support for Daffodil in some semi-formal way. 01/09: Alejandro updating Daffodil to include escape schemes, unordered sequences and ignoreCase. Daffodil being placed under formal source control in anticipation of external release. Bob has a start October deadline to create a report on what has been done for his sponsors. It would be great if we could get Daffodil on the web and have run some IBM tests so it could be highlighted at OGF 30 at end October. 08/09: Alejandro is marking up Spec draft 42 to indicate which features Daffodil implement. Bob expects Daffodil to be available on the web soon. 15/09: Alejandro had indicated in the specification which functions were implemented in Daffodill. Steve had reviewed and identified which function need to be implemented and which could be considered optional (see action 099). Alejandro is implementing the missing core functions. There was some discussion about the limitations on unordered groups. (stop value and expression not supported). It was agreed that it should be a schema definition error if dfdl:occursCountKind is 'stopValue' on any element within an unordered sequence and a floating element. 22/09: not discussed 29/09: not discussed 06/10: Alejandro has left NCSA. Bob is making the case for continuing and having a replacement. Bob to agree with Steve what can be said at OGF30. 13/10: Bob still progressing project funding and making Daffodil publically available. 10/11: NCSA internal & sponsor (US National Archive in Washington DC - Electronic Records Administration) reviews passed. NCSA have new resource allocated - Joe Futrelle. Bob has started open source paperwork. ETA end December. 17/11: Joe has started coming up to speed with Daffodil. Bob is waiting for signoff from the university to open source the code. 24/11: not discussed 01/12: Joe is becoming familiar with the code. Waiting for university to give permission to make available. 08/12: Disclosure process in progressing. Bob has permission to make the web page available so hopefully that will be soon. The US National Archive have an article on their website about DFDL. Unfortunately it is a little out of date. 15/12: Hope to get permission to make the source code available within days. Web demo page will be available when resources have been identified. 112 DFDL certification process 25/08: Discussed how to certify DFDL implementations. Alan to investigate if OGF have a defined process. 01/09: In progress, spec needs to state what conformance means, as part of this work 08/09: Discussed what needs to be said in the spec and agreed that details of a conformance test suite should be in another document. Alan to draft conformance section. 15/09: Alan had look at the conformance sections in XML and Schema specifications both of which indicate sections which must be implemented. None just say 'execute the test suite'. They talk in terms of conformance of document, schema and processors.. 22/09: no progress 22/09: Alan has added short Conformance and Optional Features sections to spec which was briefly discussed. Discussed naming for processors that don't implement optional features and those that implement all features. 06/10: Need to decide what/how test cases and certification process should occur 13/10: no progress ... 08/12: no progress 15/12: no progress 123 DFDL tutorial 13/10: Draft of first 3 chapters has been written and will be distributed to WG 10/11: Posted to grid forge here ( http://forge.gridforum.org/sf/go/doc16106?nav=1) work continuing at IBM to define a standard example-based chapter framework and to author additional chapters. Contributors welcome! 17/11: Steve, Stephanie and Alan had a meeting to discuss the best structure for the tutorial and decide which examples to use throughout. The meeting raised more questions. Further discussions will be held. 24:11: The list of topics to be covered in the remaining lessons has been produced and a lesson template. Alan will write lesson 4 01/12: Alan has started lesson 4 which covers fixed and variable fields and arrays. 08/12: Alan has almost completed lesson 4. Will send out for review. 15/12: First draft of lesson 4 is available for review. Alan to send to Bob and Joe. 124 DFDL web content on OGF standards pages 13/10: no progress 10/11: no progress 17/11: Alan has looked at the OGF web pages and there aren't many standards listed. Some of the links point to very short primers rather than the specification 08/12: Alan to produce some information to be ready for when spec is approved. Still no word about is it was discussed/approved at OGF meeting 15/12: no progress 129 Press release to publicise DFDL Steve is pulling together a press release at IBM. Want to include as many contributors and interested parties as possible.NCSA are keen to be included. Also likely that US National Archive will want to be included. Mike has indicated OCO are too. 17/11: no progress 08/12: Still no response from IBM press office 15/12: no progress 131 Transformation of dfdl properties to a canonical form 08/12: Joe has produced a XSLT to transform a DFDL schema to a canonical element form. When tested it should be made available on the WG gidforge site. 15/12: Alan tested against test dfdl schema which worked correctly (after fixing some errors in the schema) 132 Publishing DFDL xsd 08/12: Agreed that it should be made available. Suman has started the approval process in IBM 15/12: no progress Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Fw: FYI, progress on test cases
by Alan Powell 20 Dec '10

20 Dec '10

Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com ----- Forwarded by Alan Powell/UK/IBM on 20/12/2010 08:13 ----- From: Joe Futrelle <futrelle(a)ncsa.uiuc.edu> To: Alan Powell/UK/IBM@IBMGB Cc: "Robert E. McGrath" <remcgrat(a)illinois.edu> Date: 17/12/2010 17:34 Subject: FYI, progress on test cases (Alan, this is also for the WG, or whoever is interested) Regrettably, Daffodil is failing 100% of the test cases that I received this week. This primarily results from the fact that Daffodil currently does not implement section 8.1 "Providing defaults for DFDL properties" and I believe that feature is used in every test case. I will need to implement that; in the meantime, I am trying to get our annotation parser to recognize all the annotations in the test cases without incorrectly flagging them as schema definition errors, and I'm running into numerous places where Alejandro's code appears to be slightly behind the spec, or where he has made minor and easily-correctable misspellings (e.g., "supress" instead of "suppressed"), etc. Daffodil also doesn't handle empty string refs properly in at least one case, which is how I ran into the "QName and empty string" issue. -- Joe Futrelle Cyberenvironments and Technologies National Center for Supercomputing Applications http://www.ncsa.uiuc.edu/People/futrelle 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

Broadcast: OGF DFDL Working Group weekly call (12 Jan 15:00 GMT in Hursley DE2J18/UK/IBM)
by Steve Hanson 16 Dec '10

16 Dec '10

Note new 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.

1 0

Broadcast: OGF DFDL Working Group weekly call (22 Dec 15:00 GMT in Participant Passcode: 8190865 )
by Steve Hanson 16 Dec '10

16 Dec '10

Extra call, being the last call for 2010.

1 0

Minutes for OGF DFDL Working Group Call, 15 December 2010
by Alan Powell 15 Dec '10

15 Dec '10

Open Grid Forum: Data Format Description Language Working Group OGF DFDL Working Group Call, 15 December 2010 Attendees Stephanie Fetzer (IBM) Steve Hanson (IBM) Alan Powell (IBM) Bob McGrath (NCSA) Joe Futrelle (NCSA) Ruth Wiegand (IBM) Apologies Tim Kimber(IBM) Suman Kalia (IBM) 1. Current Actions Updated below. 2. Confirm that array stopValue is not part on the infoset. For computability with the array being end by a literal terminator the stopValue should not be part of the infoset 3. Additional separatorPolicy? Currently: required all separators must be found when parsing and will be output when unparsing suppressedAtEndStrict trailing missing element separators must not be found when parsing and will not be output when unparsing suppressedAtEndLax trailing missing element separators may be found when parsing and will not be output when unparsing suppressed missing element separators may be found when parsing and will not be output when unparsing Take a user who is tolerant as to whether separators need to be present when parsing, but wants them output when unparsing. We can't support that. It needs the application of 'lax' to 'required'. The use case was not thought common so will not be included in DFDL v1. 4. Status of OGF DFDL V1 review Comment from review There are some concerns about potential intellectual property claims and licensing, which the standards council would prefer are resolved prior to publication. We have not been able to find out what the concerns are but will continue to pursue. 5. AOB - Next call Jan 5th 2011? Decided to have a call next week (22 Dec) Meeting closed, 15:45 Next call Wednesday 22 December 2010 15:00 UK (10:00 ET) Next action: 133 Actions raised at this meeting No Action Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 12/05: Work still progressing 02/06: Work still progressing on technical and legal considerations ... 25/08: Will chase to allow Daffodil access to test cases. The WG should define how implementation confirm that they 'conform to DFDL v1' 01/09: IBM still progressing the legal aspect. Intends to publish 100 or so tests as soon as it can, ahead of a full compliance suite. 08/09: IBM still progressing 15/09: IBM still progressing, expect tests to be available within a few weeks 22/09: IBM still progressing, expect tests to be available within a few weeks 29/09:Test cases are being prepared. 06/10: Some test cases should be available next week. Steve would like to be able to show the test case information at OGF 30. 13/10: Still progressing 10/11: Legal issues cleared, IBM in process of collecting 100 example test cases, ideally ones that fit the 'extended conformance' of NCSA Daffodil 17/11: Work is progressing on verifying the test cases. It should be possible to distribute to the WG in 2 weeks. 24/11: About half the test cases have been completed and are being reviewed internally. 01/12: Test cases should be available shortly 08/12: The test cases are in internal IBM review. Probably need a bit of reorganising before publication Stephanie gave a brief overview of the format of the test cases. 15/12: Ruth joined the call to provide the latest status. The test cases have been updated and a draft read.me produced. Although not ready for public distribution Ruth will send them to Joe for feedback. 111 Daffodil DFDL parser 11/08: Bob and Alejandro described the new implementation that they have developed. It is a new code base and is not based on the Deffudle prototype. It is written in scala and implements approximately 80% of the features in the public comments draft of DFDL V1. Alejandro will send a list of the features not implemented. We discussed the scenarios that motivated the development which was to extract data from various sources and transform into canonical formats. Bob offered to make Daffodil available for the WG to assess the functionality. IBM WG members will get approval the company to allow them to receive Daffodil. Bob raised the question that if Daffodil becomes the public implementation of DFDL then we will need to work out how that would be funded and managed. It would be helpful if IBM test cases were available to Daffodil. IBM will investigate 25/08: Alejandro had sent a list of the functions that he has implemented and Steve ahd responding indicating the extra functions he thought were essential. Since then Alejandro has implemented some of the missing functions, such as escape schemes, pre-defined variables, binary decimal numbers, etc, and will update his list. Bob is planning to make the parser available on the internet to allow testing. His organisation is being reorganised and he doesn't know what the priority of Daffodill will be so it is essential that we move quickly. It would help if IBM could indicate its support for Daffodil in some semi-formal way. 01/09: Alejandro updating Daffodil to include escape schemes, unordered sequences and ignoreCase. Daffodil being placed under formal source control in anticipation of external release. Bob has a start October deadline to create a report on what has been done for his sponsors. It would be great if we could get Daffodil on the web and have run some IBM tests so it could be highlighted at OGF 30 at end October. 08/09: Alejandro is marking up Spec draft 42 to indicate which features Daffodil implement. Bob expects Daffodil to be available on the web soon. 15/09: Alejandro had indicated in the specification which functions were implemented in Daffodill. Steve had reviewed and identified which function need to be implemented and which could be considered optional (see action 099). Alejandro is implementing the missing core functions. There was some discussion about the limitations on unordered groups. (stop value and expression not supported). It was agreed that it should be a schema definition error if dfdl:occursCountKind is 'stopValue' on any element within an unordered sequence and a floating element. 22/09: not discussed 29/09: not discussed 06/10: Alejandro has left NCSA. Bob is making the case for continuing and having a replacement. Bob to agree with Steve what can be said at OGF30. 13/10: Bob still progressing project funding and making Daffodil publically available. 10/11: NCSA internal & sponsor (US National Archive in Washington DC - Electronic Records Administration) reviews passed. NCSA have new resource allocated - Joe Futrelle. Bob has started open source paperwork. ETA end December. 17/11: Joe has started coming up to speed with Daffodil. Bob is waiting for signoff from the university to open source the code. 24/11: not discussed 01/12: Joe is becoming familiar with the code. Waiting for university to give permission to make available. 08/12: Disclosure process in progressing. Bob has permission to make the web page available so hopefully that will be soon. The US National Archive have an article on their website about DFDL. Unfortunately it is a little out of date. 15/12: Hope to get permission to make the source code available within days. Web demo page will be available when resources have been identified. 112 DFDL certification process 25/08: Discussed how to certify DFDL implementations. Alan to investigate if OGF have a defined process. 01/09: In progress, spec needs to state what conformance means, as part of this work 08/09: Discussed what needs to be said in the spec and agreed that details of a conformance test suite should be in another document. Alan to draft conformance section. 15/09: Alan had look at the conformance sections in XML and Schema specifications both of which indicate sections which must be implemented. None just say 'execute the test suite'. They talk in terms of conformance of document, schema and processors.. 22/09: no progress 22/09: Alan has added short Conformance and Optional Features sections to spec which was briefly discussed. Discussed naming for processors that don't implement optional features and those that implement all features. 06/10: Need to decide what/how test cases and certification process should occur 13/10: no progress ... 08/12: no progress 15/12: no progress 123 DFDL tutorial 13/10: Draft of first 3 chapters has been written and will be distributed to WG 10/11: Posted to grid forge here ( http://forge.gridforum.org/sf/go/doc16106?nav=1) work continuing at IBM to define a standard example-based chapter framework and to author additional chapters. Contributors welcome! 17/11: Steve, Stephanie and Alan had a meeting to discuss the best structure for the tutorial and decide which examples to use throughout. The meeting raised more questions. Further discussions will be held. 24:11: The list of topics to be covered in the remaining lessons has been produced and a lesson template. Alan will write lesson 4 01/12: Alan has started lesson 4 which covers fixed and variable fields and arrays. 08/12: Alan has almost completed lesson 4. Will send out for review. 15/12: First draft of lesson 4 is available for review. Alan to send to Bob and Joe. 124 DFDL web content on OGF standards pages 13/10: no progress 10/11: no progress 17/11: Alan has looked at the OGF web pages and there aren't many standards listed. Some of the links point to very short primers rather than the specification 08/12: Alan to produce some information to be ready for when spec is approved. Still no word about is it was discussed/approved at OGF meeting 15/12: no progress 129 Press release to publicise DFDL Steve is pulling together a press release at IBM. Want to include as many contributors and interested parties as possible.NCSA are keen to be included. Also likely that US National Archive will want to be included. Mike has indicated OCO are too. 17/11: no progress 08/12: Still no response from IBM press office 15/12: no progress 131 Transformation of dfdl properties to a canonical form 08/12: Joe has produced a XSLT to transform a DFDL schema to a canonical element form. When tested it should be made available on the WG gidforge site. 15/12: Alan tested against test dfdl schema which worked correctly (after fixing some errors in the schema). Some minor changes are needed to cope with non standard namespace prefixes 132 Publishing DFDL xsd 08/12: Agreed that it should be made available. Suman has started the approval process in IBM 15/12: no progress Closed actions No Action Work items: No Item target version status 042 Mapping of the DFDL infoset to XDM none not required for V1 specification 070 Write DFDL primer 071 Write test cases. Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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

Agenda for OGF DFDL WG call 15 December 2010 15:00UK
by Alan Powell 14 Dec '10

14 Dec '10

1. Current Actions 2. Confirm that array stopValue is not part on the infoset. 3. Additional separatorPolicy? Currently: required all separators must be found when parsing and will be output when unparsing suppressedAtEndStrict trailing missing element separators must not be found when parsing and will not be output when unparsing suppressedAtEndLax trailing missing element separators may be found when parsing and will not be output when unparsing suppressed missing element separators may be found when parsing and will not be output when unparsing Take a user who is tolerant as to whether separators need to be present when parsing, but wants them output when unparsing. We can't support that. It needs the application of 'lax' to 'required'. 4. Status of OGF DFDL V1 review Comment from review There are some concerns about potential intellectual property claims and licensing, which the standards council would prefer are resolved prior to publication. 5. AOB - Next call Jan 5th 2011? Current Actions: No Action 066 Investigate format for defining test cases 25/11:IBM to see if it is possible to publish its test case format. 04/12: no update ... 17/02: IBM is willing in principle to publish the test case format and some of the test cases. May need some time to build a 'compliance suite' 24/03: No progress 03/03: Discussions have been taking place on the subset of tests that will be provided. 10/03: work is progressing 17/03: work is progressing 31/03: work is progressing 14/04: And XML test case format has been defined and is being tested. 21/04. Schema for TDML defined. Need to define how this and the test cases will be made public 05/05: Work still progressing 12/05: Work still progressing 02/06: Work still progressing on technical and legal considerations ... 25/08: Will chase to allow Daffodil access to test cases. The WG should define how implementation confirm that they 'conform to DFDL v1' 01/09: IBM still progressing the legal aspect. Intends to publish 100 or so tests as soon as it can, ahead of a full compliance suite. 08/09: IBM still progressing 15/09: IBM still progressing, expect tests to be available within a few weeks 22/09: IBM still progressing, expect tests to be available within a few weeks 29/09:Test cases are being prepared. 06/10: Some test cases should be available next week. Steve would like to be able to show the test case information at OGF 30. 13/10: Still progressing 10/11: Legal issues cleared, IBM in process of collecting 100 example test cases, ideally ones that fit the 'extended conformance' of NCSA Daffodil 17/11: Work is progressing on verifying the test cases. It should be possible to distribute to the WG in 2 weeks. 24/11: About half the test cases have been completed and are being reviewed internally. 01/12: Test cases should be available shortly 08/12: The test cases are in internal IBM review. Probably need a bit of reorganising before publication Stephanie gave a brief overview of the format of the testcases. 111 Daffodil DFDL parser 11/08: Bob and Alejandro described the new implementation that they have developed. It is a new code base and is not based on the Deffudle prototype. It is written in scala and implements approximately 80% of the features in the public comments draft of DFDL V1. Alejandro will send a list of the features not implemented. We discussed the scenarios that motivated the development which was to extract data from various sources and transform into canonical formats. Bob offered to make Daffodil available for the WG to assess the functionality. IBM WG members will get approval the company to allow them to receive Daffodil. Bob raised the question that if Daffodil becomes the public implementation of DFDL then we will need to work out how that would be funded and managed. It would be helpful if IBM test cases were available to Daffodil. IBM will investigate 25/08: Alejandro had sent a list of the functions that he has implemented and Steve ahd responding indicating the extra functions he thought were essential. Since then Alejandro has implemented some of the missing functions, such as escape schemes, pre-defined variables, binary decimal numbers, etc, and will update his list. Bob is planning to make the parser available on the internet to allow testing. His organisation is being reorganised and he doesn't know what the priority of Daffodill will be so it is essential that we move quickly. It would help if IBM could indicate its support for Daffodil in some semi-formal way. 01/09: Alejandro updating Daffodil to include escape schemes, unordered sequences and ignoreCase. Daffodil being placed under formal source control in anticipation of external release. Bob has a start October deadline to create a report on what has been done for his sponsors. It would be great if we could get Daffodil on the web and have run some IBM tests so it could be highlighted at OGF 30 at end October. 08/09: Alejandro is marking up Spec draft 42 to indicate which features Daffodil implement. Bob expects Daffodil to be available on the web soon. 15/09: Alejandro had indicated in the specification which functions were implemented in Daffodill. Steve had reviewed and identified which function need to be implemented and which could be considered optional (see action 099). Alejandro is implementing the missing core functions. There was some discussion about the limitations on unordered groups. (stop value and expression not supported). It was agreed that it should be a schema definition error if dfdl:occursCountKind is 'stopValue' on any element within an unordered sequence and a floating element. 22/09: not discussed 29/09: not discussed 06/10: Alejandro has left NCSA. Bob is making the case for continuing and having a replacement. Bob to agree with Steve what can be said at OGF30. 13/10: Bob still progressing project funding and making Daffodil publically available. 10/11: NCSA internal & sponsor (US National Archive in Washington DC - Electronic Records Administration) reviews passed. NCSA have new resource allocated - Joe Futrelle. Bob has started open source paperwork. ETA end December. 17/11: Joe has started coming up to speed with Daffodil. Bob is waiting for signoff from the university to open source the code. 24/11: not discussed 01/12: Joe is becoming familiar with the code. Waiting for university to give permission to make available. 08/12: Disclosure process in progressing. Bob has permission to make the web page available so hopefully that will be soon. The US National Archive have an article on their website about DFDL. Unfortunately it is a little out of date. 112 DFDL certification process 25/08: Discussed how to certify DFDL implementations. Alan to investigate if OGF have a defined process. 01/09: In progress, spec needs to state what conformance means, as part of this work 08/09: Discussed what needs to be said in the spec and agreed that details of a conformance test suite should be in another document. Alan to draft conformance section. 15/09: Alan had look at the conformance sections in XML and Schema specifications both of which indicate sections which must be implemented. None just say 'execute the test suite'. They talk in terms of conformance of document, schema and processors.. 22/09: no progress 22/09: Alan has added short Conformance and Optional Features sections to spec which was briefly discussed. Discussed naming for processors that don't implement optional features and those that implement all features. 06/10: Need to decide what/how test cases and certification process should occur 13/10: no progress ... 08/12: no progress 123 DFDL tutorial 13/10: Draft of first 3 chapters has been written and will be distributed to WG 10/11: Posted to grid forge here ( http://forge.gridforum.org/sf/go/doc16106?nav=1) work continuing at IBM to define a standard example-based chapter framework and to author additional chapters. Contributors welcome! 17/11: Steve, Stephanie and Alan had a meeting to discuss the best structure for the tutorial and decide which examples to use throughout. The meeting raised more questions. Further discussions will be held. 24:11: The list of topics to be covered in the remaining lessons has been produced and a lesson template. Alan will write lesson 4 01/12: Alan has started lesson 4 which covers fixed and variable fields and arrays. 08/12: Alan has almost completed lesson 4. Will send out for review. 124 DFDL web content on OGF standards pages 13/10: no progress 10/11: no progress 17/11: Alan has looked at the OGF web pages and there aren't many standards listed. Some of the links point to very short primers rather than the specification 08/12: Alan to produce some information to be ready for when spec is approved. Still no word about is it was discussed/approved at OGF meeting 129 Press release to publicise DFDL Steve is pulling together a press release at IBM. Want to include as many contributors and interested parties as possible.NCSA are keen to be included. Also likely that US National Archive will want to be included. Mike has indicated OCO are too. 17/11: no progress 08/12: Still no response from IBM press office 131 Transformation of dfdl properties to a canonical form 08/12: Joe has produced a XSLT to transform a DFDL schema to a canonical element form. When tested it should be made available on the WG gidforge site. 132 Publishing DFDL xsd 08/12: Agreed that it should be made available. Suman has started the approval process in IBM Regards Alan Powell Development - MQSeries, Message Broker, ESB IBM Software Group, Application and Integration Middleware Software ------------------------------------------------------------------------------------------------------------------------------------------- IBM MP211, Hursley Park Hursley, SO21 2JN United Kingdom Phone: +44-1962-815073 e-mail: alan_powell(a)uk.ibm.com 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