coremob / level-0 Goto Github PK

What is the status of each of these meta. Is it listed as things that should have an open alternative or really to support the proprietary meta which is in there?

The current draft[1] is written and intended as a specification, while I don't think this is the right format for your intented goals per the charter proposed on March 6th.

Specifications, especially when on the standards track (which is not an immediate option for community groups), mandate behavior of conforming entities, in this case user agents. The crux here lies in the fact that user agents are by no means required to adhere to certain specifications. Since there are some highly controversial items listed in the current draft, such as proprietary vendor-specific features ("apple-" prefixed meta options), certain proprietary video codecs and MUST requirements on many other specifications in various stages of maturity, I think you should propose recommendations instead.

Creating a specification is a nice goal, but you should also take feasibility into account. In my opinion, implementation of features in rendering engines should be prioritized based on usefulness and end-user demand. One way to convince them would be to provide use-cases and potentially test-suites for each of these features, leading to sane and interoperable implementations. Having a MUST requirement on the "apple-touch-icon-precomposed" meta option without a reference neither explains its purpose, nor shares the intended behavior of semantics.

Instead, consider creating a requirements document such as the Speech Incubator Group has done[2], potentially with the addition of writing conformance tests for several features.

[1] http://coremob.github.com/level-0/
[2] http://www.w3.org/2005/Incubator/htmlspeech/live/requirements.html