- dfdl-wg - lists.ogf.org

Re: [dfdl-wg] DFDL Call tomorrow
by Jim Myers 11 Jan '06

11 Jan '06

FYI: Apologies, but I'll be on a plane tomorrow at conference time. Jim At 07:38 PM 1/10/2006, Westhead, Martin (Martin) wrote: >Preliminary Agenda >------------------ > > 1. Arranging a US F2F in January > 2. Reports from trackers > 3. Review Context document see attached. > >Sorry the document is going out so late. I >messed up when sending it out to the design team for final review. > >Also notice that I have added a URL and codes >for my Web conference facility. It has slide, >application sharing, and whiteboard space. I thought it might be useful. > >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. > >Web Conference: ><https://webconferencing.avaya.com/>https://webconferencing.avaya.com >Web Conference: Part. Code 785343; WebConf Reference 158672 > > > James D. Myers Associate Director, Collaborative Systems, NCSA 1205 W. Clark St, MC-257 Urbana, IL 61801 217-244-1934 jimmyers(a)ncsa.uiuc.edu

1 0

DFDL Call tomorrow
by Westhead, Martin (Martin) 11 Jan '06

11 Jan '06

Preliminary Agenda ------------------ 1. Arranging a US F2F in January 2. Reports from trackers 3. Review "Context" document - see attached. Sorry the document is going out so late. I messed up when sending it out to the design team for final review. Also notice that I have added a URL and codes for my Web conference facility. It has slide, application sharing, and whiteboard space. I thought it might be useful. 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. Web Conference: https://webconferencing.avaya.com <https://webconferencing.avaya.com/> Web Conference: Part. Code 785343; WebConf Reference 158672

1 0

FYI: xmlecho transformation scripting language
by Mike Beckerle 05 Jan '06

05 Jan '06

Kind of sparse, but conceptually related particularly to our extensibility and layering topics: http://www.xmlecho.org/ ...mikeb

1 0

Notes from Telcon 2006-1-4
by Westhead, Martin (Martin) 04 Jan '06

04 Jan '06

Present ------- Martin Westhead Tara Talbott Bob McGrath Steve Hanson Geoff Judd It was a short meeting this week. * Extensibility group - there is some material in progress that should be ready for wider circulation in a week or so. * Face-to-face - the idea of a face-to-face in North America this quarter was well received. The end of February seemed like a possible date. Location is undecided. Steve and Geoff will look into getting out here, particularly if they can combine the trip with an IBM implementation meeting. (I can definitely make a meeting in the Bay area if there was sufficient interest in that. I will find out in a couple of weeks if I can get a travel budget for my DFDL involvement. I am keen to try to get to this meeting). Martin

1 0

First telcon of 2006
by Martin Westhead 04 Jan '06

04 Jan '06

Agenda 1. Reports from tracker group 2. Possible face-to-face this quarter Talk to you tomorrow. Martin Conference call instructions: Time: 9am PST Number: 1-800-664-0771 At the automated answering system, press 0 for the operator. Ask for the "Daffodil working group" call.

2 1

Last telcon of 2005
by Westhead, Martin (Martin) 21 Dec '05

21 Dec '05

Present ------- Martin Westhead Tara Talbott Bob McGrath Steve Hanson Geoff Judd We discussed Geoff's document comparing properties and variables. Martin is working on a proposal to combine these concepts and is promising to produce a document shortly after the new year to outline these ideas. We heard a summary from Mike on the scoping proposal that IBM is working on. ***Note: there will be no telcon on December 28th*** (The next call will be January 4th) Merry Christmas/Happy Holidays! Martin

1 0

Telcon now
by Westhead, Martin (Martin) 21 Dec '05

21 Dec '05

Sorry for the late reminder. Martin 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

Properties and Variables
by Geoff Judd 21 Dec '05

21 Dec '05

Hi, I have attached a document the compares properties and variables It is intended to be used as the basis for a discussion at this afternoon's conference call. Regards, Geoff Judd Websphere MQ Integrator Development IBM UK Ltd Hursley Telephone: +44-1962-818461 E-mail: JUDDG(a)uk.ibm.com

1 0

Notes from telcon
by Westhead, Martin (Martin) 14 Dec '05

14 Dec '05

Present ------- Bob McGrath Martin Westhead Steve Hanson Geoff Judd Tara Talbott Items ----- 1. Planning for next GGF (February) I believe the deadline for meeting proposals is coming up soon. We need to get our act together and figure out our representation in Athens. At this point we do not have any definite attendees. Note: If no one can go it may be OK for us to skip this one? 2. Variable semantics Discussed the possible overlap between properties and variables. It is important to understand if there is a single mechanism that meets both requirements here. So can we meet the requirements of a variable with a user-defined property? Can we use the same scoping rules for both? 3. Ongoing review of tracker tasks Extensibility group is making progress, they had a good meeting last week and found a lot of opportunity with "hidden layer" semantics to help support read-modify-write cycles for DFDL.

1 0

RE: [dfdl-wg] Telcon Notes
by Westhead, Martin (Martin) 14 Dec '05

14 Dec '05

Hi Geoff, I'll certainly put this on the agenda. If anyone has anything else please let me know. Also some comments: 1. I'd like to understand how variables relate to parameters, specifically: a. Could we actually define variables to be user-defined parameters? (if not, why not?) b. If (a) doesn't work can we have variables use the same scoping rules as parameters? 2. In the extensibility group we have been talking about reference direction. It was proposed that XPaths in a DFDL document can only refer to elements higher up the document (i.e. backwards only) they cannot reference things below them (which will not yet have been parsed). With the use of "hidden layers" this can be done without loss of generality. I would suggest that variable references should work this way. I.e you are only allowed to refer to data that has already been parsed. Thanks, Martin _____ From: Geoff Judd [mailto:JUDDG@uk.ibm.com] Sent: Tuesday, December 13, 2005 9:34 AM To: Westhead, Martin (Martin) Cc: dfdl-wg(a)ggf.org Subject: Re: [dfdl-wg] Telcon Notes Martin, Please can you add a discussion of the semantics of DFDL Variables to the agenda of tomorrow's telecon. I have attached a document with some thoughts that I have had on the subject. Regards, Geoff Judd Websphere MQ Integrator Development IBM UK Ltd Hursley Telephone: +44-1962-818461 E-mail: JUDDG(a)uk.ibm.com "Westhead, Martin (Martin)" <westhead(a)avaya.com> Sent by: owner-dfdl-wg(a)ggf.org 30/11/2005 18:12 To <dfdl-wg(a)ggf.org> cc Subject [dfdl-wg] Telcon Notes Present ------- Mike Bekerle Tara Talbott Martin Westhead Geoff Judd Steve Hanson Bob McGrath Reports from Active Trackers ---------------------------- Scoping tracker is being worked on - no news. Extensibility group is moving forward - nothing to report yet Discussion of Geoff's documents ------------------------------- Variables doc Mike observed that variables could be used in place of his extensibility proposal on annotations. Martin asked about whether we wanted to include this in the standard. Is the complexity worth the addition - the feeling of the meeting was probably it was. Martin proposed that instead of binding a variable value to an element, the variable value should be set with an XPath expression. Discussed the question as to whether the variable value can be reset, whether it can/should be scoped in the same way as annotation attributes. Next step will be for Geoff to revise the document to look at cases where value may need to be reset and start to explore some of the semantic issues involved. Choices doc Discriminator type - what if discriminator is not a string? For efficiency can we handle discriminators that are integers? Suggest that instead of discriminators being computed to strings they are computed to an XPath value with its implied type so that numeric discriminators do need to be converted to strings. Wildcard docs Group seemed fairly happy with this proposal as it stands.

2 1