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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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


Subject: Re: [xliff-comment] Re: csprd01-27 Resource Data Module Design


That's fine with me too.

Cheers -- Jörg

On Jule 19, 2013 at 20:00 (CEST), Ryan King wrote:
Yves is correct, the intention is to use href in <res:source>, <res:target>, <res:reference> to point to external resources. The ref attribute in  <res:resourceItemRef> is specifically to point to a <res:resourceItem> element.

Thanks,
Ryan

-----Original Message-----
From: Yves Savourel [mailto:yves@opentag.com]
Sent: Friday, July 19, 2013 4:00 AM
To: joerg@bioloom.de; Ryan King; xliff-comment@lists.oasis-open.org
Subject: RE: [xliff-comment] Re: csprd01-27 Resource Data Module Design

This proposal was intentionally (URI ref) to also permit external
resources. What about having both types (optionally)?

I see.

Then it's not the only change needed for this. The type of the <resourceData> id attribute would also need to change to ID and be unique per document.

But overall I'm not sure we could do this. <resourceData> is a descriptor of resources rather than a resource. So the URI would have to point to a standalone file with that element (or a list of those elements). Resources themselves can be externalized with href I think.

But Ryan would have a better view on what is doable or make sense.

Cheers,
-yves



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