PUBLIC MARKS with search master-metering

python library for extracting html5 microdata

1) your passwords will be copied to your mobile device and stored in the clear

This parses the HTTPS Everywhere rulesets and, where it can, generates JSON objects to add toChromium's TransportSecurity to require they be secured.

The topic of my Master thesis project is the development of a design pattern taxonomy for data visualization and information design. In its core, the project consists of a collection of 55 design patterns that describe the functional aspects of graphic components for the display, behavior and user interaction of complex infographics. The thesis is available in the form of a 200-page book that additionally includes a profound historical record of information design as well as an introduction into the research field of design patterns. It has been submitted by the end of February 2008, and will be presented in mid-April. Further information on the thesis content and a first version of the pattern browser prototype will be online soon after.

The pagoda (chùa) Thuyèn Tôn was founded by Master Dai Duc Thich Vien Dieu and is named after his original monastery, located in Central Vietnam. The pagoda moved to its current location in 1990 after having been in located in smaller building on St. Laurent where it had been for around 10 years.

karl dubost said at 4:32 am on December 14th, 2010:

Matthew Gertner: “I’ll concede that I have more experience with W3C standards than with those of other organizations. ”

http://www.w3.org/Search/Mail/Public/search?keywords=Matthew+Gertner+

Matthew Gertner: “Someone at the W3C, the de facto master of all things web, decided that we needed a proper schema language for XML.”

Ah? It is usually not the way it is happening. Someone with experience of W3C knows that usually some companies being W3C members have interests in developing a market (because they need interop, because they need to sell products, because… etc.). These companies under the umbrella of W3C organize a Workshop where they gather position papers. After this Workshop, a report is written and published. If more interests, an activity proposal is drafted. This activity proposal is then sent to W3C Membership for reviews and comments. More comments, more modifications. Basically the goal is to establish if the Members have enough interests to commit resources for developing the work. WG charters are established along the same line.

XML at W3C has been pushed because companies had developed tools for handling it and thought that because invested a lot of efforts in the XML toolchain, let’s reuse pieces of it.

IMHO, the standards activities anywhere (including W3C) derail when Marketing dept/Product groups have too much impact on the specification itself. The standard is not anymore driven by the market needs, but the companies are creating the market. HTML5 starts to become known outside of the tech sphere and I think we will have surprises.

The top-down approach in a standard organization seems bit strange considering that the work is the result (usually) of a community of practice.

As for an individual or a small group is not “best” for creating technical specs, it is just easier and address the needs of this small group. So indeed it is easier to produce something which is consistent for this group, which goes faster to implement, to market, etc. That doesn’t mean the technology is better :) The bigger the committee the larger the number of issues. This is a truism. All communities are working like this.

Matthew Gertner: “I’d rather see companies get their tech out there and open it up afterward because it’s in their interest (which is usually is).”

Yes and it is what happens most of the time. That doesn’t mean it will necessary solve things. A good example has been SVG. Three “proprietary” specifications were published before the SVG work with people having things implemented in products. But the spec grew too big, with many people wanted to have their own feature, domain introduced in the specs. Standardizing means reducing diversity, and it’s sometimes take times. For SVG, Macromedia (which was bought far later by Adobe) was on the initial SVG WG… as lurkers and unfortunately not really active participants. This is another reality of standards organization.

There are many more issues. W3C (the organization) is doing a fair job at balancing the interests of everyone. There are frictions, nothing is perfect, but there has been always room for improvements. The process has always been flexible for welcoming new use cases.

Your comment is awaiting moderation.