# Base: entry.2004-05-23.0105.n3 @prefix xsd: . @prefix rdf: . @prefix : . <> a :Entry ; :author [ a :Person ; :email ; :name "Ken McLeod"^^xsd:string ; :url ] ; :content [ a :Content ; :data "After a long conversation on #atom irc channel, with Henry I think we came to the conclusion that making a Feed a subclass of Entry is a bad idea. The following reasons make me think this would make the model unRESTful. The main problem is that by allowing any entry to be turned into a feed we make it reasonable for every entry on the system to be polled, since at any time that entry could turn into a new feed. This would if deployed widely massively increases the amount of requests going over the web, make the caching of entries meaningless, and thereby render meaningless the main reason of a feed's existence: the reduction in traffic it allows for by funnelling changes into one request.

So even though this model does seem equivalent to the original one proposed by Danny, and though it looks cleaner UML wise, it also potentially fails to preserve the main properties of a feed:

  • entries should not change
  • the head document of a feed should be the only thing that does change
Once a feed has reached a certain size its contents should be moved into a feed archive which should be fixed and unchanging."^^rdf:XMLLiteral ; :type "text/html" ] ; :copyright "Creative Commons" ; :created "2004-06-23T01:05:00.000 GMT+02:00"^^xsd:dateTime ; :id ; :title [ a :Content ; :data "Not a good idea!"^^rdf:XMLLiteral ; :type "text/simple" ] .