W3C home > Mailing lists > Public > public-fx@w3.org > July to September 2012

RE: [filters] Shading language recommendation

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Wed, 5 Sep 2012 20:29:52 +0000
To: David Sheets <kosmo.zb@gmail.com>
CC: "public-fx@w3.org" <public-fx@w3.org>
Message-ID: <3C4041FF83E1E04A986B6DC50F0178291BE30D56@TK5EX14MBXC227.redmond.corp.microsoft.com>

[David Sheets:]
> Media Source Extensions normatively specifies a method,
> addSourceBuffer(type)
> <http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-
> source.html#mediasource-methods>,
> on SourceBuffer objects to handle these matters. The informative sections
> of Media Source Extensions follow a normative section
> <http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-
> source.html#byte-stream-formats>
> detailing support for byte stream formats under certain conditions
> (support for resources of that format).

It does not recommend a specific format but informatively documents how 
these formats can be used. Again, I am not alluding to this particular 
spec as a specific technical template for Filter Effects; as such pointing
out to specific items MSE does or does not define is probably not very 
productive. MSE is only referred to as an *example* of a standard that 
does not take a normative dependency on a specific technology but document 
how it does integrate with various alternatives. 

> CSS FX would require additional normative content to be analogous to Media
> Source Extensions.
> >> Do you have any specific technical proposal to manage the divergence
> >> you are proposing? What exactly is your "[s]hading language
> recommendation"?
> >
> >
> > We would not recommend any at this time.
> Please clarify:
> Do you not recommend any shading language at all?

If recommend refers to its definition in RFC 2119, no.

> Do you not recommend any *specific* shading language?

If recommend refers to its definition in RFC 2119, no.

> Do you not recommend any technical means to manage shading language media
> type divergence?

I believe the feature should allow for more than one language and such a
technical mechanism should be defined. (Though I do not have a proposal
at this time). The spec may also informatively document how such a 
mechanism can be used with any specific technology the WG deems worth
Received on Wednesday, 5 September 2012 20:30:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 03:33:48 UTC