27,29c27 < June 09, 1998 (updated Dec < 31, 2000) < --- > June 09, 1998 197c195 <

A Property is a Resource that has a name and can be --- >

A PropertyType is a Resource that has a name and can be 200c198 < name; but a Property needs to be a resource so that it can have --- > name; but a PropertyType needs to be a resource so that it can have 203,207c201,202 <

A Statement consists of the combination of a Resource, a < Property, and a value. < These parts are known as the 'subject', 'predicate' and 'object' of a < Statement. < An example Statement would be: "The Author of --- >

A Property is the combination of a Resource, a > PropertyType, and a value. An example would be: "The Author of 209c204 < value can just be a string, for example "Tim Bray" in the previous --- > Value can just be a string, for example "Tim Bray" in the previous 219c214 < <rdf:Description about='http://www.textuality.com/RDF/Why-RDF.html'> --- > <RDF:Description href='http://www.textuality.com/RDF/Why-RDF.html'> 221c216 < <Home-Page rdf:resource='http://www.textuality.com' /> --- > <Home-Page RDF:href='http://www.textuality.com' /> 232c227 < Since a Property is a resource, any independent --- > Since a PropertyType is a resource, any independent 242c237 < Since RDF Statements can be converted into XML, they are easy --- > Since RDF Properties can be converted into XML, they are easy 248,249c243,244 < RDF statements are simple three-part records (Resource, < Property, value), so they are easy to handle and look things up --- > RDF properties are simple three-part records (Resource, > PropertyType, Value), so they are easy to handle and look things up 255c250 < Properties are Resources --- > PropertyTypes are Resources 261c256 < defined a Property that describes the genre of a movie, with --- > defined a PropertyType that describes the genre of a movie, with 272c267 < Statements Can Be Resources --- > Properties Can Be Resources 278c273 < Yahoo!). This means that we'll want, given any Statement such as --- > Yahoo!). This means that we'll want, given any Property such as 281c276 < Statements will need to have Properties. --- > Properties will need to have Properties. 291,292c286,287 < corresponds naturally to the distinction between Properties and < Statements. So it seems as though XML documents should be a natural --- > corresponds naturally to the distinction between PropertyTypes and > Properties. So it seems as though XML documents should be a natural 333c328 < Statements into Resources is quite tricky. Also, it turns out that --- > Properties into Resources is quite tricky. Also, it turns out that 346c341 < doesn't provide though, is any Properties of its own. --- > doesn't provide though, is any PropertyTypes of its own. 351c346 < It seems unlikely that one Property standing by itself is --- > It seems unlikely that one PropertyType standing by itself is 353c348 < packages; for example, a set of basic bibliographic Properties --- > packages; for example, a set of basic bibliographic PropertyTypes 357c352 < Property vocabularies describing books, videos, pizza joints, --- > PropertyType vocabularies describing books, videos, pizza joints, 392,413d386 < < < < < Notes on 31 Dec, 2000 update (Dan Brickley) < < The update of Dec 31st, 2000 serves only to bring this document up to < date with recent RDF terminology. Since this document was first published, < W3C have published the Model and Syntax < specification as a Recommendation. < < < I have updated the markup example to use current RDF 1.0 syntax. There < have also been some terminology changes: 'PropertyType' became 'Property', < 'Property' became 'Statement'. < I have also added a brief mention of subject/predicate/object terminology, < and lowercased a few mentions 'Value' (since rdf:object replaced < rdf:value for talking about the object of a statement). See the diff for details. < <