Atom allows lists of information, known as syndication feeds, to be synchronised between publishers and consumers. Atom feeds are composed of a number of entries, each with an extensible set of associated metadata. $Date: 2004/05/04 20:57:07 $ Friend of a Friend (FOAF) vocabulary The Friend of a Friend (FOAF) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language. testing A document. Document Online E-commerce Account An online e-commerce account. unstable unstable Project A project (a collective endeavour of some kind). A personal profile RDF document. testing PersonalProfileDocument Group unstable A class of Agents. testing A person. Person An agent (eg. person, group, software or physical artifact). unstable Agent An online chat account. unstable Online Chat Account unstable An organization. Organization represents an individual entry, the basic building block of our interpretation of an Atom blog. The resource of the entry should point to the location at which this information can be found. An Entry has no state. 1 1 1 A feed. The resource the feed points to should be the place where one can get the changeable parts of the feed. 1 1 An image. testing Image Online Gaming Account unstable An online gaming account. A link is a general object that helps attach state to a relation between two objects. The types of things one can add would be some descriptive text (eg: "next 25 results") or the mime types (eg.: "application/atom+xml" or "application/N3") This allows one to have numerous similarly named relations between two representations of a resource. The version of an Entry. A Version collects all the changeable aspects of an EntryID An EntryID is a historical representation of an Entry. The resource of the object is an URI (URN?), which is the id of the Entry. An EntryID can collect the state of the various changes to the Entry. There is a logical relation between an EntryID and an Entry. An Entry always has an EntryID with as state all the changeable elements of the Entry. A place to hold data about the blog itself. common Atom structure the state of an entry at a time hasContent Points to a Link that points to a URL resource where one can retrieve more elements of the feed (the file where an archive of previous entries is). We need a Link object in order to attach titles such as "Next 20 entries" to the link. Points to the Entries that make up this feed. Does not point to an EntryID, because the point is to be able to retrieve the Entry from the given resource, not to identify resources. indicates a person or other entity who contributed to the Entry. the blog that this object is part of. This EntryID was written in reply to an EntryVersion. It could also be in response to an EntryID, but that will potentially cause problems understanding the relation between the two. An Entry (confusing as it does between essential and contingent properties) can also be the subject of this property. The simple rule is of course that if an Entry is in reply to something, then its EntryID is also in reply to that same thing. The location of the Entry object at the time it was in this EntryIDState. Since an Entry is a resource pointing to the location at which it can be found the object is an Entry. The Entry object may now contain completely different content. Points to a Link that points to a URL resource where one can retrieve more elements of the feed (the file where an archive of previous entries is). We need a Link object in order to attach titles such as "Previous 20 entries" to the link. points to an Entry that is the header Entry of a Feed. The header entry would be an entry that gives a special meaning to the feed. It does not point to a EntryID, because Feeds are here to help us locate Entries, not to give any other special meaning to them. indicates the author of the Entry (and hence of the EntryID). The author is a necessary property of an EntryID. a human-readable title points to the dynamic element of the feed. Most feeds are divided into a dynamic element (a resource that always changes) and archival resources, that don't. A name for some thing. testing name indicates the method used to encode the content xml base64 escaped text attached to the link such as "next 25 entries" onveys a human-readable explanation of the blog points to a class that explains the content of the feed. In the case of Atom this would be the Blog class for example. The "atom:summary" element is a Content construct that conveys a short summary, abstract or excerpt of the entry. Issue Date. Publication date of this Entry or EntryIDState the URL at which new entries for this blog can be posted. points to something that can classify this entry into a topic. Some suggestions from Danny Ayers were to look at Wordnet http://xmlns.com/wordnet/1.6/Story, DMOZ directory, CYC, the Maryland folks, "Topic Exchange" when it RDFizes itself, and I suppose the way wikis work by pointing to the wiki topic. This needs some more research. the default language of the Blog indicates the time that the entry (or its EntryID) was created. the content of the Content object The URI pointed to is the place this resource can be edited. In an ideally RESTful world this would be the URL of the Entry resource itself. indicates the mime type of the content. start service.post service.feed service.edit alternate date this Entry was modified. Is equivalent to this Entry's EntryID's EntryState created property. An Entry has an EntryID, that identifies it and all changes made to it. Indicates the version of the Atom specification that the construct conforms to. generator indentifies the software agent used to generate the feed, for debugging and other purposes. href a human-readable copyright statement for the feed. To be developed.