XLIFF Inline Markup Subcommittee Teleconference - Sep-11-2012

[Yves Savourel <ysavourel@enlaso.com>]

XLIFF Inline Markup Subcommittee Teleconference

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

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


=== Confirming F2F main changes with members who couldn't attend the F2F

-- composite values for the type attribute
Something like this:

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

Or two attributes:

Like type and subType (or custType, or xType, or extType), with same values.

Need to define the values for the main category.


=== Bi-directionality details

Done in schema, specifications and test implementation (I think).



=== Annotations representation

ACTION ITEM: yves to work on implementation.
-> in progress

ACTION ITEM: Yves to edit the draft to reflect the sm/em change
-> Done.


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

Either enter suggestion in your column (add one if needed)
(ask for the link to the editable table if you don't have it any more, or post an email with the suggestions)


=== Namespace?

We need to decide to which namespace the content markup should belong.

- same as the core namespace
- one separate namespace (but still belong to the core)
- several separate namespaces (e.g. codes still belong to the core, but not annotations, etc.)


=== Any other business


-end