- From: Jörg Schütz <joerg@bioloom.de>
- Date: Mon, 10 Jun 2013 13:38:07 +0200
- To: Jirka Kosek <jirka@kosek.cz>
- CC: Arle Lommel <arle.lommel@dfki.de>, public-i18n-its-ig@w3.org, Felix Sasaki <fsasaki@w3.org>, kim_harris@textform.com, Hans Uszkoreit <uszkoreit@dfki.de>, Aljoscha Burchardt <aljoscha.burchardt@dfki.de>
+1 for PIs. We have always used PIs in language checking applications (spelling mistakes, grammar and style errors), and they worked very well. Cheers -- Jörg On June 10, 2013 at 12:03 (CEST), Jirka Kosek wrote: > On 10.6.2013 11:26, Arle Lommel wrote: > >> We need a way to mark up overlapping spans. For example, if you have the following HTML5 segment: > > Haha, overlapping markup. There are several common ways how to handle > overlapping markup. But if you want to stick to XML syntax and > datamodel, no solution will be completely perfect and elegant. > >> The mapping from MQM to ITS 2.0 is clear here, but we need a way to mark up the overlapping spans. So far we have internally used something like this: >> >> <p>Fifteen <mqm-startIssue type="markup, misplaced" id="1" /><em>relays <mqm-startIssue type="agreement" id ="2" />is</em><mqm-endIssue id="1" /> involved</mqm-endIssue id="2" /> in the operation.</p> >> >> We want a good path to interoperability with ITS. So we need a way to put the following information in the document on overlapping spans using local markup: >> >> its-loc-quality-issue-type="grammar" itsx-mqm-issue-type="agreement" its-loc-quality-comment="should be "relays are"" (etc…) >> >> Any suggestions for how to handle this use case? We want to make it as easy as possible to use MQM and ITS together, where MQM provides mechanisms for greater granularity while still retaining compatibility with ITS and ITS provides a way to share MQM data at a common granularity with other systems. > > Your example above means that elements like <mqm-startIssue/> and > <mqm-endIssue/> have to be allowed anywhere in document which requires > change in schema. For this reason it's very common to use processing > instructions instead -- they are opaque to schema validation and no > schema change is necessary, for example: > > <p>Fifteen <?mqm-startIssue type="markup, misplaced" id="1" ?><em>relays > <?mqm-startIssue type="agreement" id ="2" ?>is</em><?mqm-endIssue id="1" > ?> involved<?mqm-endIssue id="2" ?> in the operation.</p> > > Jirka > -- *Prof. Dr. Jörg Schütz* *|* bioloom group *|* Bahnhofstr. 12 *|* D-66424 Homburg *|* Fon +49-6841-756-338 *|* Mobile +49-170-801-9982 *|* joerg.schuetz@bioloom.de *bioloom group* *|* Vertreten durch / Represented by: Prof. Dr. Jörg Schütz *|* Sitz / Register: Homburg *|* USt-IdNr. / Tax-Id.: DE261087278 *|* Web: www.bioloom.de
Received on Monday, 10 June 2013 11:39:15 UTC