W3C home > Mailing lists > Public > public-change@w3.org > March 2013

RE: Fwd: A sort of synthesis

From: Dennis E. Hamilton <dennis.hamilton@acm.org>
Date: Fri, 8 Mar 2013 12:40:29 -0800
To: <public-change@w3.org>
Message-ID: <003c01ce1c3d$2c5f50f0$851df2d0$@acm.org>
I think the injection of externally-held change-tracking is an interesting situation.  

Processors that attempt to merge the information in some way will have to be resilient with respect to situations where the subject XML document is not consistent with the one the changes were introduced for.  

It seems to me that the key issue is how the external material specifies where the tracked changes apply in the subject XML document.  Perhaps the closest highly-rigorous case is external application of XML Digital signatures to (parts of) an XML document.  

Verrrry Interrrresting.

 - Dennis

-----Original Message-----
From: Robin LaFontaine [mailto:robin.lafontaine@deltaxml.com] 
Sent: Friday, March 08, 2013 09:31
To: public-change@w3.org
Subject: Re: Fwd: A sort of synthesis

+1 also for George, but there are use cases where external is useful, as Claudius says. This view was expressed too when we presented the paper in Prague. 

I am hoping we can get the best of both worlds by having both in-line and external representations and a standard transformation between them. As George says, the in-line is more 'robust' and should probably be the normative version, but we can discuss how to do that.

On 28/02/2013 17:27, Casey Jordan wrote:

	+1 George. This is a very important part of interoperability since there are so many "XML editors". As you know, many companies have groups using several tools on one content set. 

	On Thu, Feb 28, 2013 at 10:12 AM, George Cristian Bina <george@oxygenxml.com> wrote:

		Just a comment on this: 

		On 2/28/13 4:40 PM, Claudius Teodorescu wrote:

			4. rendering of changes, by using a light syntax (PIs, for instance);
			such syntax is to be used for rendering only, thus not over-loading the
			XML document itself;

		In oXygen's case, and I guess also in other XML tools, the PIs are not a syntax for rendering the changes, it is only a serialization format. Once the document is loaded the PIs are removed from the document and kept in an in-memory structure that is modified by the user actions and then when the document is saved the new current change tracking structure is serialized as PIs.
		There should not me a main issue if changes are stored out of band, in an external storage and loaded from there. However, having them separate from the document may easily result in inconsistent information. The main advantage with having them serialized directly in the document is that if some additional changes are performed with a tool that does not record changes on that document then the PIs will move as well so they will stay next to the content they mark as modified.
		Best Regards,
		George Cristian Bina
		<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger

	Casey Jordan
	easyDITA a product of Jorsek LLC
	"CaseyDJordan" on LinkedIn, Twitter & Facebook
	(585) 348 7399
	This message is intended only for the use of the Addressee(s) and may
	contain information that is privileged, confidential, and/or exempt from
	disclosure under applicable law.  If you are not the intended recipient,
	please be advised that any disclosure  copying, distribution, or use of
	the information contained herein is prohibited.  If you have received
	this communication in error, please destroy all copies of the message,
	whether in electronic or hard copy format, as well as attachments, and
	immediately contact the sender by replying to this e-mail or by phone.
	Thank you.

-- -----------------------------------------------------------------
Robin La Fontaine, Director, DeltaXML Ltd  "Experts in information change"
T: +44 1684 592 144  E: robin.lafontaine@deltaxml.com      
Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK
Received on Friday, 8 March 2013 20:41:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:11:22 UTC