Re: [xliff-comment] XLIFF 2.1 spec: bad links

Thank you for the quick answer.

Yes, it is as expected, once you understand what's going on :-)

Mihai

On Nov 22, 2017 07:04, "David Filip" <> wrote:
Hi Mihai,

thank you very much for your comment on the XLIFF Version 2.1 COS01

A JIRA Issue was created to track your comment's resolution

https://issues.oasis-open.org/browse/XLIFF-71

Please follow the comments resolution on the above link.

Unfortunately, only XLIFF TC members can edit our JIRA issues, however feel free to react to the proposed or approved resolutions in this email thread.

This way all your follow up remains grouped under this permanent markmail link that the TC uses as the Issue source reference:

http://markmail.org/thread/vrbgs6oxn5tjcotq

Please note that the Public review period ends on 19th Dec and therefore the TC won't be able to meet before year end to formally dispose of all received COS01 issues.

Nevertheless, we expect to address all COS01 issues during January 2017.

Cheers and thanks

dF

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 Mon, Nov 20, 2017 at 9:52 PM, Mihai Nita <> wrote:

There are two different pages that I can find for the XLIFF 2.1 spec:

A newer document here: http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html
It is marked "12 October 2017" and the sub-title is "Candidate OASIS Standard 01"

And an older one t http://docs.oasis-open.org/xliff/xliff-core/v2.1/cs01/xliff-core-v2.1-cs01.html
Marked "23 August 2017" and the subtitle is "Committee Specification 01"

Looking at the newest one (xliff-core-v2.1.html) some of the links are wrong
(they point to older doc, instead of staying in the same doc)

For instance go to <source> (http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html#source)
and click on any of the possible content tags.

 <sm> goes to http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos01/xliff-core-v2.1-cos01.html#sm and so on.

v2.1/xliff-core-v2.1.html#sm, click on any attribute (e.g. type), it goes to 
/v2.1/cos01/xliff-core-v2.1-cos01.html#type

I might be some bad redirect though, because saving the file the href(s) point to local labels

(#em, #type and so)

Probably not a big deal, just confusing...

Thank you,
Mihai