>> For such a change there would have to be a long period of deprecation for
>> the current style (though if a name change is on the cards,
>> perhaps a 'year
>> zero' approach might be in order).
>
>A lot of the ideas suggested here of late are going to be hard or impossible
>to make backwards compatible. I think we are talking about at least a
>possible year zero and I would only suggest such a change in the names if we
>were to proceed as such. A lot of people seem to be brain-dumping so I
>though I'd join in :)
I highly suggest that we start from scratch, and not worry about backwards
compatability. I seriously doubt that the authors of software generating feeds
would be opposed to creating another format.
If we start without any preconceived notions of what this should be like, maybe
we'll come up with something spectacular.
... I am sure that I am in the minority here, but it wouldn't break any of my tools since they normalize all data before parsing, and parse based on lowercase...
... I highly suggest that we start from scratch, and not worry about backwards compatability. I seriously doubt that the authors of software generating feeds...
... Right and I'm of the opinion that this is a good time to have these wider-ranging conversations to discuss the relative merits and risks of considering...
<Item> not the same as <item> nor is <pubDate> the same as ... Not as tedious as a case-insensitive comparison of Unicode data (even with ASCII data it's a...
Bravo Peter! You raise several significant issues. I'll jump in here and say I've raised several of the same issues. I'm encouraged that the folks that grasp...
... Indeed. At this point I'm more interested in determining the *full* impact on applications and tools would be from a namechange. And what fixing those...
... So let's start building a list of what hassles exist and what it'll take to fix them. ... Yep, recent events certainly make that abundantly clear. ... ...
... several ... as ... I'm not a member of this group, Bill. ... of the ... yahoo is ... this ... best ... handle". But it ... would presume of ... Bluntly,...
... I agree with Shelley here. I used to edit, oversee and sometimes draft technical related press releases in my recent past life. I'll gladly assist when the...
... Hmm - broadness provides space rather than reducing it, though definitely a plane that is too broad just won't get off the ground. So a strong +1 to...
... news-like ... carrying ... definitely a ... the side of ... occur if ... doesn't ... problems in ... for ... whatever). ... Danny, when I say define the...
... If it isn't a technical issue, then why are you talking about RDF vocabularies? If you're viewing from a business point of view, then surely the selection ...
Let me take another run at my point in the context of Shelley's questions. ... (First of all I'd like to say that putting RDF in the name will be a "kiss of...
... It was in the name of 0.9 and 1.0 and didn't do any harm. As to what the target audience/use is I'd say "web resources that change frequently enough to...
... RSS did fork. What is the major difference namespaces and RDF. Namespaces is no longer an issue. While it wasn't the name, it is a reminder. I'm only...
... {snip} ... {snip} I would submit that a simple (single?) focus that has broad applications is the way to go. Different "features" and restraints will come...
... Gosh, my apologies then, sorry 'bout that. ... Yeah, I've gone so far as to put the ad banner domains in DNS as empty zones. I don't see the pictures...
... What I've asked here is what sort of impact would not using RSS in the name have on various implementations. What true hassles/costs would be endured to...
... vocabularies? ... C'mon folks, let's not get too bogged down quibbling the semantics (ducks). ... Well, we've seen what someone making money off dictating...
... Whoa there, what pseudo-2.0 understands about namespaces and what's correct about using them are two entirely different matters. And it's not our job to ...