Re: Relationship with other groups (was Re: Eating our own dog food (Was: Generic Change Tracking draft spec))

Dear all,



On Fri, Jul 26, 2013 at 3:57 PM, Robin LaFontaine <
robin.lafontaine@deltaxml.com> wrote:

>  Liam raises the point about other groups - perhaps there are members of
> this group who are also involved with those groups and could help with
> that?
>
> 1. HTML5
> I believe our primary goal is XML but it would be very good to be
> applicable to HTML5 also. As part of other work we are looking at HTML5
> and processing it as XML to detect changes, but we are not yet far enough
> along that road to comment.
>

Indeed any tree representation could be targeted by change tracking. This
should then appear in the
https://www.w3.org/community/change/wiki/Use_cases_and_requirements
So please proceed

>
> 2. Efficient XML Interchange (EXI)
> I would very much hope we would be fully compatible with EXI because we will
> conform to XML - is there anyone who could comment in more depth on this?
>

I don't see how EXI would be a problem here, since EXI is fully XML
compliant. We can definitely add a requirement to be compatible with EXI in
the Use Case & Requirements document, but I don't see more burden here.

>
> 3. XPath changes to give a 'time axis' to XML per XML Prague paper
> From my recollection of this paper, the idea was to provide a time axis
> to an XML document, so you could query it as it was at a particular
> time/version. My initial thought is that this could require a fair bit of
> processing though might theoretically be possible. It would be necessary to
> work out the state of the document at the specified time which means
> reversing the changes made back to that point - could be done! The
> information is there but the format is not designed for that type of
> query.
>

I don't see us have the ability to change XPath just by asking.
But what we can definitely do, is writing a spec related to that and try to
see the implication. It may then be accepted by the XSLT & XQuery WG as a
Note that people could implement in a more standard way (without it being
mandatory : same as the namespace axis)


Mohamed


>
> Robin
>
> -- -----------------------------------------------------------------
> Robin La Fontaine, Director, DeltaXML Ltd  "Experts in information change"
> T: +44 1684 592 144  E: robin.lafontaine@deltaxml.com      http://www.deltaxml.com
> Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK
>
> On 12/04/2013 21:55, Liam R E Quin wrote:
>
> On Fri, 2013-04-12 at 08:58 -0700, Dennis E. Hamilton wrote:
>
>  The difference between Community Group products and W3C Working Group
> products (and other aspects) are summarized nicely at<http://www.w3.org/community/about/agreements/compare/> <http://www.w3.org/community/about/agreements/compare/>.
>
> Community Groups do not produce W3C Specifications or other Standards Track documents.
>
>  The idea is that community groups can provide input to Working Groups,
> so that if there was enough traction - e.g. several W3C Members or (more
> excitingly to the W3C staff perhaps) several companies or organizations
> that would join to do the work :-), we'd charter a new Working Group.
>
> But that Working Group could start with what was done here, and might be
> able to proceed quickly.
>
> Useful things to consider - relationship of the work to HTML 5/HTML.ng;
> relationship of the work to Efficient XML Interchange (EXI); whether
> changes to XPath would be appropriate, like the experiments with a
> revision history / time XPath axis presented at XML Prague a year or two
> ago.
>
> Liam
>
>
>
>


-- 
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 €