week 3 summary on Argon – Hitesh

The paper describes the background study, motivations and the technology directions towards development of the ARGON web browser. It defines the key goals towards creating an immersive and interactive AR web browsing for mobile devices.

I think it involved a lot of research and effort to not just develop an AR browser that supports Augmented and 3D content but to develop an extensible and robust platform which could be extensively used by developers and users to create rich augmented reality applications. I could understand the inclination from the example of window system in desktop, which stiches contents from different applications which sort of still operate in an independent space.  Argon has the ability to support wide range of applications/services because it supports development using existing web standards and technologies (Javascript, CSS3D, AJAX and HTML). Also, extending the spatial markup language KML is a true example of evolution of an existing standard to increase its scope. At the same time, avoiding application specific additions just increases reusability and ease of development. Also, the ability to register triggers for events (locationChanged, focusChanged) is an important element for interactive user interfaces. I might have missed it but I am curious if KARML supports registering for user generated events as well?

The web architecture of ARGON appears to be quite wholesome. Along with supporting static and existing third party content deployment, the ability of server side processing provides control and authority over content and computation. This is a necessity for a real world application. This feature attracted me the most and I would certainly like to explore it. Being a novice in GIS and Navigation systems, I am also quite interested in understanding the details of Geospots usage in ARGON.