Re: [ISSUE-34] Problem with mandatory attributes for quality

I see. In the past I have relied on the assistance of jQuery to parse and 
add extra classes where necessary.

Phil.





From:   Arle Lommel <arle.lommel@dfki.de>
To:     Felix Sasaki <fsasaki@w3.org>, 
Cc:     Phil Ritchie <philr@vistatec.ie>, Multilingual Web LT Public List 
<public-multilingualweb-lt@w3.org>
Date:   07/08/2012 15:30
Subject:        Re: [ISSUE-34] Problem with mandatory attributes for 
quality



I actually thought about splitting the XYZ:yxz.com/fake into two 
attributes (locQualityProfileRef and locQualityCode) since it would make 
such selections easier, but adding another attribute to an already big 
thing is really not ideal either.

-Arle

On Aug 7, 2012, at 16:25 , Felix Sasaki <fsasaki@w3.org> wrote:



2012/8/7 Phil Ritchie <philr@vistatec.ie>
I would see a requirement to support multiple annotations per element but 
only independent ones. That is, Arle's second example would seem required 
as it allows multiple, independent agents to add markup. For the first 
example, the parent entity seems redundant. 

Felix, what would prohibit the application of CSS/DOM processing to the 
multiple records? 

The complexity of writing adequate CSS selectors. How would you write a 
CSS selector that matches 
<meta its-loc-quality-profile="XYZ:xyz.com/fake" />
with
its-loc-quality-code="XYZ:wrong_name"
?

Felix


************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender immediately by e-mail.

www.vistatec.com
************************************************************