RE: [xliff] XLIFF "domains"

["Lieske, Christian" <christian.lieske@sap.com>]

Hi Yves,

Thanks for the reply.

I understand your points but wonder how the constraints you mention (size and character set requirements) related to the "domains/processing" steps.

One possibility:

2. Internationalization 
	a. Mark "not translation relevant" 
	b. Create note 
	c. Determine/set size requirements
	d. Determine/set character set requirements
	e. ...
...
10. Technical QA checks
	a. Missing "target" after translation
	b. Check size requirements
	c. Check character set requirements
	d. ...

Since, however, not everyone would subsume something like "determine/set constraints" under "Internationalization", I could also imagine that we have an additional "domain" which for example could be called "Constraint Setting".

What do you think?

Cheers,
Christian

-----Original Message-----
From: Yves Savourel [mailto:ysavourel@translate.com] 
Sent: Dienstag, 7. September 2010 21:01
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] XLIFF "domains"

Hi Christian,

It looks like an interesting start.

Maybe also:

11. Size requirements
	a. max/min length in different units (1.2: maxbytes, minbytes, maxwidth, minwidth, etc.)
	b. max/min number of lines (1.2: maxheight, minheight)

12. Character set
	a. set of characters allowed or not (1.2: charclass)

-ys


-----Original Message-----
From: Lieske, Christian [mailto:christian.lieske@sap.com] 
Sent: Tuesday, September 07, 2010 8:16 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] XLIFF "domains"

Dear all,
 
Thanks to input from all of you (eg. in the mail thread on the "Minimal element tree" cf. http://lists.oasis-open.org/archives/xliff/201008/msg00012.html) I have been able to develop some initial ideas for the strawman proposal that is meant to fuel the panel on "Modular and minimal XLIFF" (according to our discussion in the TC; cf. http://lists.oasis-open.org/archives/xliff/201008/msg00010.html).
 
One common theme that I spotted was the desire to discuss XLIFF in terms of domains - you could also call it by a different name such as "layer" - which may show up in XLIFF-related processes. In order to elaborate on this, I wonder if you could have a look at the following domains, and suggest additions, different wording etc. Of course, any other feedback is also most welcome.

Best regards,
Christian
 
1. Extraction/Filtering (including reverse ie. insertion/merging) 
2. Internationalization 
	a. Mark "not translation relevant" 
	b. Create note 
	c. .
3. Automated Linguistic Processing 
	a. Segmentation 
	b. Automatic TM Leveraging 
	c. Machine Translation 
	d. Terminology identification/extraction
	e. Automated linguistic checking (spelling, grammar, style, terminology)
4. Human Translation 
	a. Creation of target text 
	b. Display, creation or annotation of notes 
	c. Special operations (eg. cloning) 
	d. .
5. Localization 
	a. Adaptation of control viewports
	b. Adaptation of URLs
	c. .
6. Reviewing 
	a. Insertion of annotations 
	b. Display, creation or annotation of notes
	c. .
7. Inclusion of reviewing results 
8. Workflow Events 
	a. Status updates 
9. Tool-specific Events 
	a. Trigger rendering
10. Technical QA checks
	a. Missing "target" after translation
	b. ...

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