W3C home > Mailing lists > Public > public-personalization-tf@w3.org > March 2021

My Action #79

From: John Foliot <john.foliot@deque.com>
Date: Mon, 22 Mar 2021 08:40:11 -0400
Message-ID: <CAKdCpxwbxsZECXKTxVHuVhiR5zM9+ahTByfYrtikf4saX5f4Xw@mail.gmail.com>
To: public-personalization-tf <public-personalization-tf@w3.org>
RE: https://www.w3.org/WAI/APA/task-forces/personalization/track/actions/79


I have looked at other markup languages at the W3C, and based on my
observations I recommend that we:

   1. use space separated attribute values to concatenate the string (ref:
   2. do NOT use a space between joined values (justification: 'spaces'
   perform string concatenation, and we do not want to concatenate value +
   value as "value plus value", but rather "value-value"
   <img src="her-name.png" alt="שמה" data-symbol="15691+14707"/> as "her
   name" rather than
    <img src="her-name.png" alt="שמה" data-symbol="15691 + 14707"/> as "her
   plus name")
   3. declare our decision, rather than ask for permission


   - CSS uses space separated. Concatenate items are authored together
   (i.e. 12px)
   - CSS uses commas to separate selectors, not attribute values.
   - ARIA uses space separated attribute values. For attributes that take
   multiple values (e.g. ARIA-describedby), the values (idRefs) are processed
   in the order in which they are declared
   - XML does not permit multiple attribute values (<node att1 ="val1" att2
   = "val2"/>)
   - I could not find an example of 'joined' attribute values in any W3C
   markup language

For further discussion.

*John Foliot* | Principal Accessibility Specialist

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"
Received on Monday, 22 March 2021 12:41:06 UTC

This archive was generated by hypermail 2.4.0 : Monday, 22 March 2021 12:41:07 UTC