document: How to make a semantic web browser Two important architectural choices underlie the success of the Web : numerous , independently operated servers speak a common protocol , and a single type of client the Web browser provides point-and-click access to the content and services on these decentralized servers . However , because HTML marries content and presentation into a single representation , end users are often stuck with inappropriate choices made by the Web site designer of how to work with and view the content . RDF metadata on the Semantic Web does not have this limitation : users can gain direct access to information and control over how it is presented . This principle forms the basis for our Semantic Web browser an end user application that automatically locates metadata and assembles point-and-click interfaces from a combination of relevant information , ontological specifications , and presentation knowledge , all described in RDF and retrieved dynamically from the Semantic Web . Because data and services are accessed directly through a standalone client and not through a central point of access ( e.g. , a portal ) , new content and services can be consumed as soon as they become available . In this way we take advantage of an important sociological force that encourages the production of new Semantic Web content while remaining faithful to the decentralized nature of the Web .
doc_bio_tags: O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B O O O O O B I O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O O B I O O O O O O O O O O O O