Subject: RE: [xliff] RE: How do we refer to an external skeleton in XLIFF 2.0?
Good catch David. Sorry that I hadn’t noticed that before.
I don’t mind your solution.
But it seems a bit odd to me that if I’m interested in information about an external skeleton I need to know to look at the <file> element, but if I’m interested in information about an internal skeleton I need to know to look at the <skeleton> element. This confusion is exacerbated by the fact that in XLIFF 1.2 each case was supported in the <skl> element.
So I guess my (not passionate) vote would be to leave the @href on <skeleton>, and remove the @skeleton from the <file> element.
From: Dr. David Filip [mailto:David.Filip@ul.ie]
Bryan, this seemed reasonable to me last week.
However, your proposal started with the question how do we refer to an external skeleton in XLIFF 2.0
And looking at the spec today I figured, there was a way to point to external skeleton even before your skeleton attribute was introduced.
So now we unfortunately have two totally analogical mechanisms for pointing to an external skeleton..
- skeleton attribute on file, which exludes usage of the skeleton element
- ahref attribute on skeleton that forces the skeleton attribute to be empty.
I guess this can only create confusion. It would force people to look for the external skeleton at two places and would introduce a superfluous dilemma for implementers.
I actually do not care which of the two mechanisms we keep, I just guess we should keep only one.
I propose to roll back the new attribute on skeleton. I may add a note that external skeleton is being pointed to from file via the skeleton attribute.
I would also make the skeleton attribute value an IRI rather than text.
@Everyone, please let me know if this seems OK, or if you prefer it the other way round, eventually if you have a use case that would support having the mechanism at both levels..
Dr. David Filip
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
On Tue, Apr 2, 2013 at 1:50 PM, Dr. David Filip <David.Filip@ul.ie> wrote:
Dr. David Filip
On Tue, Mar 26, 2013 at 5:09 PM, Schnabel, Bryan S <firstname.lastname@example.org> wrote:
To: Schnabel, Bryan S; email@example.com
Subject: [xliff] RE: How do we refer to an external skeleton in XLIFF 2.0?