Comments (3)
Will provide explanatory prose
from xliff-xliff-22.
No action required.
The explanatory note already exists in the published XLIFF 2.1 standard
http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#id
Note
All of the above defined uniqueness scopes ignore Module and Extension data. It would be impossible to impose those uniqueness requirements onto Module or Extension data. As Core only Modifiers could inadvertently cause conflicts with Modules or Extensions based data they cannot access. Modules and Extensions reusing Core need to specify their own uniqueness scopes for the xlf:id. In general, Modules and Extensions are advised to mimic the Core uniqueness requirement within their specific wrapper elements enclosing the reused Core elements or attributes, yet Module or Extensions are free to set wider uniqueness scopes if it makes business sense.
from xliff-xliff-22.
Also based on discussion in meeting on 16th August
This is addressed in the Translation Candidates Module
http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#candidates
from xliff-xliff-22.
Related Issues (20)
- Provide a way to associate <note> elements with <segment> elements HOT 6
- XLIFF 2.1 - Example in 4.3.1.40 type is invalid HOT 3
- Fix local CSS/image links in working draft HTMLs HOT 1
- Remove requirement to register prefix HOT 2
- [Core Proposal] Add examples to explain processing requirements of state attribute HOT 2
- [Core Proposal] Refine constraint for <sc> and <ec> HOT 2
- [Erratum] Normative keywords should follow BCP 14 HOT 1
- [Erratum] Investigate definitions of srgLang and trgLang attributes HOT 2
- [Core Proposal] Support <notes> and <mda:metadata> for entire XLIFF document
- [Core Proposal] Clarify value for “version” attribute HOT 2
- [Core Proposal] Rename Appendix B “Machine Readable Validation Artifacts (Informative)”. HOT 1
- [Erratum] <Typos in the spec>
- [Erratum] The example in "5.8.8.2.2 Inline Elements" should extract the `alt` HOT 1
- [Extended Proposal] Provide a standard way to add description to <resourceItem> HOT 2
- [Task] Need to fix the file / folder casing HOT 1
- [Extended Proposal] Change Appendix A from registration template to MIME declaration section
- [Extended Proposal] PGS module review feedback
- [XLIFF TC Task] Update the announcements section in the TC webpage
- [Extended Proposal] Typos in the spec (capital letters) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from xliff-xliff-22.