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] | [Elist Home]


Subject: RE: [xliff] Notes from face to face meeting


Hi all,

The correct attendees for day one of the face to face included Gerard and
John Reid and Mirek was present as an observer. Enda apologised.

Peter.

-----Original Message-----
From: Peter Reynolds [mailto:Peter.Reynolds@Berlitz.ie]
Sent: Thursday, May 09, 2002 2:00 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Notes from face to face meeting


Below are my notes from Today's meeting so far.

Peter.

Face to Face meeting Thursday
Attendence: Tony, John Corrigan, Merc, Matt, Yves, Christian, Peter,
Reinhard

Session 1 - XLIFF 1.1 Framework,  Vision  and Roadmap
Tony outlined what the group currently have.
	*	Spec complete
	*	Accepted as a committee spec
	*	DTD
	*	White paper
	*	naming conventions/ irregularities
	*	Too open (content openness/ data openness)

Vision
We discussed the different models of implementation and what has been done
with XLIFF to date

Localisation interchange model
Using XLIFF and Web Services any publisher can select any vendor. Open
system power with customer. 

XML Content Localisation
Oracle streamlining content localisation. Oracle tools can read specific
XLIFF file 'OraXLIFF'. 
Development structure

Novell getting some developers to hand over XLIFF.
Moving XLIFF up the value chain.

Tool neutral data container
	Choose vendors
	Add new tools
	Add vendors

Need for tool providers to support format. 

XLIFF being used for interchanging data between tools. All tools are XLIFF
aware. Single data format.

Tools need to be able to use XLIFF. 

Standard API could allow tools to use XLIFF more easily 
Namespaces could provide similar power

Different needs - Publishers/ Vendors/ Translators/ Tool providers

XLIFF is a capture localisation requirements and best practises. Template
for development.



Who's doing what
Oracle: OraXLIFF for Datawarehouse files
Berlitz: Special Olympics/ CMS
Alchemy Catalyst: support for XLIFF
Sun: working on tools
Lotus/ IBM: DGW working with Berlitz
Trados: support for XLIFF
RWS: Rainbow



 * Interchange 	- between file formats
		- between publishers and vendors
		- between tools
		
 * Interoperability

Single data format.

Development structure - Developers using XLIFF/ Use XLIFF early on in the
process/ Resource container

Tool neutral data container
	Choose vendors
	Add new tools
	Add vendors

Need for tool providers to support format. 

Tools need to be able to use XLIFF. 

Technology structure
		API 
		* Schema
* Namespaces 
* Formal extensibility 
Developer support for design and authoring


Different needs - Publishers/ Vendors/ Translators/ Tool providers

XLIFF is a capture localisation requirements and best practises. Template
for development.

Segmentation structured in a way that tools take advantage of it. (OSCAR)

* Uniformity of representation
Use existing standards
Granularity

The ability to mark up/ capture the data and pass it on to different options
at different stages without loss of that data.

Push XLIFF up stream in development process

* Spec naming conventions, structure refinements

* Backward compatibility/ Migration path

Interchange/ Interoperability
Spec naming conventions, structure refinements
Backward compatibility/ Migration path
Uniformity of representation
Formal extensibility 
Schema
Namespaces 




----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


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


Powered by eList eXpress LLC