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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-promotion message

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


Subject: RE: Forming a Working Liaison with ISO TC37/SC5 to push XLIFF 2.0 as ISO standard


Hi David,

 

I sent you a proposal in August and resent it this month.

 

You asked me for more information and I sent you documents which explains the scope SC 5.  I can do what you ask but I do not agree that we have sent me is a good example. My proposal is quite simple. I am suggesting that the XLIFF TC requests to be a liaison member of ISO TC 37 SC5. I am afraid I find the example you give below ambiguous, badly worded and not relevant to this situation.

 

I would like us to move on this proposal immediately.

 

Best regards,

 

Peter.

 

 

From: Dr. David Filip [mailto:David.Filip@ul.ie]
Sent: Monday, December 10, 2012 15:12
To: Peter Reynolds; xliff-promotion
Subject: Forming a Working Liaison with ISO TC37/SC5 to push XLIFF 2.0 as ISO standard

 

Dear Peter,

 

please find linked a sample ballot by which the TC approved a working liaison, in this case 

 

I'd like to draw your attention to the concise mandate (scope and responsibilities) as copy-pasted down below.

 

Do you think that you could draft an post to the P&L SC a similar concise mandate for the ISO TC37/SC5 by the end of 2012, so that XLIFF TC can have ballot on this liaison in early 2013?

 

Thanks for your understanding and collaboration

dF

 

Dr. David Filip

=======================

LRC | CNGL | LT-Web | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

 

[sample mandate start]

 

This is a concise mandate for the liaison (to be used in an electronic ballot if seconded)

 

Scope (work on and facilitation of the following):

1.     XLIFF TC providing business requirements to MultilingualWeb-LT, so that semantic match between the standards is secured early on.

2.     Optionally, representation of  MultilingualWeb-LT metadata using XLIFF 1.2

1.     Having a "profile" or mutual understanding on the best practice

3.     Most importantly, both groups should strive to have native representation of  MultilingualWeb-LT metadata categories in XLIFF 2.0  

Responsibilities:

 

The liaison will report to the P&L SC, which in turn reports at least monthly to XLIFF TC.

The main duties of the liaison at MultilingualWeb-LT shall be:

1) Ensure that XLIFF TC viewpoint (localization roundtrip) is well represented during the requirements gathering. 

2) Follow up on queries and issues logged by XLIFF TC and its members to ensure that they are well addressed according to W3C WG process throughout draft, test suit, till final recommendation.

3) Identify and promote opportunities for common non-normative best practice notes. 

 

[sample mandate end]



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