On Thursday, November 11, 2004, at 09:17 PM, Eric Scheid wrote:
On 12/11/04 3:09 PM, "Joe Gregorio" <[EMAIL PROTECTED]> wrote:Anyone considering such a solution might refer to PacePersonRef[1], although it's in the "Closed" list. It did what's described in this thread, and did away with inheritance. Reasons for closing it:simple, explicit, allows (in an efficient manner) for the use case of half
the entries being authored by one person and the other half by another.
I'm not saying I agree with this in general, but just as a point of interest, I'll point out that SVG does this.
that's good - not because something else does it, but because we can then
ask this question: has SVG revealed any deep problems with this mechanism?
I'll write up a Pace, but won't bother if there are known problems, deep
intractable problems.
http://www.imc.org/atom-syntax/mail-archive/msg09290.html
PacePersonRef contains, among its "Key Questions": "2. Do we want entries to inherit the author from the feed if they don't specify one?" This seems simple and straightforward and easy to understand, thus my answer would be "yes', so I guess I'm -1 on this proposal.
http://www.imc.org/atom-syntax/mail-archive/msg09490.html
PacePersonRef got one -1 from me, and nobody, including its author, objected. Absent pushback, rejected.
It's author (yours truly) did not object because hardly anyone had commented on the proposal, and I read silence as ambivalence, and thus felt uninclined to fight for it. Perhaps the proposal should be revisited, with revisions if necessary.
Another option would be to create a generalized mechanism for referencing data whereby, for example, any element (and it's child content and elements) with an @id can be @ref'ed, possibly with limitations as to where the @id'ed element can appear.
[1] http://www.intertwingly.net/wiki/pie/PacePersonRef
