Re: PaceCollection

2005-02-07 Thread Eric Scheid


 PaceCollection

+1

yeeouch - I had no idea just how extensive the difference in opinions as to
what a feed represents.



Re: PaceCollection

2005-02-03 Thread =?ISO-8859-1?Q?Bill_de_h=D3ra?=
James Snell wrote:
In any case, we're talking about something as simple as the name of a
single element.  I just don't see any real technical value in changing
it's name.  It doesn't make processing any easier.  It doesn't change
any of the functional semantics.  It doesn't address any critical bugs
in the design.  It just doesn't do anything.
I don't think asking or looking for technical value is that relevant 
here. Names are important [witness the arguments over the name RSS]. 
In markup, element naming tends to matter.

In this case replacing atom:feed with atom:collection doesn't help me 
personally understand the format better - I'm 0 on PaceCollection.

cheers
Bill


Re: PaceCollection

2005-02-03 Thread Antone Roundy
On Wednesday, February 2, 2005, at 11:55  PM, James Snell wrote:
In any case, we're talking about something as simple as the name of a
single element.  I just don't see any real technical value in changing
it's name.  It doesn't make processing any easier.  It doesn't change
any of the functional semantics.  It doesn't address any critical bugs
in the design.  It just doesn't do anything.
Allow me to exaggerate.  Had we been using the following names, there 
would obviously be a point in changing them:

guacamole
chonmage
blueberryThis is my blog/blueberry
raspberry2004-01-25T10:04:00+/raspberry
chonmage
mountain
blueberryJohhny learns to read/blueberry
raspberry2004-01-25T10:04:00+/raspberry
[...]
/mountain
mountain
blueberryI resolve to blog/blueberry
raspberry2004-01-24T14:02:00+/raspberry
[...]
/mountain
/guacamole
Is collection more descriptive than feed of what we're using it 
for?  Would it make for quicker absorbtion of the concept by people not 
already familiar with the term feed?  Would it confuse those already 
familiar with the term feed?

My only objection to collection is that it has two more syllables 
than feed.



PaceCollection

2005-02-02 Thread Eric Scheid


http://intertwingly.net/wiki/pie/PaceCollection

== Abstract ==

Rename the top level element name for the atom document format which holds a
collection of entries, to better communicate it's collection nature, and
more easily allow non-feed collections.

== Status ==

Open

== Related and Conflicting Proposals ==

none

== Rationale ==

The term feed has generally held the special meaning of the collection of
entries which were recently published, and into which new entries will also
be published, with older entries being removed sliding window style (or
something like that)

Which has meant it has been a pain to refer to Atom Feed Documents which
don't obey that semantic, instead being (say) an archive of all posts within
a specific period of time (eg. June 2004). A given resource (eg. the June
2004 archive) could be said to be both an Atom Feed document, but also
''not'' be a feed. Confusing.

Atom Feed Documents are properly collections, of which feeds are just one
semantic. Other semantics for Atom Collection Documents include archives,
directory, comments, trackbacks, pings, parts, versions, and so
on.

== Proposal ==

Rename the top level element for Atom Feed Documents to atom:collection,
and rename Atom Feed Document to Atom Collection Document.

{{{
no spec text -- this is really just a job for the editor, i hope.

*s/atom:feed/atom:collection/
*s/Atom Feed Document/Atom Collection Document/
}}}

== Impacts ==

none. it's just a name change.

== Notes ==



CategoryProposals



Re: PaceCollection

2005-02-02 Thread James Snell

-1. A name change of the top level element accomplishes nothing. 


On Thu, 03 Feb 2005 16:55:35 +1100, Eric Scheid
[EMAIL PROTECTED] wrote:
 
 
 http://intertwingly.net/wiki/pie/PaceCollection
 
 == Abstract ==
 
 Rename the top level element name for the atom document format which holds a
 collection of entries, to better communicate it's collection nature, and
 more easily allow non-feed collections.
 
 == Status ==
 
 Open
 
 == Related and Conflicting Proposals ==
 
 none
 
 == Rationale ==
 
 The term feed has generally held the special meaning of the collection of
 entries which were recently published, and into which new entries will also
 be published, with older entries being removed sliding window style (or
 something like that)
 
 Which has meant it has been a pain to refer to Atom Feed Documents which
 don't obey that semantic, instead being (say) an archive of all posts within
 a specific period of time (eg. June 2004). A given resource (eg. the June
 2004 archive) could be said to be both an Atom Feed document, but also
 ''not'' be a feed. Confusing.
 
 Atom Feed Documents are properly collections, of which feeds are just one
 semantic. Other semantics for Atom Collection Documents include archives,
 directory, comments, trackbacks, pings, parts, versions, and so
 on.
 
 == Proposal ==
 
 Rename the top level element for Atom Feed Documents to atom:collection,
 and rename Atom Feed Document to Atom Collection Document.
 
 {{{
 no spec text -- this is really just a job for the editor, i hope.
 
 *s/atom:feed/atom:collection/
 *s/Atom Feed Document/Atom Collection Document/
 }}}
 
 == Impacts ==
 
 none. it's just a name change.
 
 == Notes ==
 
 
 CategoryProposals
 
 


-- 
- James Snell
  http://www.snellspace.com
  [EMAIL PROTECTED]