AWWSW

Official home page

AWWSW is the "Architecture of the World Wide Semantic Web" Task Group. This is a task group created in a November 2007 HCLS/TAG meeting to look into the semantics of web architecture, the semantic web, and HTTP interactions.

We request that you not edit the AWWSW pages unless you have agreed to the terms of the W3C patent policy.

Regular members:

Jonathan Rees
David Booth

Irregular members:

Henry S. Thompson
Pat Hayes
Michael Hausenblas
Tim B-L
Alan Ruttenberg
Nathan Rixham
Harry Halpin
Stuart Williams

Individual aims

Various group members have expressed different aims. The following are for-instances. (See AwwswQuestions for a more systematic list of use cases and questions.)

TimBL would like to know what triples to assert inside of Tabulator as a result of an HTTP interaction, in particular what to do about the various 30x status codes. These triples should allow tabulator code to deduce useful information for the user interface (such as what to offer an image view of, etc etc), and should allow one to discover what went wrong with access to an information resource, etc.
Jonathan Rees would like to use an ontology to help straighten out the awful mess surrounding RFC 2616, RFC 3986, webarch, httpRange-14, and LRDD. Also interested in what one would like to say in LRDD documents about the nature of resources (provenance, stability, etc.).
David Booth would like a more definite notion of how denotation is established on the Semantic Web.
Stuart Williams asks: 1) What can be inferred (stated, preferably as RDF triples) as a consequence of an HTTP protocol interaction? 2) What inferences/conclusions would it be useful to be able to justify on the basis of 'evidence' from HTTP interactions?
Michael Hausenblas would like to have a formal description of HTTP semantics for data discovery
Alan Ruttenberg asks: "If you were hired to audit a company's site to see whether they were adhering to Web/Semantic Web architecture, how would you do so?".
Nathan Rixham would like to have precise definitions for those elements of web architecture which are at the intersection of the HTML/Web App, Semantic Web and REST communities, where the definition of those things matches "reality" and can be found agreeable by the respective communities. The purpose of this is to be able to quickly remove some things from the equation when answering difficult questions, to have some constraints to test specifications against, and to aid answering the other members questions.