W3C home > Mailing lists > Public > public-multilingualweb-lt-tests@w3.org > December 2012

RE: Standoff markup issue

From: Yves Savourel <ysavourel@enlaso.com>
Date: Tue, 4 Dec 2012 11:15:28 -0700
To: "'Multilingual Web LT-TESTS Public'" <public-multilingualweb-lt-tests@w3.org>
Message-ID: <assp.0685190f41.assp.0685bbde7d.008501cdd24b$57574650$0605d2f0$@com>
Hi Leroy,

Thanks for the example.
I have a few notes:

There are two issues IMO with this output, or more exactly there are two reasons not to do this representation:

-- a) So far we have set the information (the right part after the path) on the element or attribute to which that information applies. So in your example the stand-off information applies to the p elements. that is, IMO, where the information should be output. Not on the stand-off nodes themselves.

I even think it's vital to do that because it forces the implementations to resolve the reference. This reference is a reference to ITS data, not a reference to some data carried by an ITS information like most xyzRef attributes are.

-- b) We cannot set the output information on the stand-off nodes like in this example because the stand-off nodes may be in a different document. The stand-off reference attributes like locqualityIssuesRef or provenanceRecordsRef may point to an external XML or HTML documents where that stand-off markup resides. So an implementation needs to fetch the document, open it, get the stand-off data and output that on the node to which it applies. And yes: that is not something easy to implement.


Look at it from a different viewpoint: We should have the same set of information output on a given node whether the ITS data are represented as local markup or stand-off markup. The only difference is that for stand-off markup we may have a several items of that type of information.

Fredrik is looking at some examples of possible output and will post an email later.

cheers,
-yves
Received on Tuesday, 4 December 2012 18:16:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 December 2012 18:16:03 GMT