PUBLIC MARKS with tag specification

As a real world example of how big the impact can be on performance, I made a test with the full HTML5 specification downloaded locally and ran the profiler. I noticed few of the most expensive selectors had ":link" and ":visited". I changed these to instead be "a:link" or "a:visited" (in this case they were equivalent in terms of which elements matched). This trivial change makes the engine use a cache, and bought the selector matching time down from about 14 seconds to about 11 seconds.

This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed such that it can be extended to work with other push notification schemes such as Push SMS.

WebAPI is an effort by Mozilla to bridge together the gap, and have consistent APIs that will work in all web browsers, no matter the operating system. Specification drafts and implementation prototypes will be available, and it will be submitted to W3C for standardization.

a strict subset of the full HTML5 specification that omits user-agent (UA) implementation details. It is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.

html I'm posting this here as a heads-up for anyone who might be interested, since what I've written is presumably going to supersede the corresponding part of the HTML5 spec. Unless requested by an employer, I do not intend to submit the specification for publication by the W3C. However, it's licensed under CC0, so anyone who's interested can do whatever they like with it, including publish it in some form at the W3C.

you got a binary file and don't know its contents. Or some software creates binary files where you have a specification but don't want to decode them manually.

Synalyze It! allows you to create a grammar for binary files interactively. Unlike in regular hex editors or viewers the files are interpreted automatically for you!

By karl - 2:10 PM on November 7, 2010

Reply

Did you publish a draft specification document somewhere about it? Could you send it as a W3C Member Submission and/or Editor’s draft to CSS WG. The earlier, the better.

relation types for Web links, and defines a registry for them

Two dimensional symbol - QR Code - Basic specification

The GeoServices REST Specification provides a way for Web clients to communicate with geographic information system (GIS) servers through Representational State Transfer (REST) technology. Clients issue requests to the server through structured URLs. The server responds with map images, text-based geographic information, or other resources that satisfy the request.

The Open Publication Distribution System (OPDS) Catalog format is a syndication format for electronic publications based on Atom and HTTP. OPDS Catalogs enable the aggregation, distribution, discovery, and acquisition of electronic publications. OPDS Catalogs use existing or emergent open standards and conventions, with a priority on simplicity.

SAMP is a messaging protocol that enables astronomy software tools to interoperate and communicate.

The growing suite of SPARQL query services offer consumers an opportunity to merge data distributed across the web. A small number of extensions to SPARQL 1.1 enable expression of the merging queries. In particular, a SERVICE allows one to direct a portion of a query to a particular SPARQL query service, just as a GRAPH directs queries to particular named graphs. A BINDINGS keyword adds a compact syntax for tranfering results which constrain a query. The combination of these extensions allows one to compose a query which delegates parts of the query to a series of services. This specification defines the syntax and semantics of these extensions.

The Provenance Vocabulary provides classes and properties to describe the provenance of data from the Web. Hence, this vocabulary enables providers of Web data to publish provenance-related metadata about their data. The Provenance Vocabulary Core Ontology provides the main classes and properties required to describe provenance of data on the Web. Notice, this vocabulary is not designed to describe provenance of other kinds of content such as documents.

A publisher can't depend on anything being broadly implemented just because some spec says a browser MUST do something. A MUST in a specification isn't a law; it provides no push. The only role a MUST in standard actually has is to provide a check-box for implementations; if the vendor of the implementation says "I implement standard X", they mean, among other things, "I follow every MUST in the spec, and I also follow every SHOULD except when I have a good reason not to, which I can explain". That's it. That's all the standard really does, is give you something to measure against.