Dave Winer ☕️Why did the W3C, which is part of MIT, a supposedly respected academic institution, take my name off the RSS 2.0 spec? They should explain this, fix it, and probably apologize.
Andreas Kuckartz@davew The W3C is no longer part of MIT. See https://www.w3.org/blog/news/archives/9823
yes i heard that. i still think you have to respect creative commons attribution licenses. that was one of the first such licensed documents.
if you work at the w3c please ask them to just point to the spec. that's what would be weblike and respectful.
https://cyber.harvard.edu/rss/rss.html
scroll to the bottom to see authorship credits and the cc license.
@davew I do not work at the W3C.
Maybe @koalie can help.
BTW: A relaunch of the website is scheduled for tomorrow:
https://status.w3.org/incidents/t7dg7v8kjh20
Coralie Mercier (W3C)@andreas_kuckartz thanks for drawing my attention to this.
Hi @davew it looks like the license is respected and that the documents this particular document draws from do not credit individuals either. I'm happy to help fix any error but I'm not finding where the error(s) is/are.
Hi @davew it looks like the license is respected and that the documents this particular document draws from do not credit individuals either. I'm happy to help fix any error but I'm not finding where the error(s) is/are.
@davew I think the issue is that the version hosted on the W3C site draws from versions hosted on https://www.rssboard.org/ which are different from https://cyber.harvard.edu/rss/rss.html
I am a former member of W3C, I was also a fellow at Berkman when that doc was published. That is my writing you're hosting on the W3C site, it's obvious, and my name and copyright have been removed. I'm handling this according to the process outlined by the CC (link below). I don't want to get drawn into your relationship with the group you mentioned. ;-)
Please just fix this and let me get back to my work on making the web work better. Thanks.
What to Do if Your CC-Licensed Work is Misused - Creative Commons
The CC licenses are designed to make sharing simple and place minimal requirements on reusers who want to be able to use creative works. However, sometimes reusers still misuse CC-licensed works, either intentionally or by mistake, and as a licensor, there are several things you can do about it. Before you take action: Before you…
@davew I'm happy to help fix this, I'm not trying to be difficult :) Having just tuned to this, my train of thoughts was that if the author(s) of our page chose to compile from pages from this group (with which we have no relationship otherwise) instead of original pages, there must have been a good reason. Anyway, I'll have a look ASAP.
Rogers Cadenhead@koalie @davew I'm Rogers Cadenhead, the chairman of the RSS Advisory Board.
What the W3C is doing is correct. It is republishing our copy of the RSS specification under the terms of the Creative Commons Attribution/Share Alike license and using our preferred authorship credit: RSS Advisory Board with a link to https://www.rssboard.org/.
The RSS Advisory Board has published the RSS 2.0 specification for 20 years. We've always made it available under that Creative Commons license.
AJ Ianozi@rcade @koalie @davew I'm not affiliated with Dave or W3C, but after reading some context on HN I opened up an Issue on the github repo for this, linking the PR where a similar copyright to the original document was removed: https://github.com/w3c/feedvalidator/issues/106
@aj @koalie @davew The version of the RSS 2.0 specification that had "© Copyright 1997-2002 UserLand Software. All Rights Reserved" was from 2002 and not under a CC license.
There have been 11 versions published since then under a CC license, as described here:
https://www.rssboard.org/rss-history
The W3C is following the license correctly.
@rcade @koalie @davew So W3C is attributing but is rssboard is attributing incorrectly?
I only say that because I did a diff between Dave's original page and the current "RSS 2.0 (version 2.0.11)" and there's still a 93% match. According to CC license:
"If supplied, you must provide the name of the creator and attribution parties, a copyright notice, a license notice, a disclaimer notice, and a link to the material." but no link/name.
"2.0.1-rv-6" is the last version to credit Dave by name.