Tag: standards

Towards the Geoweb

heh. the economist calls my work on kml standardization “the road to web 3.0”.
2007-10-18: Mining Information from Collections and KML

Among the results were many amazing links that completed my research by taking me to geo-referenced content on the web; the Rome honeymoon Collection lead me to this great photo of the fountain and this KML file from Google’s keyhole BBS lead me to this stunning Panorama of the area.

I hope this brief overview helps get you started with this new feature in Live search maps. I find it to be one of the most fun and useful (I’m biased as I work on the VE Collections team), and when combined with other features like 3D Birds eye navigation the line between research and leisurely exploration get pretty blurry

very commendable how they talk about the geoweb.

HTTP/2

an update on waka

As I mentioned in a earlier post Roy Fielding has started a ASF Lab for Web Architecture that is intended to be a place to work on documentation regarding Web Architecture. This includes existing protocol improvements and Waka a new HTTP upgrade. Waka is still in the head of Roy Fielding and the changes have been alluded to over 8 years in various ApacheCon presentations; in various Apache 2.0 design notes and emails focused mostly around the IO-layer and request-response processing chains in Apache 2.0; emails to rest-discuss and references to various draft RFC and previous HTTP next generation efforts – rHTTP, W3C’s HTTP-NG and Spero’s HTTP-ng.

2007-12-07:

Another reason to revise HTTP is that there’s a lot of things that the spec doesn’t say. The people who were there in the late 90’s understand the context, and those who have been around HTTP enough have learned to understand the thinking behind its design and the intent of its features. However, there’s a whole new generation of implementers and extension builders who haven’t been exposed to this. If we can document the philosophy of HTTP with regard to extensibility, error handling, etc., they have a better chance of understanding the right way to use it.

i want waka 🙂
2014-01-11:

I wrote up a wall of text about HTTP/2 tradeoffs. It makes for good bedtime reading, puts you to sleep in no time.

Grammar

Years ago I was on the periphery of a massive standardization effort and very very late in the process a feature in the spec was found to be, well, unimplementable. So under the guise of a “grammar fix” the spec was revised to change a “will” to a “will not.”

Use RELAX NG

I have recently recommended to a large publishing client that they adopt RELAX NG as the basis of the formal definitions of their content, in preference to W3C XML Schema Definition Language (WXS). There are lots of individual bits of information on why RELAX NG should be preferred all over the web. Here is an attempt to condense some of the key information into 10 points

  1. A better spec means better interoperability
  2. Availability of a compact syntax
  3. The specification is a stable ISO standard
  4. No PSVI
  5. No content defaulting
  6. Better datatyping support
  7. More sophisticated modelling
  8. More sophisticated grammatical validation
  9. Instances have no dependency
  10. Growing consensus

now hopefully kml will get cured of the XSD disease

iPhone and Open Standards

I was a little nervous to look at iPhone for Web Developers from the Apple Developer Connection; with a splash as big as the iPhone, it seemed inevitable that they’d cut corners when it came to support for open standards. Surely the Use Standards and Tried-and-True Design Practices heading was a tease. But then… wow… The first surprise was support for the tel: URI scheme

then again, apple does NOT hate the web on the iphone. these are incredibly well done