RE: Atom Thread Support?

["Jeremy Gray" <jeremy@xxxxxxxxxxxxx>]

> -----Original Message-----
> From: owner-atom-syntax@xxxxxxxxxxxx
[mailto:owner-atom-syntax@xxxxxxxxxxxx] 
> On Behalf Of Eric Scheid
> Sent: Friday, December 05, 2003 5:40 AM
> To: Atom Syntax
> Subject: Re: Atom Thread Support?
> 
> On 5/12/03 9:30 AM, "petite_abeille" <petite_abeille@xxxxxxx> wrote:
> 
> > Reply and InReplyTo sounds very reasonable. Plus it follows a well 
> > established vocabulary: email.
> 
> Just to be confusing, how about "ReplyTo" and "ReplyFrom"?

I'll bite - I don't like "From" in this case. It just reads weirdly to me,
but I'd go with whatever particular words everyone likes the most. I guess
the words "reply" and "from" combine in my mind in a way that suggests the
author of a reply (because of the email sense of "from", I suppose), but I
think weirdly. :)

To keep things moving, the following suggestions:

- pascalCase: the rest of Atom's elements and attributes start with
lowercase letters (that I am aware of). Not sure if any standard has been
set regarding multiple words, abbreviations, acronyms, etc. My preference
would be pascal case for multiple words*. At the least, let's not start with
upper case, so even all lowercase would be fine with me if that's the way
everyone else wanted to go.

- RFC 2731-style link rel: <link rel="Atom.hasReply" href="http://..."; ...
/>

- in a number of places in Atom, both now and later as the core is expanded,
extensions are added, etc. we are probably going to often allow for pairs of
"inverse properties" that point in both directions like this. To do so
consistently would be helpful to those both using the spec as well as those
maintaining and expanding it. Perhaps "has" vs. "is" prefixes i.e.
"Atom.hasReply" vs. "Atom.isReply". Or, since "Atom.isReply" may, to some
readers, have a connotation of "oh, and here is a reply", as opposed to the
intended "this is a reply", "has___" vs. "is___To" or "has___ vs.
"is___For", i.e. "Atom.hasReply" vs. "Atom.isReplyTo" or "Atom.isReplyFor".
Thoughts? Preferences?

Jeremy Gray

* the RDF'er in me would say pascalCase for properties and InterCap for
classes but I won't even go there. :)

* the programmer in me would add (just for trivia, not that I'm suggesting
it here) that there should be no abbreviations and that acronyms be initial
cap for 3 letters and longer, all caps for two letters, and when either are
used to start a property name all the letters of the acronym go lowercase.
Here's the trivia part: Guess the language/platform. :)