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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

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

Subject: RE: [xliff] XLIFF Reference Implementation

Hi Yves/all,

From my point-of-view, answers amongst others depend on the definition
we choose for "Reference Implementation".
As sample definition is the following:


A key phrase here is "A reference implementation ... is a software
example of a specification". If I remember
the discussion we had during the TC call last week, we may have two
distinct dimensions in the XLIFF 2.0

1. a format description
2. a set of processing expectations related to the format

Tools for checking adherence to/compliance with a format description
from my understanding are somewhat related
to the format description and the formalism used to codify that
description. Example: If you codify with RelaxNG
you may be able to do other types of compliance checking than with XSD.

I am unsure whether the set of processing expectations should work along
the lines you sketch. From my understanding,
this would mean working towards an XLIFF-specific DOM/XLIFF processing
API specification.

One level down, you could say that not only an API specification will
be targeted but actually an implementation of that API/specification.
Next level of detail would answer questions such as: which development
model/source code repository, which programming language, which license


-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com] 
Sent: Saturday, March 07, 2009 11:57 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] XLIFF Reference Implementation


I've seen with delight that a reference implementation is planned for

The current notes indicate that it would contain validation tools.

1) Are we planning to perform this validation solely based on schema(s)
or do we also plan on processing in the documents and having
some direct checks that a schema could not perform?

2) If the answer to 1) is yes: Will the processing be a simple read, or
are we planning to actually hold the different parts of the
XLIFF documents in objects and access them through an API?


To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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