- From: George Cristian Bina <george@oxygenxml.com>
- Date: Tue, 28 Feb 2012 16:30:04 +0200
- To: David Lee <David.Lee@marklogic.com>
- CC: Robin Berjon <robin@berjon.com>, "public-xml-er@w3.org Community Group" <public-xml-er@w3.org>
Hi David, You can watch the recorded panel that Robin referred to: http://www.youtube.com/watch?v=U5u5nT9_Vgc&list=PLA053B5F535B7CEE7&index=1&feature=plcp One of the complains of using XML on the web is the draconian error handling and some people find it a showstopper for some applications. Now, a browser for example is not necessary an XML processor, it is an XML application and it can decide to recover if what it was supposed to be XML turns out not to be XML (not well-formed). Instead of having each application recover in its own way it will be great to have that recovery mechanism defined somehow so that the users will get consistent behavior. This consistent behavior is important when we talk about similar applications, in this case web browsers. In this context creating a DOM is the actual usecase so I think that starting with defining how a DOM can be created should provide both the algorithm and one useful implementation. In oXygen for example, we have this kind of recovery implemented since 2003 - when you edit an XML, it is not well-formed while you edit it in text mode, but we still need to present its tree in the Outline view. It may not be really necessary for the tree that we present in the Outline to be the same as the DOM a browser will create from a not well-formed XML, I do not think many people will care if that will be different. However, if XML-ER will be finalized we will look to see if we can use the same recovery rules to create a similar tree in the Outline view - and that will be a different implementation than the one that creates a DOM. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 2/28/12 4:03 PM, David Lee wrote: > Ok that's the part I missed. I apologize for not being able to be at the conference but I am still vastly interested in this work. > > But please bear with my confusion ... > > Exactly what is that you want to build ? > A specification ? Of what ? An implementation ? of What ? > A proof of concept ? > > In business speak, what is the expected deliverable of this committee ? > > > > ----------------------------------------------------------------------------- > David Lee > Lead Engineer > MarkLogic Corporation > dlee@marklogic.com > Phone: +1 650-287-2531 > Cell: +1 812-630-7622 > www.marklogic.com > > This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. > > >> -----Original Message----- >> From: Robin Berjon [mailto:robin@berjon.com] >> Sent: Tuesday, February 28, 2012 8:58 AM >> To: David Lee >> Cc: public-xml-er@w3.org Community Group >> Subject: Re: It's probably me.. >> >> On Feb 28, 2012, at 14:50 , David Lee wrote: >>>> I'm with Mohamed on this one: let's build something and figure out if we >> like >>>> it once we've seen what it looks like. If we do, I have no doubt that we >> can >>>> find a nice home for it :) >>> >>> I',m all for that. But what is it you're going to build ? Thats all I'm asking ... >>> Maybe it doesnt matter ... >> >> The plan we had was to run with the proposal that Anne made in his talk at >> XML Prague, with the surrounding discussions taken into account. >> >> -- >> Robin Berjon - http://berjon.com/ - @robinberjon >> >> Coming up soon: I'm teaching a W3C online course on Mobile Web Apps >> http://www.w3devcampus.com/writing-great-web-applications-for-mobile/ > >
Received on Tuesday, 28 February 2012 14:30:41 UTC