[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Teleconference - Apr-12-2011
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 Duration: 1 hour You can use the following US phone number, or the VOIP option provided by GoToMeeting: Dial 630-869-1010 Access Code: 408-998-929 === 1) Admin Minutes of previous meeting: http://lists.oasis-open.org/archives/xliff-inline/201103/msg00001.html === 2) Discussion Requirement working page: http://wiki.oasis-open.org/xliff/OneContentModel/Requirements Markup options working page: http://wiki.oasis-open.org/xliff/OneContentModel/Comparison --- 2.1) Native data representation in inline Thread on the native data representation: http://lists.oasis-open.org/archives/xliff-inline/201011/msg00001.html ACTION ITEM: Christian to contact Felix Sasaki and Richard Ishida about additional suggestion about XPath/XPointer/CSS/etc. Done, see email here: http://lists.oasis-open.org/archives/xliff-inline/201103/msg00002.html ACTION ITEM: Andrew to post some "nasty" examples on inline codes. Pending. See also email from David in TC list: http://lists.oasis-open.org/archives/xliff/201104/msg00025.html (item #3) --- 2.2) Cloning, deletion, addition of inline codes. Current requirements list need of feature to clone and add inline codes. See email here: http://lists.oasis-open.org/archives/xliff-inline/201104/msg00000.html --- 2.3) Span/markers -type elements XLIFF 2.0 needs specific elements rather than a generic <mrk>. Let's start defining those elements, based on the requirements. === 3) Any Other Business? - Next meeting will be May-10 at 14h00 UTC -end
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]