RI or written spec?

Is the RI informative or normative?

When the spec is actually published, will the written word take 
precedence, albeit with code fragments from the RI textually included or 
will the RI itself be the ultimate arbiter?

Mob

When we've produced a spec to propose as the normative ES4 standard,  
it will be, er, normative ;-). The RI at that point will be  
informative, but it will be maintained so future editions can  
continue to extract code to include in the spec.

/be

On Mar 6, 2008, at 12:23 PM, Michael O'Brien wrote:

> Is the RI informative or normative?
>
> When the spec is actually published, will the written word take
> precedence, albeit with code fragments from the RI textually  
> included or
> will the RI itself be the ultimate arbiter?
>
> Mob
> _______________________________________________
> Es4-discuss mailing list
> Es4-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es4-discuss

The spec is normative.  The RI is informative.  (It will presumably
have to commit to some things that the spec need not commit to, even
if its something as relatively trivial as the precise workings of the
random number generator.)

--lars

On 3/6/08, Michael O'Brien <mob at mbedthis.com> wrote:
> Is the RI informative or normative?
>
>  When the spec is actually published, will the written word take
>  precedence, albeit with code fragments from the RI textually included or
>  will the RI itself be the ultimate arbiter?
>
>
>  Mob
>