RE: [xliff-comment] Proposed changes to matches module

["David.O'Carroll" <David.OCarroll@ul.ie>]

Title: RE: [xliff-comment] Proposed changes to matches module

Hi all,

In accordance with my previous comment (see below) I would suggest changing the id attribute on the segment element from OPTIONAL to REQUIRED. This way it would be possible to reference the segment id from a module like the matches module. In the case of the matches module it would mean not needing to pollute the segment's source with inline markup used to match translation candidates as the match can reference the segment instead.

Regards,
Dave

-----Original Message-----
From: David.O'Carroll [mailto:David.OCarroll@ul.ie]
Sent: Mon 9/30/2013 4:33 PM
To: xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] Proposed changes to matches module


Hi all,

The current implementation of the matches module (i.e. where the source references the match using mrks) does not seem adequate. The only solution at the moment to handle multiple matches for a single source is to have nested mrk elements in the source with each one referencing a unique match.

I would suggest having the match reference the source instead. This can be achieved by adding two attributes to the match element; segRef and mRef. segRef is a URI pointing to the segment id that contains the source for the match. mRef is a URI pointing to some inline marker (mrk for a single segment and matching sm em tags for cross segment matching). It is required to have one and only one of segRef or mRef on the match element.

This solution means the source can remain intact in all cases where the segment is the source of the match. It also avoids having to use nested mrks in the source when multiple matches are available for a single source.

Regards,
Dave