[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-inline] Inline Markup Teleconference - May-08-2012 - Summary
Teleconference 8 May 2012 - Summary Presents: Yves, Alan, Fredrik, Jung, Arle, Regrets: Ingo, DavidW, Leave of absence: Andrew The summary of our initial requirements is here: http://wiki.oasis-open.org/xliff/OneContentModel/Requirements Latest draft is here: See http://tools.oasis-open.org/version-control/svn/xliff/trunk/xliff-20/xliff-core.pdf There is a TODO page to try to summarize the various issues we have left: http://wiki.oasis-open.org/xliff/OneContentModel/ToDo === Annotations representation 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> See section "2.5.3 Annotations" in draft for an early draft. -> Yves working on it. How to assign metadata on span of content? ID vs offset Fredrik, Jung: id seems to be better. id more XML-friendly, offset requires constant updates Yves: +1 === Representation of editing hints ACTION ITEM: Yves to add section for this in specification. -> Added attributes in schema and draft Processing expectations to be completed based on Fredrik's document, once we discussed them. ACTION ITEM: Fredrik will post a document soon on the general topic of editing/working with inline codes. -> Done see: http://lists.oasis-open.org/archives/xliff-inline/201204/msg00007/xliff_edit_pe.pdf Please, make sure to read and comment the PDF Review of Fredrik's document. Notes: - need to make sure new id in cloned code do not exist in source or target (should be enough to ensure the id of a deleted code is not reused). - need new attribute in sc to indicate the "XMLness" of the original data. ACTION: Yves put text into specs. And post to TC, public. === Bi-directional markers Some reference material: - http://www.w3.org/International/questions/qa-bidi-controls - http://www.w3.org/International/wiki/BidiProposal ACTION ITEM: Fredrik will try to come up with a markup for this. -> Done, see: http://lists.oasis-open.org/archives/xliff-inline/201204/msg00009.html and follow up emails Please, make sure to read and comment. - Idea is to separate directionality defaults for source and target Provide inheritance from <file> - disp-dir used for direction of the original data (native code) could be useful some day (e.g. Arabic elements) - In mrk: not the marked span but the content mrk points to. Not sure if it's the way to do it. Yves: not sure either, seems dir info should be in the referred data. May need to be addressed by TC (dir on metadata like simple-note) Use of Unicode control: what should be the scope? unit? segment? Need to look at span with different dir across segments. ACTION: Yves need to bring dir discussion to TC level. Check also with Unicode (no liaison with UTC, only ULI (DavidF)) === Representation of added codes ACTION ITEM: Fredrik to try to post his document about different cases for adding inline codes. Done see: http://lists.oasis-open.org/archives/xliff-inline/201204/msg00007/xliff_edit_pe.pdf See early text in Yves' email: http://lists.oasis-open.org/archives/xliff-inline/201202/msg00014.html Any comment? Good enough to start putting this in the spec? Jung: Need also things like ruby in HTML5 May need to be added. Yves: possibly as a list of mapping generic->native that tools can use. Arle, Fredrik: would work only for some formats. Maybe an extension module? This would be a construct outside the content. -> Something to get going in the TC as a module (after the foundation is set, to avoid confusion) === Face-to-face: For meeting location, lodging, etc. See: http://wiki.oasis-open.org/xliff/OneContentModel/June2012FaceToFace We'll work on the agenda in the coming weeks. === Any other business --- F: String length restriction: Possible attribute for inline: display-length for a given inline code. Alan: any thought about generalizing this type of information? Yves: not as far as I know. 1.2 has things like char-class Fredrik: many tools probably do checks like this. Would be nice to have a generic way to do this. Note QA annotation may be related? Yves: QA annotation is meant for output currently. (but having QA input would be certainly nice too). --- Bug in the schema for inline code In main content a sequence should be a choice. ACTION: Fredrik to update the schema. --- Next teleconference is normally on June-12. But: a) it's only 2 days before the face-to-face meeting b) several of the SC will be at the MLW-LT workshop Instead we can have the call on June-14 (afternoon of the first day of the F2F) All agree. ACTION: Yves to post the info. -end
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]