Change Tracking by Injection

Mohamed asked, in the thread below, what I meant by injection.
 
I meant by injection the introduction of change-tracking information by 
 
(1)     injecting material into an existing XML document that is not part of the document and does not make use of any already-specified extension mechanism for the application of the XML document. 
 
(2)     Having data entirely external to the XML document that projects changes onto the XML document without touching it directly.
 
In either case, the coupling is from the change-tracking material into the XML document and I view that as injecting the change-tracking into/onto the XML document.  It is external to the specification that applies to the application of the XML document.  The first case is essentially what happens with introduction of XML processing instructions, although placement of them makes proximity to an effected location in the XML document easier than the second case where pointing into the XML document to situate a change is more troublesome.
 
I don’t know that it is a specialized technical term.  It might be usefully defined as one.
 
-   Dennis
 
From: innovimax@gmail.com [mailto:innovimax@gmail.com] On Behalf Of Innovimax W3C
Sent: Sunday, September 21, 2014 03:11
To: Dennis Hamilton
Cc: public-change@w3.org
Subject: Re: Change Tracking Prolog Description
 
Dennis,
 
On Sat, Sep 20, 2014 at 8:25 PM, Dennis E. Hamilton <dennis.hamilton@acm.org <mailto:dennis.hamilton@acm.org> > wrote:
I am assuming that when change-tracking is dealt with in the document model and schema where XML documents are applied, having announcement of that fact in a prolog is not so meaningful, since schema and model awareness is required.
 
I don't think so. You can declare only the element required for change tracking understanding
 
  I wasn’t thinking about differences of serialization, but of cases where change-tracking is not by injection, however serialized, but is wired into the application document structure.  (I.e., the case with OOXML and ODF.)
 
Suppose that OOXML or ODF allows multiple ways to represent change tracking. Then you get the use case.
 
 
That comes back to a scope question.  If you mean this for what appear to be injection cases and that is the scope of this work, I understand.  Is that the scope?
 
can you expand on "injection" ? if this is a common terminology, I would be happy to add it to the wiki Terminology :  https://www.w3.org/community/change/wiki/Terminology
Regards,
Mohamed
 
(This leads to a question that I will raise separately.)
 
-   Dennis
 
From: innovimax@gmail.com <mailto:innovimax@gmail.com>  [mailto:innovimax@gmail.com <mailto:innovimax@gmail.com> ] On Behalf Of Innovimax W3C
Sent: Saturday, September 20, 2014 06:13
To: Dennis Hamilton
Cc: public-change@w3.org <mailto:public-change@w3.org> 
Subject: Re: Change Tracking Prolog Description
 
Dennis,
If you read the link you'll see that I try to separate the way the serialization of the result will be made
The <?change-tracking?> PI is there to allow ANY representation IN THE CONTENT
Hoping it helps understranding the scope

Mohamed
 
On Sat, Sep 20, 2014 at 2:57 PM, Dennis E. Hamilton <dennis.hamilton@acm.org <mailto:dennis.hamilton@acm.org> > wrote:
My feedback is I have no useful feedback on change-tracking at this level, especially if processing instructions are also used in the expression of the tracked changes.
 
This will not be very applicable in situations where change-tracking is handled within the schema for XML document that applies for the application in which the XML document is employed, the case where XML documents are employed internal to the representation of document files for OOXML and ODF, for example.
 
From: Innovimax SARL [mailto:innovimax@gmail.com <mailto:innovimax@gmail.com> ] 
Sent: Saturday, September 20, 2014 02:36
To: public-change@w3.org <mailto:public-change@w3.org> 
Subject: Change Tracking Prolog Description
 
Dear all,

I made a proposal to define a Change Tracking Prolog Description that 
* would help programs and people to understand what kind of change tracking content they have in hand 
* and if they are able to handle it (do validation for example)
It will looks like this (very rough proposal) and be present at the begining of the document
<?change-tracking type="pi" sub-type="simple"?>
 
<?change-tracking type="pi" sub-type="rdf-triple"?>
 
<?change-tracking type="element" sub-type="namespace-less" list-of-elements="diff ins"?>
 
<?change-tracking type="element" sub-type="namespace" target-namespace="http://w3.org/ns/ct"?>
 
I would like to see feedback here

Thanks

Mohamed



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787 <tel:%2B33%209%2052%20475787> 
Fax : +33 1 4356 1746 <tel:%2B33%201%204356%201746> 
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 € 



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787 <tel:%2B33%209%2052%20475787> 
Fax : +33 1 4356 1746 <tel:%2B33%201%204356%201746> 
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 € 



-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €