- From: David Singer <singer@apple.com>
- Date: Mon, 23 Jun 2014 09:02:25 -0700
- To: Robin Berjon <robin@w3.org>
- Cc: Silvia Pfieffer <silviapfeiffer1@gmail.com>, TAG List <www-tag@w3.org>
Since we want permanent labels, I fear that tying them to a version of the spec and its anchors and/or sections, and location, might be fragile. And, as Robin points out, we don’t need choice. I know URNs have issues when referring to things you might want to retrieve, but here we want a name that identifies what the track is for, and we need that name to be non-conflicting with other definitions and to identify who defined it. Obviously it’s a plus if it helps you find the documentation, but it’s not strictly necessary. On Jun 23, 2014, at 6:50 , Robin Berjon <robin@w3.org> wrote: > On 23/06/2014 15:44 , Silvia Pfeiffer wrote: >> On Mon, Jun 23, 2014 at 11:27 PM, Robin Berjon <robin@w3.org> wrote: >>> On 23/06/2014 13:28 , Silvia Pfeiffer wrote: >>>> You could also use these, if you prefer their description here: >>>> http://www.w3.org/TR/html5/single-page.html#attr-track-kind-subtitles >>>> http://www.w3.org/TR/html5/single-page.html#attr-track-kind-captions >>>> etc >>> >>> >>> I think that the fact that you're giving David a choice is part of the >>> problem :) >> >> Not really - they point to different things: one the attribute value >> of the object and the other the general definition. >> Also, the answer to having two alternatives is not to introduce a third. ;-) > > Agreed :) But I was suggesting indicating which one to use, not introduce another to the choice! > > -- > Robin Berjon - http://berjon.com/ - @robinberjon David Singer Manager, Software Standards, Apple Inc.
Received on Monday, 23 June 2014 16:02:56 UTC