Re: [xliff] Summary of the Call - XLIFF TC

Felix, all,

everyone can help by reviewing the current draft

https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/xliff-core-v2.1.pdf

In particular, the following needs review:

[I made a wiki page where volunteers can checkout datacats they want to review in the draft

https://wiki.oasis-open.org/xliff/Review_wd01]

Elements Within Text

Locale Filter

Provenance

External Resource

Target Pointer

ID value

MT Confidence

Allowed Characters

The above data categories were not reviewed in their current shape AFAIK

The below categories are in the spec mostly for more than a year but still may be useful to review

Translate

Localization Note

Terminology

Directionality

Language Information

Domain

Text Analysis

Preserve Space

Localization Quality Issue

Localization Quality Rating

I am sure there are still lose ends, so please do volunteer to review parts of the spec.

Feedback would be best given as comments in the pdf copy sent to the main mailing list, so that I can keep track of dealing with the comments in the pdfs and confirm implementation on the main mailing list.

We want to make most fixes now in an informal way.

We will need to make a comment resolution for every fix after the first public review.

I will concentrate on ctr for the rest of the week. Tom and Soroush need to provide final versions of all validation artifacts by the end of this week..

Yves and others should review the artifacts

especially the ITS rules file, itsm.xsd and itsm.sch (once available)

Cheers and thanks

Dr. David Filip

===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

On Tue, Sep 20, 2016 at 11:01 PM, Felix Sasaki <felix@sasakiatcf.com> wrote:

Apologies for not being able to be on the call. If there is something else I can do to move XLIFF 2.1 forward, let me know.

Best,

Felix

> Am 20.09.2016 um 17:15 schrieb Yves Savourel <ysavourel@enlaso.com>:
>
> Here is the summary for today's XLIFF TC call.
>
> (BTW: I'm afraid I could not capture everything in the CTR and LocNote discussions as I was one of the attendees talking. Please,
> make corrections as needed).
>
>
> Summary of the Call - XLIFF TC - Sep-20-2016
>
> I Administration (0:00 - 0:10)
> A. Roll call
>
> Done.
>
> B. Approve meeting minutes, 6 September 2016
> https://lists.oasis-open.org/archives/xliff/201609/msg00017.html
>
> BS: Not sure those are the right meeting minutes
> .. So we will table the approval for later.
>
>
> C. Revise scheduled for XLIFF 2.1
> https://lists.oasis-open.org/archives/xliff/201504/msg00009.html
> https://lists.oasis-open.org/archives/xliff/201504/msg00014.html
>
> BS: No change as far as I know.
> .. think we are still on track, right?
>
> DF: We did slow down
> .. we don't have started the public review draft yet.
> .. may not be doable for this time.
> .. so hopefully next time, but that'll a month late.
> .. If we don't make next time we'll be in big trouble
> BS: Make sense
>
> DF: maybe we can go through the pending issues
>
> .. We made good progress in ITS categories.
> .. But Fredrik doesn't have time to get his action item done.
> .. So should we drop the feature?
> .. Felix was in favor.
> .. Another thing is the rules file
> .. Felix finished it.
> .. We are missing the Schematron too.
> Soroush: I should be able to do it by next time
> DF: Also need some update in the XSD files from Tom
> Tom: working on it.
> DF: Also the fix for change tracking
> .. several issues with CTR module (ID for source/target, segments, etc.)
> .. could not find the time to write up a solution
> .. also an action item for Tom to update the XSD for allowing more in the <item> element
>
> YS: The CTR issues are difficult to solve
> DF: I think it's important to be able to use segment/ignorable in the item
> YS: yes, but it's very hard to implement.
> DF: we should at least try to see if core can be used.
> .. If that is not feasible we could then just fix the ref value for source/target and keep the content as text
> BS: will try to get the size restriction solution from Fredrik
> .. for the CTR: could we have example of un-implementable?
> DF: we thought just adding inline would be ok, but we found the issue later.
> .. will try to get Chase input on this.
> Basically the items blocking us are in the status email.
>
> <snip>
>
> II XLIFF 2.1 (0:10 - 0:45)
>
> Latest printout
>
> https://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/201609/msg00019.html
>
> L * Localization Note vs <note> (Yves)
> https://lists.oasis-open.org/archives/xliff/201609/msg00045.html
>
> BS: Also the issue with Localization Note
> YS: It seems the ITS Localization Notes and the XLIFF <note> simply don't have the same semantics
> ... (Yves described the issues)
> DF: We should be able to have rules that would make the ITS mapping work
> YS: but we would have different behavior when you look at the same <note> from an XLIFF core or an ITS Module viewpoint
> .. that would be very strange and very hard to implement (e.g. inheritance)
> DF: what is Felix take on this.
> BS: see https://lists.oasis-open.org/archives/xliff/201609/msg00048.html
> .. Basically: giving guidance for the extraction is what we could do.
>
>
> BS: We have a hard stop at the top of the hour
> End of the call
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

xliff message