Custom XML on 4/8 WG4 Meeting

[Shawn Villaron]

That seems fair.  So let's do this.  We'll move Custom XML to 4/22 and we'll continue to take comments on the proposed responses until 4/16.  I'll ask Zeyad to reschedule to the 4/22 meeting.


From: Horton, Gareth [mailto:Gareth_Horton at datawatch.com]
Sent: Wednesday, April 07, 2010 5:12 AM
To: Shawn Villaron; Brown, Alex; e-SC34-WG4
Cc: Cave, Francis
Subject: RE: Custom XML on 4/8 WG4 Meeting

Shawn,

Alex is on vacation, so in the absence of any direction from him, let's postpone it.

Gareth
________________________________
From: Shawn Villaron <shawnv at microsoft.com>
Sent: 07 April 2010 12:58
To: Alex Brown <alexb at griffinbrown.co.uk>; SC 34 WG4 <e-SC34-WG4 at ecma-international.org>
Subject: RE: Custom XML on 4/8 WG4 Meeting
I never heard back from this request.  I'm inclined to push the Custom XML defect reports until the 4/22 meeting unless I hear otherwise.  We need to decide on this relatively quickly so I can let Zeyad know if he'll be needed during the 4/8 call.

Thanks,

shawn

From: Shawn Villaron
Sent: Tuesday, March 30, 2010 7:02 AM
To: 'Alex Brown'; SC 34 WG4
Subject: RE: Custom XML on 4/8 WG4 Meeting

Thanks, Alex, for this feedback.  It helps us determine what changes we need to make.  Both points sound reasonable.

Would you prefer that we move the Custom XML discussion to the conference call on the 22nd?  I think it is more important to have all of the key contributors available for resolving these defect reports than it is to have them resolved in the next two weeks.

Again, thanks for the feedback.

shawn
From: Alex Brown [mailto:alexb at griffinbrown.co.uk]
Sent: Tuesday, March 30, 2010 2:18 AM
To: Shawn Villaron; SC 34 WG4
Subject: RE: Custom XML on 4/8 WG4 Meeting

Dear Shawn, all,

I still think we need to deal with the issue of content defaulting while addressing these fixes, if only to say it is application dependent.

e.g.

"If, as a result of validation against a schema, the infoset of the extracted XML is modified, it is application-dependent whether these modifications are included in the extraction result."

This then makes this clear as an interop danger area.

And a minor point - we should not refer to this IS as "Open XML" ... that's for the marketing folks.

I will not be able to make the call on the 8th, as I will be on holiday.

- Alex.


From: Shawn Villaron [mailto:shawnv at microsoft.com]
Sent: 29 March 2010 18:57
To: SC 34 WG4
Subject: Custom XML on 4/8 WG4 Meeting
Importance: High

Good morning, afternoon and evening.

According to my count, we're down to just over 70 active defect reports.  I'd like to focus on the Custom XML defect reports for our next teleconference, April 8th.  I've asked Zeyad to attend the call as he is the subject matter expert for all things Custom XML.

In order to put ourselves in the best possible position to resolve the open Custom XML defect reports, I'd like to ask everyone to spend some time this week reading the attached document.  If you have questions, comments or concerns, please put them in the document or in email and send them to me.  We'll attempt to process all questions, comments and concerns that we received by EOD April 2nd in time for the teleconference.

The following defect reports are impacted by the attached document:

09-0207        GB      Request for clarification            Further Consideration Required            WML: Custom XML and Smart Tags
09-0208        GB      Request for clarification            Further Consideration Required            WML: Custom XML and Smart Tags
09-0210        GB      Technical defect                           Further Consideration Required            WML: Custom XML and Smart Tags
09-0211        GB      Technical defect                           Further Consideration Required            WML: Custom XML and Smart Tags
09-0213        GB      Technical defect                           Further Consideration Required            WML: Custom XML and Smart Tags

Time permitting, we're hoping to have a few more defect report responses ready for everyone, too.

Thank you.

shawn


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.vse.cz/pipermail/sc34wg4/attachments/20100407/30e967ec/attachment.htm>