This will add the prohibition of use of the xml namespace on markers.
I also added xml namespace to normative references to facilitate referencing it in the spec.
---------- Forwarded message ----------
From:
<workgroup_mailer@lists.oasis-open.org>
Date: Tue, Jan 21, 2014 at 2:18 PM
Subject: [xliff] Version Control Commit by David.Filip
To:
xliff@lists.oasis-open.orgAuthor: David.Filip
Date: 2014-01-21 14:18:41 +0000 (Tue, 21 Jan 2014)
New Revision: 431
Web View:
https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/?rev=431&sc=1
Modified:
trunk/xliff-20/ReviewChangeTracking/csprd02.xml
trunk/xliff-20/attributes/xml_lang.xml
trunk/xliff-20/elements/candidates/match.xml
trunk/xliff-20/fragments/fragments.xml
trunk/xliff-20/xliff-core-v2.0-wd03.html
trunk/xliff-20/xliff-core-v2.0-wd03.pdf
trunk/xliff-20/xliff-core-v2.0-wd03.xml
trunk/xliff-20/xliff-core.html
trunk/xliff-20/xliff-core.pdf
trunk/xliff-20/xliff-core.xml
Log:
printaout ready for csd03/csprd03 vote except for the following:
(non-normative) schema listings and trees need update
(potentially normative) comment #130
(potentially normative) PR on not reordering units
---------------
the complete and fixed xml:lang solution (inclusding <match>
added Warning to fragid section saying that referencing 3rd part namespaces within modules and extensions is not possible, corresponds to solution 1) from Yves e-mail
change tracking updated