Primer - Getting into the semantic web and RDF using N3. [translations into other languages ] The world of the semantic web, as based on RDF, is really simple at the base.
This article shows you how to get started. It uses a simplified teaching language -- Notation 3 or N3 -- which is basically equivalent to RDF in its XML syntax, but easier to scribble when getting started. Subject, verb and object In RDF, information is simply a collection of statements, each with a subject, verb and object - and nothing else. <#pat><#knows><#jo> . Everything, be it subject, verb, or object, is identified with a Uniform Resource Identifier. There is one exception: the object (only) can be a literal, such as a string or integer: <#pat><#knows><#jo> . The verb "knows" is in RDF called a "property" and thought of as a noun expressing a relation between the two. <#pat><#child><#al> . alternatively, to make it more readable, as either <#pat> has <#child><#al> . or <#al> is <#child> of <#pat> .
<#pat><#child><#al>, <#chaz>, <#mo> ; <#age> 24 ; <#eyecolor> "blue" . The Platform for Privacy Preferences 1.0 (P3P1.0) Specification. W3C Recommendation 16 April 2002 This Version: Latest Version: Previous Version: Editor: Massimo Marchiori, W3C / MIT / University of Venice, (massimo@w3.org) Authors: Lorrie Cranor, AT&T Marc Langheinrich, ETH Zurich Massimo Marchiori, W3C / MIT / University of Venice Martin Presler-Marshall, IBM Joseph Reagle, W3C/MIT Please refer to the errata for this document, which may include some normative corrections.
See also translations. Copyright ©2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. Abstract This is the specification of the Platform for Privacy Preferences (P3P). Status of This Document This section describes the status of this document at the time of its publication. This is the W3C Recommendation of the the Platform for Privacy Preferences 1.0 (P3P1.0) Specification. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. The list of known errors in this specification is available at Table of Contents Data Set. Reinventing HTML. Making standards is hard work.
Its hard because it involves listening to other people and figuring out what they mean, which means figuring out where they are coming from, how they are using words, and so on. There is the age-old tradeoff for any group as to whether to zoom along happily, in relative isolation, putting off the day when they ask for reviews, or whether to get lots of people involved early on, so a wider community gets on board earlier, with all the time that costs. That's a trade-off which won't go away. The solutions tend to be different for each case, each working group. Some have lots of reviewers and some few, some have lots of time, some urgent deadlines.