XLIFF Inline Markup Subcommittee Teleconference Every second Tuesday of every month at 14:00 UTC 7:00am PDT, 8:00am MDT, 10:00am EDT, 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 === 1.5. Must allow to associate spans of content with metadata We had the action item to propose some representation for the same example. The original post is here:
http://lists.oasis-open.org/archives/xliff-inline/201108/msg00027.html The mailing list has plenty of follow-up emails. Most of them have "Sample for metadata" in their title. === 1.8. Must be able to identify uniquely an inline code within a segment The last email I can see on this topic is:
http://lists.oasis-open.org/archives/xliff-inline/201108/msg00011.html But I think Christian posted an answer. (could you confirm?) It seem the last part of the solution here is to name the 'rid'/'refid'/'idref'/whatever that is the attribute in the closing element that points to the opening one. Naming can wait too. === 1.13. Must be able to represent separately different flows of text and codes when, in the original format, they are mixed together See
http://lists.oasis-open.org/archives/xliff-inline/201108/msg00013.html I don't think there has been any follow-up on this. === 1.14. Should be able to represent the mutual relationships between a nested flow of text and its parent See
http://lists.oasis-open.org/archives/xliff-inline/201108/msg00022.html And before/after I've detached the discussion about the id values in a separate topic === 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 === ID values. Several of our constructs call for ID values. We need to define what value are OK for an ID, and it needs to be compatible with what the TC will do as well. See
http://lists.oasis-open.org/archives/xliff-inline/201108/msg00025.html === 1.15. Should be able to represent illegal XML characters in the content On this topic we are actually discussing wording of the text of the solution rather that what solution it should be. See
http://lists.oasis-open.org/archives/xliff-inline/201109/msg00003.html === Any other business -end