I've been thinking a lot about the latest Mixed Reality news to come out from Mobilizy about their open standard for Augmented Reality browsers. This is discussed here and the standard is available here. The standard is based on Google Earth's KML specification, ammending it with AR browser functionality. While there is buzz around it, the lack of detail has created loads of questions. Will it cover 3D, heights, orientation, etc... I'm excited and skeptical at the same time. I like that they are creating an open standard, and on the surface KML seems to be a good standard to build on. Last thing the world needs an entirely new specification, so at least they are trying to build on an existing one. KML immediately provides locational information, as well as style information for the icons that hover on the AR Browser's screen. The description of the placemark provides support for HTML tags. Perhaps the most appealing part of the idea is being able to load in an AR Browser or in Google Earth. KML though lacks a lot, from a GIS perspective at least. No attribute information outside of the descriptions. No metadata. So I'm skeptical... I want to see more of the standards before I rush to start using it a future project that I hopefully will be working on.
3D support is an interesting question though. I think this is a question being asked by people who don't really know about KML and Google Earth. Google Earth can already parse 3D geometry in the form of a Collada file. Just look at all the files created in sketchup and geotagged ready for Google Earth. So it isn't the specification that needs to support 3D, but the AR Browser. I myself asked thought of it wrong when I threw the question out to the twitterverse (no one said anything), but I was thinking taking Collada specifications and incorporating it into KML. This of course would make KML a beast of an xml file to parse. Best to keep them as two separate standards and let them do what they do best. Since Layar announced their 3D support recently, I wonder what type of file format they are using. If it is Collada, then it wouldn't be difficult to 'augment' the ARML standard to includ ARCollada or something more clever.