On Fri, 12 Nov 2004 08:45:42 -0700, Antone Roundy <[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: <snip> > 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.
> [1] http://www.intertwingly.net/wiki/pie/PacePersonRef I think reopening PacePersonRef would be best, as it seems to address most of the issues I've seen in this discussion. The point of contention (evidenced by the name of this thread) is inheritence, with three suggestions: 1) no inheritance: feed:author is just for the feed. 2) yes inheritance: the author of the feed is also the author of each entry unless specified otherwise. 3) yes inheritance, with a NULL option: as #2 but provide a mechanism by which an entry can be specified to have an 'unknown' author. Tim Bray's objection was solely based on inheritance. If we can nail that down we should be able to accept this proposal. > 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. In this regard PacePersonRef is similar to what I suggested (informally)[2]. Categories got wrapped in hierarchy discussions and I didn't see any consensus formed. If you threaten me with "write a Pace" it'll largly be copy-pasted from PacePersonRef. I'll admit that I am just barely XML-literate, but I thought all XML operated on this principle (that you could refer to another node by its @id via a @ref). Lance Lavandowska [2] http://www.imc.org/atom-syntax/mail-archive/msg11331.html
