W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2010

Re: Adoption of the Typed Array Specification

From: Kenneth Russell <kbr@google.com>
Date: Thu, 13 May 2010 11:49:28 -0700
Message-ID: <AANLkTikCjKD8Cc5hWcjsgFULs4s3zk3NI5T-emENVmIz@mail.gmail.com>
To: Allen Wirfs-Brock <Allen.Wirfs-Brock@microsoft.com>
Cc: "arun@mozilla.com" <arun@mozilla.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, "es-discuss@mozilla.org" <es-discuss@mozilla.org>, Vladimir Vukicevic <vladimir@mozilla.com>
On Thu, May 13, 2010 at 11:29 AM, Allen Wirfs-Brock
<Allen.Wirfs-Brock@microsoft.com> wrote:
> Arun,
>
> Thanks for forcing this into our attention.  At a functional level, this appears to be proceeding in a reasonable direction.  However, I think there are some problematic issues about the form and depth of the specification as well as related process issues.
>
> The first words of the specification are " This specification describes additional core ECMAScript types...".    This isn't something that the Khronos Group can do, as the ECMAScrpt specification including its core data types are under the control of Ecma TC39 and any modification or extensions to it will have to be approved by it and the Ecma general assembly.  Since Mozilla is a member of both TC39 and Khronos you are doing the right thing by bringing this to TC39 and I'm sure we can work together on this matter.
>
> However, I think the above statement about "core ECMAScript types" may exemplify a misperception that has deeper technical implications.  The existing formulation of the  Typed Array Specification really doesn't have anything in it involving "core ECMAScript types".  Instead, it uses W3C WebIDL conventions to specify the behavior of a new family of what, in ECMAScript terminology, are known as "host objects".  Host object, are objects that exist outside of an ECMAScript implementation but which may be accessed from within ECMAScrpt programs.  Host objects, do not necessarily conform to the full semantics of ECMAScript objects and may not necessarily fully  support or interoperate with all features of the ECMAScrpt language.   For example, host objects may be anomalous in their support of prototype inheritance and in their implementation of the various property attributes.  Historically, WebIDL based specifications have not addressed such issues and this has resulted in many i
>  nteroperability issues among browsers.
>
> The Khronos Group certainly has every right to specify "host objects"  to serve as interfaces to their technologies.  However, if the desire is for this form of binary data to be integrated into ECMAScript as a "core types" that is available in all ECMAScript implementations (independent of the host environment) then this needs to be addressed by TC39 using its specification techniques which will ensure that the necessary types and features fully integrate into the language.  The existing Typed Array spec. probably works as a specification of a set of "host objects" and it is a good starting point as a set of functional requirements for new ECMAScript functionality  but it is not adequate as the specification of a core ECMAScript extension.  Hopefully, this is something we can take care of in the context of TC39.

Allen,

Thanks for the feedback. I've revised this text in the TypedArray
spec, as you're right that it isn't appropriate to describe these
types as part of ECMAScript at the present time.

-Ken

> Again, thanks for forcing this issue.
> Allen Wirfs-Brock
> Microsoft
>
>
>> -----Original Message-----
>> From: es-discuss-bounces@mozilla.org [mailto:es-discuss-
>> bounces@mozilla.org] On Behalf Of Arun Ranganathan
>> Sent: Thursday, May 13, 2010 5:57 AM
>> To: public-script-coord@w3.org; es-discuss@mozilla.org
>> Subject: Adoption of the Typed Array Specification
>>
>> Greetings, TC-39 WG and script mavens!
>>
>> Browser vendors participating in the WebGL WG intend to implement the "Typed
>> Arrays" specification, allowing for greater manipulation of binary data:
>>
>> https://cvs.khronos.org/svn/repos/registry/trunk/public/webgl/doc/spec/Typed
>> Array-spec.html
>>
>> The draft specification (a work in progress) resides at Khronos, which is typically
>> an unusual home for something integral to the rest of the web platform.
>> Khronos is where we work on WebGL, which enjoys Google, Opera, Mozilla, and
>> Apple participation, amongst other organizations.
>>
>> The general usefulness of constructs such as ArrayBuffers (covered in the "Typed
>> Arrays" draft specification) lends itself to other web platform specifications,
>> such as the File API, parts of which are implemented in Firefox 3.6.3:
>>
>> http://dev.w3.org/2006/webapi/FileAPI/
>>
>> In the above draft (also a work in progress), the Blob interface exposes an
>> ArrayBuffer property, which can then be used with different views.
>>
>> While implementations are currently proceeding unimpeded by standards-track
>> considerations, it would be useful if Typed Arrays were taken on as a work item
>> by TC-39, for more general inclusion in JavaScript.  Should it live elsewhere, and
>> if so, where?
>>
>> -- A*
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss@mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>
> _______________________________________________
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
Received on Thursday, 13 May 2010 18:50:27 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:02 UTC