Google| Subject | Re: Will Tony apologize? (was: Re: Colonial Photo & Hobby) |
| From | Eric Stevens |
| Date | 04/27/2014 01:54 (04/27/2014 11:54) |
| Message-ID | <9rfol99hm6vquhjuuk14qgmql8c4h3s9o9@4ax.com> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Sandman |
| Followups | Sandman (9h & 16m) > Eric Stevens |
On 26 Apr 2014 17:23:41 GMT, Sandman <mr@sandman.net>wrote:
SandmanYour juvenile crowing is premature. The text you have quoted has been standard in RFCs going back for yoncks. What you have missed the first paragraph of 3.4.3
In article <e9tml9h72fpqm2me47gu32vdhgiinotmjm@4ax.com>, Eric Stevens wrote:SandmanMaybe you should get yourself a standards-compliant news client. I see you use ForteAgent, which is known as the worst news reader ever made in the history of mankind.Eric Stevens
Please cite/quote the standard you are relying on in this matter.
RFC 5537, section 3.4.4
3.4.4. Construction of the References Header Field
The following procedure is to be used whenever some previous article (the "parent") is to be referred to in the References header field of a new article, whether because the new article is a followup and the parent is its precursor or for some other reason.
The content of the new article's References header field MUST be formed from the content of the parent's References header field if present, followed by the content of the Message-ID header field of the parent. If the parent had a References header, FWS as defined in [RFC5536] MUST be added between its content and the Message-ID header field content.
Ready to admit you were wrong, yet?
"A followup is an article that contains a response to the contents of an earlier article, its precursor. In addition to its normal duties, a posting agent preparing a followup is also subject to the following requirements. Wherever in the following it is stated that, by default, a header field is said to be inherited from one of those header fields in the precursor, it means that its initial content is to be a copy of the content of that precursor header field (with changes in folding permitted). However, posters MAY then override that default before posting."
... so it is not mandatory that "The following procedure is to be used ... " with no exceptions.
More importantly these rules deal with follow ups. They say nothing about changes in subject lines. In fact I am aware of no rules, RFCs etc which deal with the treatment of threads when the subject line is changed. The nearest I can get to it is at http://www.newsdemon.com/what-is-thread.php where it states
"THREAD A message and the replies to it for a discussion thread. All Usenet newsgroup messages that are not replies to other messages are new threads. A thread is the most common way to distinct particular messages from a post to track the community responses to the topic. A thread is an array of multiple posts on the same subject matter of the original posts. A thread is commonly distinguished by the RE: subject name in order to filter the messages that correspond to the original message that was posted on a particular newsgroup, or an array of Usenet newsgroups that handle the same subject matters in a variety of deviations. "
I would not regard this as a final authority but note that it says "A thread is an array of multiple posts on the same subject matter of the original posts" i.e. change the subject matter and you have a new thread.
This makes sense. 2.1.4 'Subject' of RFC 1036 states:
"The "Subject" line (formerly "Title") tells what the message is about. It should be suggestive enough of the contents of the message to enable a reader to make a decision whether to read the message based on the subject alone. ...... "
Any sensible news reader will sort messages by subject and if there is a change of subject it will place that message and it's follow-ups in a group all together. As far as the reader is concerned it is a new thread.
--
Regards,
Eric Stevens
04/14/2014-
