Sorry I could also have given a java representation:
class Entry {
String title;
Person author;
List<Person> contributor;
....
}
class Feed {
Entry head;
List<Entry> entries;
//that's all folks, the rest is just methods...
String getTitle() {
return head.title;
}
Person getAuthor() {
return head.author;
}
List<Person> getContributors() {
return head.contributor;
}
List<Entry> getEntries() {
return entries;
}
...
}
Henry Story
On 16 Nov 2004, at 18:30, Henry Story wrote:
On 16 Nov 2004, at 18:14, Graham wrote:
On 16 Nov 2004, at 4:54 pm, Henry Story wrote:
So similarly you should have no problem accepting that the title in
an Entry that is the head of a feed is the title of the feed.
It's the "an Entry that is the head of a feed" that will never get
acceptance. I don't understand your obsession with this. If you
wanted to create an Atom Record structure, one that is a head and the
rest are called entries, that might make sense and would equally
achieve your goals, wouldn't it?
Perhaps we may well be agreeing. Always difficult to tell :-)
I am saying there is an Entry record structure. A feed is a pair
feed(Entry head, List<Entry> entries)
or
Feed1
|------head-------> Feed1sHead ----a---->Entry
|------entry------> Feed1Entry1 ---a---->Entry
|------entry------> Feed1Entry2 ---a---->Entry
|------entry------> Feed1Entry3 ---a---->Entry
ie: we have one record structure of type Entry.
A Feed has one such record structure in the head relation to it.
And it has a list (or sequence, or whatever collection takes your
fancy) which form
the entries of the feed.
Are we agreeing?
Henry Story
Graham
