 Regular XLIFF OMOS TC meeting (Conference Call) |
|
| Name | Regular XLIFF OMOS TC meeting (Conference Call) |
| Time | Tuesday, 22 February 2022, 05:00pm to 06:00pm WET
(Tuesday, 22 February 2022, 05:00pm to 06:00pm UTC) |
| Description | https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3947 |
| Minutes | # OMOS Meeting 2022-02-25 # ## Attendees ## ## Business ##
RVC: have a separate document for round-tripping DF: additional documents create more overhead. I agree in principle but to expedite we should have one document. RVC: the trade-off is we can publish independently DF AI: [#0003](https://www.oasis-open.org/apps/org/workgroup/xliff-omos/members/action_item.php?action_item_id=3951): Ask chet about a docbook version of informative template. There was consensus for informative document. TC Note (informative document) DF: did some editing on Inline Content so would like to verify direction ...need to resolve "characters invalid in xml" ...was discussing in xliff committee along with Yoshito ...coming around to json convention, editors should be told not to display it. RVC: preserving semantics is very important ...jliff simplicity does not harm, DF: whitespace does not need to be addressed RVC: xml 1.1 now allows characters such as bell DF: needs to be discussed within the roundtrip document, need to have instructions when going back to xliff. RVC: most parsers will handle control characters automatically DF: special characters will be markup in xliff. so users will need to be told. RVC: json normalization spec uses utf-16 Yoshito: does json use/recommend any specific normalization formats like NFC? DF: xliff defines equivalents in NFC ...lots of discussion about normalization formats... DF: continued presentation of his work on inline content "properties with array values" good interpretation? RVC: yes I think it's fine PR: clear to me too DF: "anonymous object with a text property" "anonymous text object" phrasing is used extensively throughout the spec! ...section 1.1 Text DF: we should dedicate one meeting to invalid characters in xml. ...representation will require more radical rewrite will try for next time. DF: nice to have - implement change track with user data extensions using user data #15 ## Next Meeting ## 2022-03-15 16:00 UTC |
| Agenda | # XLIFF OMOS Agenda for 22nd February 2022 # - Roll-call - Approve minutes from 25th January 2022 - Review progress of [February Review](https://github.com/oasis-tcs/xliff-omos-jliff/milestone/15) - AOB - Adjourn |
| Submitter | Dr. David Filip |
| Group | OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC |
| Access | This event is visible to OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) TC and shared with
|