RE: Issue-55 - XLIFF mapping -

Hi Felix, Yves,

This solutions makes sense. I am assuming the namespace is applicable in both 
XLIFF 1.2 and 2.0. Is this correct?

Regards
Des



-----Original Message-----
From: Felix Sasaki [mailto:fsasaki@w3.org]
Sent: 04 March 2013 10:06
To: Yves Savourel
Cc: 'Dr. David Filip'; 'Sean Mooney'; 'David Lewis'; 
public-multilingualweb-lt@w3.org
Subject: Re: Issue-55 - XLIFF mapping -

Hi Yves, David, all,

I haven't yet checked W3C internally about the namespace hosting -
butYves solution sounds good to me. Would that work for everybody?

Best,

Felix

Am 01.03.13 14:54, schrieb Yves Savourel:
> Hi David, all,
>
> maybe there is no need for one after all.
>
> There is an "ITS Extension" namespace already 
> (http://www.w3.org/2008/12/its-extensions)
>
> This has been used for several years to markup extensions to ITS after 1.0, 
> trying to gather new features for 2.0.
> See for example: 
> http://www.w3.org/International/its/wiki/IssuesAndProposedFeatures
>
> So far I had not thought about this namespace as a place to specify the 
> "missing" parts for mapping to XLIFF and other formats, but thinking more 
> about it there is no reason that could be used for this.
>
> As long as the different elements and attributes are clearly defined and 
> have an explanation on where they should be used.
>
> cheers,
> -yves
>
>
> -----Original Message-----
> From: Dr. David Filip [mailto:David.Filip@ul.ie]
> Sent: Friday, March 01, 2013 6:38 AM
> To: Yves Savourel; Sean Mooney; Felix Sasaki; David Lewis
> Cc: public-multilingualweb-lt@w3.org
> Subject: Re: Issue-55 - XLIFF mapping -
>
> Yves, I agree the UL hosting of the namespace is of course just a stop gap 
> measure.
> We are happy and ready to hand over to W3C at any moment.
> @Felix, did you look into W3C hosting of the namespace? Did I miss it?
>
> Discussing it with Dave et al., we figured that other mappings might be in 
> need of similar extensions, Dave has some RDF related examples on the wiki.
> So the idea is to have itsx: and call it "ITS Extensions" and use it for any 
> extensions that are required for mapping into different vocabularies.
> Sean will circulate the URL and the initial xsd that we are going to use in 
> Rome. The xsd will be placed onto GitHub, so that others can contribute to 
> it until the namespace is taken over by W3C, and managed via a W3C process.
>
>
> 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
> mailto: david.filip@ul.ie
>
>
> On Fri, Mar 1, 2013 at 2:04 AM, Yves Savourel <ysavourel@enlaso.com> wrote:
>> Hi Dave, David, all,
>>
>> Last conference call I think David noted that UL was ready to host a
>> namespace URI for the extra namespace we need for the extra attributes
>> needed to cover the lack of direct mapping (the itsx namespace
>> described at
>> http://www.w3.org/International/multilingualweb/lt/wiki/XLIFF_Mapping)
>>
>> I think the real namespace should be hosted by either the W3C or by OASIS 
>> and it needs to be set up soon. We don't want to start generating XLIFF 
>> documents for production with a temporary namespace.
>>
>> cheers,
>> -yves
>>
>>
>>
>>
>