Martin I think we also need to discuss to closure at the F2F: - What APIs to we expect DFDL implementations to provide to users - Which XML Schema constructs are supported - The set of DFDL properties we provide Regards, Steve Steve Hanson WebSphere Message Brokers, IBM Hursley, England Internet: smh@uk.ibm.com Phone (+44)/(0) 1962-815848 Geoff Judd/UK/IBM@IBMGB Sent by: To owner-dfdl-wg@ggf "Westhead, Martin (Martin)" .org <westhead@avaya.com> cc dfdl-wg@ggf.org, 26/01/2006 09:29 owner-dfdl-wg@ggf.org Subject Re: [dfdl-wg] Telcon notes 2006-1-25 Martin, In the discussion on contexts I would also like to include a discussion of variables and how they fit in with contexts. It may be that they are effectively the same concept but I would like a discussion to agree whether this is the case or not. I would like the agenda item 'Choices and defaults' split into 2 items: 1. Choices and wildcards 2. Null and default values Regards, Geoff Judd Websphere MQ Integrator Development IBM UK Ltd Hursley Telephone: +44-1962-818461 E-mail: JUDDG@uk.ibm.com "Westhead, Martin (Martin)" <westhead@avaya.com> Sent by: owner-dfdl-wg@ggf.org To <dfdl-wg@ggf.org 25/01/2006 18:16 > cc Subject [dfdl-wg] Telcon notes 2006-1-25 Please note: We need to agree a preliminary agenda for the F2F by the end of the week. Please take a look at the agenda at the end of this document and send comments/additions to the list. Our face-to-face time is limited, I am keen to try to direct our attention to strategy and big picture questions and leave details for the telcons. I propose to devote some call-time to each agenda item to fine-tune what the outstanding issues for discussion are. Present Geoff Judd Bob McGrath Tara Talbott Martin Westhead Suman Kalia Agenda 1. US F2F Logistics Meeting is set for 1-3 March in Milpitas. Agenda details are required urgently, for Suman’s travel request. 2. Reports from trackers Final extensibility documents presented. 3. Outstanding issues on hidden elements Discussion lead to the observations that: a) putting things into a global complex type appears to be the only way to avoid any possible name clash issues. b) We could restrict things to this, or document this as a best practice. Suman is in favour of restricting the language in order to avoid this problem. The issue remains open at this point. 4. Review “Bundles” document We did not get to this. 5. Review “Conversions” document We had an initial discussion on the conversions document. There were a lot of questions about motivations and the extent to which this proposal would change things. More discussion will be needed to bring the group to a common understanding of the proposal. Face-to-face agenda Conversions/context/hidden elements Scoping document Choices and defaults Actions to lead to a final document set.