Re: ISSUE-107 Change Proposal

Recorded here:
http://dev.w3.org/html5/status/issue-status.html#ISSUE-0107

On Apr 13, 2010, at 11:11 AM, Julian Reschke wrote:

> SUMMARY
>
> The example in the description of the <param> element currently just  
> transports an anti-plugin opinion of the author. It *should* be an  
> example that actually makes sense in practice.
>
> RATIONALE
>
> The purpose of examples in spec text is to illustrate a specific  
> feature, not to transport a specific opinion about other technologies.
>
> DETAILS
>
> The spec currently has the following example:
>
>   <object type="application/vnd.o3d.auto">
>    <param name="o3d_features" value="FloatingPointTextures">
>    This page requires the use of a proprietary technology. Since you
>    have not installed the software product required to view this
>    page, you should try visiting another site that instead uses open
>    vendor-neutral technologies.
>   </object>
>
> The problem with the fallback text is that it's not a good example  
> at all; it just transports an anti-plugin point of view. Why would  
> *anybody* *ever* put that text into a page?
>
> A more realistic example would use fallback text with instructions  
> about where to actually get the plugin.
>
> Such as:
>
>   <object type="application/vnd.o3d.auto">
>    <param name="o3d_features" value="FloatingPointTextures">
>    This page requires the use of the FOOBAR O3D plugin. Get it
>    from the <a href="...">FOOBAR O3D Download Page</a>.
>   </object>
>
> IMPACT
>
> 1. Positive Effects
>
> The example actually makes sense in that it could occur in a real- 
> world web page.
>
> 2. Negative Effects
>
> None.
>
> 3. Conformance Classes Changes
>
> None.
>
> 4. Risks
>
> None.
>
> REFERENCES
>
> None.
>

Received on Tuesday, 20 April 2010 10:53:31 UTC