Bill de h�ra wrote:
> I'm not sure it's simple for multi-author scenarios or composite
> feeds. It'll work for my blog, but I don't know if it's work
> for pubsub.
As currently specified, it doesn't work for PubSub. The problem is
that any author/copyright statements that we make at feed-level for our
composite feeds end up getting inherited by any entry that we publish that
doesn't have its own author/copyright information. This is one of the
reasons that I have been arguing for PaceHeadInEntry. I want to make it
possible to clearly establish the scope for inheritance.
In a composite feed, no feed-level data should be inherited by
entries. However, I think it is overly onerous requirement to say the same
for non-composite feeds. Thus, we need a way to block the inheritance --
hopefully without introducing to many mechanisms that are specific to
composite feeds. Personally, I think that PaceHeadInEntry is probably the
best compromise here. It allows explicit statement of inheritable data while
requiring minimal modification to the definition of an entry. To properly
and completely cover the cases here, I think we should also consider
allowing "null" values for inheritable fields so that non-composite feed
developers can block inheritance. Alternatively, we should have a rule that
says: If you need to block inheritance in a non-composite field, simply put
a head in the entry that declares the correct values. (An empty <head/>
might also be useful as a block of all inheritance.)
bob wyman
