RE: [xliff-inline] Requirements - #8

["Dimitra.Anastasiou" <Dimitra.Anastasiou@ul.ie>]

Hi Yves,

Following up on the requirement 1.8, I think "content" alone does not suffice. It needs sth. else to be complete, maybe "segment"? I see what you mean with the example, maybe we can add an example in parentheses.
My supplements/suggestions are in capitals below:

"Must be able to identify uniquely an INLINE code within a content SEGMENT (<source> and/or <target> in XLIFF 1.2 or <seg> in TMX)"
"An inline code may be associated with metadata located outside the content SEGMENT. In order TO link together the code and its associated metadata, a way to identify the inline code uniquely within the content is needed."

What do you think?
Will we discuss also how we link it with the metadata or not? Sorry for asking, it is just not clear to me.

Regards,
Dimitra


-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com] 
Sent: 15 July 2010 19:05
To: xliff-inline@lists.oasis-open.org
Subject: [xliff-inline] Requirements - #8

Hi all,

As we discussed at the last teleconference: let's try to make some progress in the requirements.
We can discuss and propose changes by email, hopefully reaching a stage where we have a broad agreement. Then we can go through those items at the next teleconference and possibly close them quickly.

The next one on the list may be an easy one:

#8: Currently we have:
http://wiki.oasis-open.org/xliff/OneContentModel/Requirements

"Should be able to identify uniquely a code within a content fragment"
"As a code need to be associated to additional information within or outside its container, we need to be able to identify it uniquely. For example using unique ID per content, or unique type+ID, etc."

I would propose:

"Must be able to identify uniquely a code within a content"
"An inline code may be associated with metadata located outside the content. In order link together the code and its associated metadata a way to identify the code uniquely within the content is needed."

One question: I think here the scope of "content" is the element where the text is located (currently <source>, <target> in 1.2, or <seg> in TMX). I think it should be that way. But I'm not sure the wording expresses that properly.

-ys





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