XLIFF Inline Markup Subcommittee Teleconference - July-10-2012

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  Leave of absence: Andrew  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

--
Dropping original data storage inline. Original data would be stored only in <data> See  https://lists.oasis-open.org/archives/xliff-inline/201206/msg00009.html
-- canOverlap attribute New attribute to indicate whether the original code of an inline code can overlap or not. See  https://lists.oasis-open.org/archives/xliff-inline/201206/msg00010.html
-- composite values for the type attribute Something like this: type ::= <category>[' '<subcategory>] <subcategory> ::= <authority>'-'<value> Would allow a fixed set of categories and user-defined ones See  https://lists.oasis-open.org/archives/xliff-inline/201206/msg00011.html
-- using <sm>/<em> for non-well-formed <mrk> Instead of using multiple <mrk> we would use the same system of starting/ending standalone tags: See  https://lists.oasis-open.org/archives/xliff-inline/201207/msg00001.html
=== Bi-directionality details  Changes for bidi markup. See thread starting at:  https://lists.oasis-open.org/archives/xliff-inline/201207/msg00003.html
=== Annotations representation  ACTION ITEM: yves to work on implementation. -> in progress  ACTION ITEM: Yves to edit the draft to reflect the sm/em change -> waiting for confirmation of consensus
=== 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