- From: Sean Lin <selin@mozilla.com>
- Date: Wed, 21 Oct 2015 14:54:47 +0800
- To: Paul Higgs <paul.higgs@ericsson.com>
- Cc: "public-tvapi@w3.org" <public-tvapi@w3.org>
- Message-ID: <CAO=RbvnhLvR=WosUHPidGG8XLz1QP_mk3eT5YA1_VqwBJLxn3g@mail.gmail.com>
Hi, The references are updated based on the comments. (But for reference to ISO 639-2, I only add links to section 8.2 <http://w3c.github.io/tvapi/spec/#methods-4>, since it's not in specref DB yet and thus cannot be auto generated in the references section.) Thanks, Sean Lin Mozilla Taiwan selin@mozilla.com On Wed, Oct 21, 2015 at 12:22 AM, Paul Higgs <paul.higgs@ericsson.com> wrote: > Hello > > > > During review, the following are noted regarding the TV Control API > Specification – provided at http://w3c.github.io/tvapi/spec/ > > > > 1. The Terminology <http://w3c.github.io/tvapi/spec/#terminology> > section states “The video > <http://www.w3.org/TR/html51/semantics.html#the-video-element> element, > and HTMLMediaElement > <http://www.w3.org/TR/html51/semantics.html#htmlmediaelement>, TimeRanges > <http://www.w3.org/TR/html51/semantics.html#timeranges> interfaces are > defined in [HTML51 <http://w3c.github.io/tvapi/spec/#bib-HTML51>]” > however these are all defined in [HTML5]. Do we need to reference HTML 5.1 > working draft when HTML 5 is already a recommendation? > > 2. The Terminology <http://w3c.github.io/tvapi/spec/#terminology> > section states “The TextTrack > <http://www.w3.org/TR/html51/semantics.html#texttrack>, TextTrackCue > <http://www.w3.org/TR/html51/semantics.html#texttrackcue>, and TrackEvent > <http://www.w3.org/TR/html51/semantics.html#trackevent> interfaces are > defined in [HTML51 <http://w3c.github.io/tvapi/spec/#bib-HTML51>]” > however these are all defined in [HTML5]. Do we need to reference HTML 5.1 > working draft when HTML 5 is already a recommendation? > > 3. Based on the above two items, the informative reference to > [HTML51] is not required. > > 4. As the TVMediaSource is an extension of the MediaSource, the > reference to [MediaCapture-Streams] should be normative. > > 5. There should be a normative reference to ISO 639-2, *“ISO > 639-2:1998 Codes for the representation of names of languages – Part 2: > Alpha-3 code”* – it is directly reference in section 8.2 > <http://w3c.github.io/tvapi/spec/#methods-4>. > > > > I will try to complete a more comprehensive review, but having been > involved in the creation of this specification, it is often difficult to > spot “issues” > > > > [image: Ericsson] <http://www.ericsson.com/> > > *PAUL HIGGS * > Technical Solutions Manager > Ericsson Inc > > > *Ericsson* > 6 Concourse Parkway, suite 400 > Atlanta, GA 30328, United States of America > Phone +1 (650) 580-1731 > paul.higgs@ericsson.com > www.ericsson.com > > > > [image: http://www.ericsson.com/current_campaign] > <http://www.ericsson.com/current_campaign> > > > > Legal entity: Ericsson AB, registered office in Kista, Sweden. This > Communication is Confidential. We only send and receive email on the basis > of the terms set out at www.ericsson.com/email_disclaimer >
Attachments
- image/gif attachment: image001.gif
- image/gif attachment: image002.gif
Received on Wednesday, 21 October 2015 06:55:18 UTC