OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oiic-formation-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oiic-formation-discuss] Canonicalizations galore

--- On Tue, 6/24/08, Dave Pawson <dave.pawson@gmail.com> wrote:

> From: Dave Pawson <dave.pawson@gmail.com>
> Subject: Re: [oiic-formation-discuss] Canonicalizations galore
> To: oiic-formation-discuss@lists.oasis-open.org
> Date: Tuesday, June 24, 2008, 1:36 PM
> 2008/6/24 jose lorenzo <hozelda@yahoo.com>:
> > What then, if any, might be the OIIC's initial set
> of deliverables/scope/etc in this area of
> canonicalizations/diffs/etc?
> Wording to require the TC to deliver a definition of c18N
> above and
> beyond w3c c18N, to include such as style variations
> and any other relevant considerations for the purposes of
> supporting
> interop testing.

I see. I should have also linked to this response in replying to Rob (http://lists.oasis-open.org/archives/oiic-formation-discuss/200806/msg00716.html ). The wording you provide here, in part, might be suitable to help define the scope and potential deliverables for the TC charter .. and without being too specific.

> > Perhaps based on demand for some of these things (a
> specific profile, a specific diff need, etc), work will be
> undertaken by outside groups in parallel to OIIC TC work
> and issues will be reported to the TC as they crop up. The
> TC can then consider how to add lubrication/order/etc to
> the process and submit requests of some sort to the main
> TC.
> That's doing the work. Our scope is defining what's
> to be done

Not sure what you mean specifically. By "lubrication" I mean doing things like helping standardize particular canonicalization algorithms. See this reply http://lists.oasis-open.org/archives/oiic-formation-discuss/200806/msg00717.html

I'd go further than with the reply you gave at the top.. or rather, I'd be less general, since standardizing such algorithms/mappings (and dealing with associated tid bits) is something that could be usefully done on an ongoing basis to address numerous market use cases (besides those of the ODF compliance tester). These use cases would make themselves known not all at once but over time (not to mention it takes time to implement any such std alg).


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]