RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Oct-09-2012 - Summary

[Yves Savourel <ysavourel@enlaso.com>]

XLIFF Inline Markup Subcommittee Teleconference - Summary
Oct-09-2012

Every second Tuesday of every month at 14:00 UTC 7:00am PT, 8:00am MT, 10:00am ET 3:00pm London, 4:00pm Berlin

Teleconference meeting place:
https://www1.gotomeeting.com/join/408998929
Meeting ID: 408-998-929
You can use the following US phone number, or the VOIP option provided by GoToMeeting:
Dial 630-869-1010
Access Code: 408-998-929

Present: Yves, Fredrik.
Regrets: Alan


Latest draft is here:
See http://tools.oasis-open.org/version-control/svn/xliff/trunk/xliff-20/xliff-core.pdf


=== type for inline codes

Composite values for the type attribute Something like this:

type ::= <category>['/'<subcategory>]
<subcategory> ::= <authority>':'<value>

ACTION ITEM: Jung will try to come up with an initial list of main types:
Done -> See here:
https://lists.oasis-open.org/archives/xliff-inline/201210/msg00000.html

Y: wonder about the 'bidi' type. really needed?
.. Bidi support exists inline
F: See some used cases where it may be used.

Y: Should we still go for composite values?
F: should try to keep number of attribute low.
Y: Ok, if needed change is not drastic.


=== fs attribute

Bryan has been working of the fs attribute since a while:
https://lists.oasis-open.org/archives/xliff-inline/201210/msg00006.html
and:
https://lists.oasis-open.org/archives/xliff-inline/201210/msg00008.html

F: probably should be a module
Y: agree
.. should be fine inline, as long as it makes sense overall.
F: agree.
.. seems more work than it was initially planned for.


=== Maximum length

Status from Fredrik (if needed)

F: try to get it done.
.. want it to be well defined



=== Elements and Attributes Names

Time to start choosing final names for the inline markup.

See spreadsheet here:
https://docs.google.com/spreadsheet/pub?key=0Av8I1YVQlYmsdEwtZ0VEVmo5Y0ZLTndEcUlFMzZnZmc&output=html

ACTION: Yves to resend the link to the editable page.


=== Any other business

Next meeting Nov-13.
(Not affected by difference in daylight time change date between US and Europe)

ACTION: Yves to make sure x- is changed in spec/schema.

F: Concern about re-segmentation and metaholder/extensions
.. Splitting especially:
.. Can't duplicate because if you split then merged you get different result.
.. will need processing expectations

Y: no extension in inline markup is holding up

F: we should have a central place for the PE, maybe? Currently it's all over the place.
Y: could probably do that.



-end