Hi Yves, My 7am call might end after 39 min. Would it be disruptive if I joined late? - Bryan ________________________________________ From:
xliff-inline@lists.oasis-open.org [
xliff-inline@lists.oasis-open.org] On Behalf Of Yves Savourel [
ysavourel@enlaso.com] Sent: Monday, November 07, 2011 3:48 AM To:
xliff-inline@lists.oasis-open.org Subject: [xliff-inline] Inline Markup Teleconference XLIFF Inline Markup Subcommittee Teleconference Every second Tuesday of every month at 15:00 UTC 7:00am PT, 8:00am MT, 10:00am ET, 11:00 Montevideo, 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 The summary of our main items is here:
http://wiki.oasis-open.org/xliff/OneContentModel/Requirements Draft is under SVN, here:
http://tools.oasis-open.org/version-control/svn/xliff/trunk/inline-markup/ (this will be replaced by DocBook version soon) === 1.5. Must allow to associate spans of content with metadata Current proposed representation:
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html <mrk [id='id'] type='type' [value='some value'] [ref='someId'] [translate='yes no']>...</mrk> Yves had an action item to start test implementation. -> done. This leads to some question about overlapping representation.
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00022.html - what to do with isolated tag and non-well-formed annotation? -> possibly use <as>/<ea> type elements Other questions:
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00027.html - what about translate info without other info? Should type='trans' be mandatory? === Type of inline codes: A by-product of trying to resolve question about keeping or not <pc> led us to make a mapping table between 1.2 and 2.0. (Appendix in
http://tools.oasis-open.org/version-control/svn/xliff/trunk/inline-markup/ ) - need to handle isolated code (vs non-well-formed) -> possible isolated attribute for <sc>/<ec> and rid replaced by id for isolated <ec>. - do we need crc? - do we need assoc? === 1.16. Inline codes should have a way to store information about the effect on the segmentation See
http://lists.oasis-open.org/archives/xliff-inline/201109/msg00005.html === Keeping <pc> or not? Will need a resolution soon as it affect other decision like <mrk> vs <sa>/<ea>. === Bi-direction markers Several tools use Unicode characters in 1.2. Goes against W3C recommendation but seems common practice. -> need to know about other tools -> ask for info to W3C === Representation of added codes Need to clarify use of duplicated code. e.g. why not re-use same code? (See
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00021.html ) === Representation of editing hints Need to have notation for 'permissions' Last discussion:
http://lists.oasis-open.org/archives/xliff-inline/201106/msg00003.html === Any other business -end --------------------------------------------------------------------- To unsubscribe, e-mail:
xliff-inline-unsubscribe@lists.oasis-open.org For additional commands, e-mail:
xliff-inline-help@lists.oasis-open.org