Next in thread → Next in month →

RE: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.

From
Schnabel, Bryan S <>
Date
2013-12-13T19:56:10+00:00
ID
Thread
RE: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.
Oh, right. Makes sense. So I guess we’ve cleared CFD. Ryan has given me the go-ahead to make the updates.

 

From: Dr. David Filip [mailto:]

Sent: Friday, December 13, 2013 10:25 AM

To: Schnabel, Bryan S

Cc: Dr. David Filip; Yves Savourel; 

Subject: Re: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.

 

By resulting I mean the same what you mean, i.e. correcting the mistake and replacing <xliff> with <file> in the set of elements, where the module is to be allowed..

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

http://www.cngl.ie/profile/?i=452

mailto: 


 

On Fri, Dec 13, 2013 at 5:21 PM, Schnabel, Bryan S <> wrote:

Yes, again I misfired. I agree the right elements to allow ctr are "**<file>**, <group> and <unit>"
 not "in **<xliff>**, <group> and <unit>."

 

That was a typo on my part.

 

But David I don’t understand “this module should be explicitly allowed on the resulting set of elements.”

 

Can you elaborate, or let me know if this changes my proposal?

 

From: Dr. David Filip [mailto:]

Sent: Tuesday, December 10, 2013 2:20 PM

To: Yves Savourel

Cc: Schnabel, Bryan S; 


Subject: Re: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.

 

I agree with Yves and also agree that this module should be explicitly allowed on the resulting set of elements

Rgds

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

http://www.cngl.ie/profile/?i=452

mailto:


 

On Tue, Dec 10, 2013 at 9:04 PM, Yves Savourel <> wrote:

Hi Bryan, Ryan, all,

I'm guessing you meant "in **<file>**, <group> and <unit>" not "in **<xliff>**, <group> and <unit>".

<xliff> has no extension point for elements (and we wouldn't want anything in <xliff> but <file> anyway).

Right?

Cheers,

-yves

-----Original Message-----

From:  [mailto:] On Behalf Of Schnabel, Bryan S

Sent: Tuesday, December 10, 2013 1:39 PM

To: 

Subject: [xliff] [csprd02 139] CFD: Propose Change Track is allowed on <xliff>, <group>, and <unit>.

Hello,

Ryan and I propose Change Track is allowed on <xliff>, <group>, and <unit>.

This proposal is independent of the issues around modules vs. core in schema, and order of elements (core vs. modules).

If I do not hear dissent by the end of the week I will assume this proposal approved.

Thanks,

Bryan

---------------------------------------------------------------------

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:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

---------------------------------------------------------------------

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:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Next in thread → Next in month →