[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (XLIFF-40) Docbook anchors with itsm_ prefixes for its: attributes
[ https://issues.oasis-open.org/browse/XLIFF-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65423#comment-65423 ]
David Filip commented on XLIFF-40:
----------------------------------
Thanks, Yves, this has not been Resolved, just Proposed.
I agree that the Proposal doesn't address the Docbook anchors directly, so I also agree we can have a won't fix resolution, as the situation became clearer mainly due to edits for https://issues.oasis-open.org/browse/XLIFF-41 and its subtask https://issues.oasis-open.org/browse/XLIFF-36.
> Docbook anchors with itsm_ prefixes for its: attributes
> -------------------------------------------------------
>
> Key: XLIFF-40
> URL: https://issues.oasis-open.org/browse/XLIFF-40
> Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
> Issue Type: Improvement
> Components: ITS Module
> Affects Versions: 2.1_csprd02
> Environment: http://markmail.org/thread/skncl7tvvjq4p4nu
> Reporter: Yves Savourel
> Assignee: David Filip
> Priority: Trivial
> Labels: Proposed, editorial, request_tc_discussion
> Fix For: 2.1_csprd03
>
>
> I've noticed that several ITS attributes were anchored using IDs/names starting
> with "itsm_" (e.g.
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd02/xliff-core-v2.1-csprd02.html#itsm_locQualityIssueComment)
> while there are
> now ITS attributes, not ITSM.
> I know it's just because of the historical changes, and this has no relevance
> for conformance, but keeping the IDs with that prefix
> may be a bit confusing, especially since there is no indication in the
> description of the attribute to which namespace it belongs.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]