- From: Felix Sasaki <fsasaki@w3.org>
- Date: Tue, 23 Oct 2012 19:16:01 +0200
- To: Shaun McCance <shaunm@gnome.org>
- Cc: public-multilingualweb-lt@w3.org
- Message-ID: <CAL58czqFZLUxFq2+OG6O0kwoxOPvF3FmRbwxe5jNVY3+80orVA@mail.gmail.com>
2012/10/23 Shaun McCance <shaunm@gnome.org> > On Tue, 2012-10-23 at 15:52 +0200, Felix Sasaki wrote: > > > I know - my point is not about pointers, but about "adding information > > *without fixed values* to attributes or elements". I just can't > > imagine people writing rules like this > > > > > > <its:locQualityIssueRule selector="//span[@id='q1']" > > locQualityIssueType="typographical" locQualityIssueComent="Sentence > without > > capitalization" locQualityIssueSeverity="50"/> > > > > > > That is, tailored to one "span" element. Am I wrong? > > I can't imagine people writing that either. But I can imagine programs > writing it. Consider a program that outputs an ITS-annotated XML/HTML > file based on machine-generated info and/or user input in some UI. If > it needs to present info for an attribute value, the only way it can > do it is by ensuring the parent element has a unique identifier and > writing writing rules like this.ld > Sure - the question is just whether what is more important: allow for every potential use case or focus on what implementors are agreeing to do now. Again I feel remembered of all these global rules for ITS 1.0 (ruby, directionality, even terminology), and I didn't see a user so far. Felix > > -- > Shaun > > > > > -- Felix Sasaki DFKI / W3C Fellow
Received on Tuesday, 23 October 2012 17:16:27 UTC