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

["Dr. David Filip" <David.Filip@ul.ie>]

Peter, it is too bad that you were not around when the ambiguous and badly worded sample liaison mandate was discussed and voted on. You are of course free to provide much better description of the SC5 liaison mandate.

I do not find your proposal simple at all. You ask that the whole TC becomes SC5 liaison member. I am afraid this is not possible as per OASIS liaison policy. AFAIK, working liaisons can be formed on the basis of individuals with double membership. OASIS has a fast track submitter status at ISO and, according to your explanation, this basically means that the SC5 review of our spec can happen at the same time as the public review of our XLIFF TC spec (once the TC decides to push the Committee Draft to Committee Spec).

Finally, if you think that P&L SC is slowing down your progress with this liaison, you are free as any other TC member to propose to Bryan a TC agenda point. I am however afraid that the TC will not be able to decide the matter of your proposal, as I find it not only ambiguous and badly worded, but totally absent.

This can of course be my issue, so please bear with me.

Could you please answer the following questions?

1) Do you want to represent XLIFF TC on ISO TC 37 SC5?

2) What will be your goal as our liaison at SC5

What will be your means and responsibilities in order to achieve that goal?

How often will you report on your progress back to the P&L SC

What support from the SC and/or TC do you need to achieve the goal

etc. Whatever seems relevant in order to effectively decide the matter in 5-10min of the TC time

As I said before, I honestly do not know what to put in front of the TC based on your communications so far, but am more than happy to discuss the matter on the SC meeting Dec 18, 5pm GMT.

Thanks for your understanding, consideration, 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

mailto: david.filip@ul.ie

On Mon, Dec 10, 2012 at 5:53 PM, Peter Reynolds <p.reynolds@maart.pl> wrote:

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 

https://lists.oasis-open.org/archives/xliff/201204/msg00013.html

 

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

mailto: david.filip@ul.ie

 

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