Jump to content

Talk:Digital rights management/Archive 3

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1Archive 2Archive 3Archive 4Archive 5Archive 6

DRM takes a shot in the heart.

"Following digital music pioneer Apple Inc.’s lead yet again, Microsoft Corp. said this week it will soon sell digital music online without digital rights management (DRM) protection.

Microsoft’s apparent change of heart on selling DRM-free music came in response to Apple’s deal earlier in the week to sell unprotected content from recording company EMI Group PLC. The company previously claimed that DRM was necessary for current and emerging digital media business models."

"In February, Apple CEO and founder Steve Jobs stirred up controversy when he called for the end to DRM in an open letter to the industry… At the time, Microsoft responded harshly to Jobs’ statement — a Zune spokesman called it naive and irresponsible — but now the company seems to have literally changed its tune."

Booya.

BTW, information extracted from John C. Dvorak's blog (dvorak uncensored), dvorak.org/blog is where you can find it. I don't think they'll mind too much, it's just a blog anyhow.

Obnoxiety news: Coldplay

Coldplay's new CD has rules (added 2 Jan 06 by 84.109.75.239, ww)

One point about the "no refund" disclaimer inside the packaging. INAL, but I think that creates conditions on the sale after the sale is complete, so would be legally invalid (for US and probably other countries too). --H2g2bob 03:46, 27 June 2006 (UTC)

NPOV?

This article has some point of view issues. Take this bit, for instance. Instead of an actual definition of trusted computing we get a silly conspiracy theory and some FUD:

However, trusted computing creates the prospect of a computer system which cannot be trusted by its owner, but rather its behavior can be remotely manipulated at any time, regardless of the legal merits of such manipulation. Most opponents have little faith that the courts or legislatures will be able to limit such manipulation to only that which is legally permitted.

There are some valid worries in there I'm sure, but they shouldn't be presented as fact. We should use the accepted definition, then mention the concerns as concerns. 24.39.223.104 05:20, 7 January 2006 (UTC)

24.29...:
The NPOV question has been the subject of multiple postings here (see above and above and above and ...). This objection, like many others, is a complaint without a proposed resolution. As before, please suggest a better wording, rather than merely noting alleged bias. In this case, the facts are as stated, whatever the wording. Trusted computing (or some other alternative phrase meaning the same thing), is in fact a way to prevent a computer from doing some things its user/pwner might wish. And, as is stateted in several places here, the resulting control of the computer may or may not match the owner/operator's actual legal rights. As for accepted definition(s), there is much manipulation of terms in this field, sufficiently so that it is seriously questionable there are 'accepted' definitions. Recall that Sony/BMG's stealthed rootkit installation was termed 'Rights Management' and "User Protection', not 'insecurity installation'. It's one of the biggest security breaches in history apparently.
Given the problems in this field (terminological, legal, marketing, engineering, cryptologic, ...), it is nearly certain that no presentation will satisfy all. WP should, as this article currently tries hard to do, attempt an even handed presentation, incuding problems that some vendors do not like to discuss or see discussed. If some object, let them suggest improvements. ww 22:34, 22 January 2006 (UTC)
I agree with Ww here. The objection stated is not specific enough that it could ever be addressed in principle. If 24.39.223.104 wants to try some specific change in wording or the like, we can work on that (which is what article editing does). But an a priori claim that the article is in some abstract, non-specific way POV doesn't warrant the NPOV tag. Try to improve it first, and if that doesn't work out after some sincere efforts, then tagging might become relevant. Lulu of the Lotus-Eaters 22:41, 22 January 2006 (UTC)
The primary POV issue is a popular misnomer: the phrase "your computer". It is NOT your computer. Virtually every code on every chip, every component of the hardware, drivers, software, and operating system, including the DRM components, are licensed to you under certain conditions. An accurate POV is to say that it is their computer, which they graciously permit you to use for a fee, provided that you are willing to submit all your information for continual monitoring for practically any reason at all. Anything else is illegal. I submit that that is the neutral POV under the law. 204.186.59.178 23:04, 2 April 2007 (UTC)

DRM = Malware

Since the effects of DRM is always detrimental to the owner of the file, isn't it by definition a kind of malware?

anon poster -- This is a common view, but is not entirely true, at least in theory. Being malware depends in part on whose ox is being gored. Sony, for instance (or some cretin there) seems to have thought that inserting a root vulnerability into your computer system when you played one of their protected audio CDs was a net benefit -- to them. Those who understand what is going on, and its significance, surely disagreed. In the long run, the furor about it all when it became publicly known probably made the entire effort a net loss to Sony.
And there is a not so theoretical problem here. It appears that all the anit-virus makers knew about Sony's rootkit installation, but decided that it didn't meet their definition of 'virus' and so did not bother to inform users of their software about this vulnerability, nor did they repair the 'problem'. Users who understood what was at stake presumably were not pleased to learn this. I was certainly not one. F-secure (of Finland), to their credit, were the only anit-virus maker who did so when it came to their attention. You may imagine how that affects my evaluation of the various anti-virus makers and their products and policies. Finnish phones and now Finnish anti-virus software. Leaping about naked in the snow on subzero winter days after leaving the sauna is probably next. Brrr!
A purely theoretical DRM system which prevented only those things which were not legal or licensed (and which changed what it prevented as real world events occurred such as copyright expiration, changes in license terms, ...) would not, in itself, be malware. No such DRM exists as the technical problem of designing or building DRM which behaved this way are so immense as to be, in my view, impossible. Probably for the indefinite future. And, of course, this non-malware sort of DRM would have to be error free (design and implementation) and not subject to alteration by pranksters or others when deployed. No one knows how to do this. Software systems have killed several people (whilst controlling or mal-controlling, industiral robots), have ruined spacecraft and rocket launches to very great loss (the first attempted ariane 5 launch, for instance), etc etc.
So your point that DRM is by definition malware is well taken in actual practice, though not in theory. Lawyers and marketing cretins seem nearly universally incapable of realizing this, though quite why is not entirely clear. Law school classes in which engineering reality is specifically prohibitied from affecting legal consideration, maybe? How to make this point in the article without POV bias (or being accused of POV) is much harder to figure out.
ww 19:58, 23 February 2006 (UTC)

NPOV Digital Restrictions Management/Digital Rights Management

Since there's actually debate about which is the correct expansion

Digital Rights Management vs Digital Restrictions Management

Can Rights Management actually claim to a NPOV?

The very fact that no common form of DRM actually protects the rights of the consumer (First Sale and Fair Use being prime rights) wouldn't the correctness of Restrictions Management make it the better true article title. i.e. since no title can claim NPOV the expansion closer to the facts of life should overrule.

It's very simple. The term Digital Rights Management was the original expansion, or rather DRM is the abbreviation of this. It should be understood however, that these rights are not rights in the judicial sense of the word, but in the computing sense, as in "access rights".
Since the way the term is now propagated is blurring this border, people alarmed by this development have started re-expanding DRM to Digital Restrictions Management.
Since in current usage both expansions are inherently POV, the only way to remain NPOV is to somehow mention them both, which we are doing in the article. Whether the new expansion should be mentioned here is open to debate and mainly based on click-through ratio: how many people looking up this expansion would also look up the article? I think that number to be near 100%. I think the usual lookup path will be: "user gets confronted by DRM in real life - what does this mean? - what does Wikipedia say? - enters DRM in search box - clicks through to the article". Shinobu 15:17, 16 March 2006 (UTC)
IMHO... saying the same thing as Shinobu... this is a problem that occurs with almost any accepted term that was coined by people who were promoting their own point of view. I hold it to be true that a) DRM stands for Digital Rights Management, i.e. if you asked people who use the initialism what it stands for, that is what the overwhelming majority would answer; b) Digital Rights Management is an extremely loaded term (like "intellectual property" or "caller ID" or "pro-life"/"pro-choice") whose very use presupposes things that aren't necessarily true. I don't agree that there is a debate about which is the commonly understood expansion. The debate is about how the initials ought to be understood. Both "Digital Rights Management" and "Digital Restrictions Management" are propaganda, but the former is the successfully promulgated propaganda. Dpbsmith (talk) 15:31, 16 March 2006 (UTC)
That was not the debate I meant - I meant whether the Restrictions expansion should be mentioned here @ DRM, as opposed to only here in the article. The thing is, we (i.e. Wikipedia) don't really want to promulgate either propaganda, or if that's impossible, at least we want to make sure that we're promulgating both to the same extent. Shinobu 16:55, 16 March 2006 (UTC)
(edit: I thought this discussion was being held on Talk:DRM. My bad.)
I would also like to add that with "succesfully promulgated" always comes the question "in what circles?" - I for one always use the Restrictions expansion, and so do a lot of people belonging to the particular sub-culture I seem to be a part of now and then. That we are less numerous is not really that relevant. After all, the point of view of "most people" is not necessarily neutral. The only way to deal with this is as I described before - tell how the moniker came to pass, why it's misleading, and why some of us choose to expand it differently. IIRC the article already does that. As for the appearance of the expansion on DRM, that should be based on click through ratio. I think this is nearly 100%, so I don't think it will be necessary, as I stated before. Shinobu 16:12, 18 March 2006 (UTC)
The remark that DRM should be called digital restrictions managament is about as much NPOV as saying that the m in meat stands for murder. No matter how much sense it makes, it is definetly not NPOV, it is propaganda, therefore i have deleted it from the article. Lyml 20:01, 15 February 2007 (UTC)
On the other hand, I'm marking this entire article as POV as it seems to have alot of problems with NPOV, wikipedia has stated that it is considered bad manners for an article about a subject to talk about critisism about the subject. The critisism about DRM really should be extracted into a separate article with this article only explaining the technical meaning of DRM. —Preceding unsigned comment added by Lyml (talk • contribs)
You have obviously misunderstood neutral point of view and describing points of view. -- intgr 20:28, 15 February 2007 (UTC)

DRM depends on Mandatory Access Control

Changed the para with this claim to delete the flat claim, replacing with forward looking observation and some perspective on the reasons why we're headed there. That's the way things are headed, but we're not there yet. After Vista, perhaps. 71.249.12.89 04:35, 16 April 2006 (UTC)

Beale Screamer and FreeMe

Why nothing about this here?

sarbanes-oxley & drm opponents

this paragraph, from "drm opponents":

The use of DRM is a key part of implementation of corporate compliance policies such as the Sarbanes-Oxley Act of 2002, protecting corporate documents from unauthorized tampering and creating an audit trail which can be used to determine liability at board level within corporations for misdemeanors. This level of control is obviously unwelcome at certain levels.

doesn't seem quite npov, or quite right. If it's true that DRM is key to Sarb-Ox, that's a factual piece of information that should probably go under the "other uses of drm" header, and the snarky sentence about "obviously unwelcome" taken out. This paragraph isn't discussing actual groups, as the other entries in this section do; it's hypothesizing. As described, Sarb-Ox could also be taken as an argument for drm. I don't know much about the subject, so didn't want to jump into editing it.. Brassratgirl 00:49, 20 May 2006 (UTC)

Good catch. After spending a few minutes scratching my head over what was being states in this paragraph, I decided to remove it entirely. If someone wants to identify what group(s) would be against DRM implementations for Sarb-Ox purposes, with a citation to a publication that makes this identification, they can add it in with much better language. Warrens 01:02, 20 May 2006 (UTC)

Digital Restrictions Management = POV claim

NB: In respect of the discussion below, see the prior discussion referenced here (now in an archive page), on this and related alleged POV points, here.

The reversion of this change in the first sentence is due to the long history back and forth of POV accusations. Digital Rights Management is itself an attempt to bias the discussion by terminology choice. There are in fact no specifically digital rights (only existing IP rights transferred into a digital context) and the assorted attempts to protect those rights have characteristically (because the engineering does not well match the legal categories and permissions) attempted to protect rights the copyright holders do not have, in law, as for instance the right to make a copy of the material onto an 8-track for use in a car.

There is no satisfaftory name for these schemes, whether as a class or as an individual instance. Please note the long history of dispute on this topic as reflected on this talk page. Your position, with which I have some sympathy, can't be justified in the context of this WP article. ww 15:49, 6 July 2006 (UTC)

Whatever, man, you're entitled to your opinion, but don't use Wikipedia to preach a preferred POV. Keep focused on producing encyclopedia-quality articles. This article is about, literally, "Digital Rights Management". The fact that some people have re-termed it "Digital Restrictions Management" as a form of criticism of the technology and concepts is important to mention, but it's not something that needs to be stated in very the first sentence of the article. An article's first responsibility, according to Wikipedia:The perfect article and Wikipedia:Lead section, is to clearly define what the subject is. The term is covered in the third paragraph of the lead section, which is a perfectly appropriate place for it. Warrens 19:17, 6 July 2006 (UTC)
W, No preferred preaching coming from me. You'll note that I have retained both terms. And have argued repeatedly above on both sides of the "It's all an infernal plot", and "It's justified to protect those rights", sides. So I decline the nomination, as both not nice, and wrong in fact.
If we have here a stylistic point in dispute, that is one thing. I disagree that the issue may be deferred to the 3rd para given the high intensity feelings surrounding the subject whatever it's called. It should be made clear early on, as a point WP may entirely encyclopedically make, that there is conflict re the terminology. Not an isolated position (see various above, eg, dpbsmith). So I would retain the note you have elided and early on too.
If, on the other hand, you are claiming that D Restic Man is POV, while D Rights Man, is NPOV, we could not agree less. EVERYONE attempts to control the debate by controlling the terminology (except of course me...:). Including editors of this article. Please refer to the long history of accusations of POV (in re this or that aspect, including the terms used) in regard to this article. See above and above and above... on this talk page. In fact this precise point is made by several here, including Lulu_of... This issue has been hashed out repeatedly for a long time, and you are coming into the affray at a late date.
The phrasing you have changed and rechanged had been stable for some time prior to your intervention. I suggest that its alleged bias is insufficient, even it it could be determined to be present, to damage the article's *OV and that it be retained, if nothing else, as a warning flag to the Average Reader for whom we are writing. Comment? Reaction? Anyone? ww 22:14, 7 July 2006 (UTC)
Sure. I think the common expansion is highly POV, but we do a very good job on explaining what DRM is in the first sentence, including (last time I checked) that it has nothing to do with rights. As long as the reader gets that point, we're in the clear I think. I think having to expansions in the first para is very ugly. Considering that D.Ri.M. was the original expansion for DRM in this context, it might make sense to have that one first and have D.Re.M. in the second para or so. Shinobu 12:46, 8 July 2006 (UTC)
No, you're not understanding the point at all. Let's say the U.K. Conservative Party decides that Tony Blair should be known as "Balony Bear", does this suddenly grant them the right to rewrite the article on Tony Blair, writing something like "Anthony Charles Lynton Blair (born 6 May 1953), also known as Balony Bear, is the Prime Minister of the United Kingdom of Great Britain and Northern Ireland"? No, absolutely not. Right? Should Microsoft be introduced as "Microsoft Corporation (NASDAQ: MSFT, HKSE: 4338), also known as Micro$haft, is an international computer technology corporation?" No, absolutely not. Right? Alternate terminology coined by detractors and oppontents has precisely zero place in the introductory sentence of an article. None! We're an encyclopedia; we define things as precisely as possible, then we describe them, then we get to the issues. Trying to argue that the term "Digital Rights Management" is not a neutral phrase is completely irrelevant here; the creators of the technology call it Digital Rights Management, and so Digital Rights Management is what it shall be known as. You and I may not *like* the technology (I certainly don't), but whatever, we're here to write an encyclopedia, not to promote Free Software Foundation-approved opinions on subjects. So, in the context of writing a proper encyclopedia, should this subject be introduced as "Digital Rights Management (DRM), also known as Digital Restrictions Management is any of several technologies used by publishers?" No, absolutely not. Right? -/- Warren 18:46, 8 July 2006 (UTC)
People really call him Baloney Bear??! To each his or her own I guess. In this case, the question for WP is whose loaded terms to be featuring in some sense. The inventors of the term, those who object to this as a loaded characterization in the name, or someone else. Since we're writing an encyclopedia, we should make -- in cases such as these in which disputes run at high temperature -- no choice between loaded terminology. We should note, early, that there is dispute about the meaning of DRM, and thereby take no position on the question. As I noted that is the position arrived at long ago here, after considerable backing and forthing. We should let stable positions lie, in my view. ww 03:38, 9 July 2006 (UTC)

ww, please re-read WP:NPOV you are mis-understanding our policy on POV. The idea behind it is that we not insert our own POV into articles. Mentioning other people's POV is perfectly fine, see the section on "Writing for the enemy" in particular. AlistairMcMillan 04:50, 9 July 2006 (UTC)

Agreed. And inclusion of D Res Mgt early is so mentioning, without, I admit, making a blunt declarative sentence on it. Which is why, in this matter, I'd prefer to mention the Restric expansion en passant, as it were. Always poor writing practice to whack readers over the head, at least in this sort of writing. ww 16:34, 9 July 2006 (UTC)

Also the section on "Giving equal validity" while you are at it. The people who created DRM say it means Digital Rights Management, critics say Digital Restrictions Management is a closer meaning. We don't give equal validity to both points of view. Like Warrens said, we wouldn't put "Micro$haft" into the first paragraph of the Microsoft page.AlistairMcMillan 04:50, 9 July 2006 (UTC)

We can't give any validity at all to either expansion, and shouldn't do so by commission or omission. Not a WP thing as you note. All we can do is report a dispute about the meaning, and it's all we should do. In this case, no one (well not in this cycle of the controversy (so far)) is actually arguing that the alternative, strongly held by important folks in the software world (the most important of whom is a MacArthur Award winner), should not be included at all. It's a stylistic point in re where to put WP's recognition of the dispute. It being as political as it is, I'm in favor of noting both, early, and getting on with the discussion. Which is (has been and probably will be as long as momentus questions of control and profit are thought to stand or fall on this stuff) contoversial in and of itself. ww 16:34, 9 July 2006 (UTC)
Yes we bloody well can give more validity to one. The people that created it called it "Digital Rights Management". That is the proper name. We don't give equal validity to alternate names invented by critics. Mentioning the critics alternate name in the third paragraph is where it belongs. AlistairMcMillan 16:58, 9 July 2006 (UTC)

And please stop saying there was a stable accepted position here. All discussion just tapered off and then an anonymous contributor re-inserted "Digital Restrictions Management" into the first sentence.[1] There was no consensus. And if there was a stable position it was the one without "D Restricted M" in the first sentence. AlistairMcMillan 04:50, 9 July 2006 (UTC)

If was the dying away of some of the accusations of bias that I was characterising as stability. Quiescence on debated WP articles is, I suspect, about as much stability as we will ever see. I've considered attempting reach stability by intervention and blocking and all that, but in some years here, I've not seen a case in which this did not pour oil on fire, not on troubled waters. So I've made a decision not to throw my (not so consequential, actually) weight around. Which is why I reached the conclusion that "quietus = (as much stability as we here will ever see in controversial articles)". ww 16:34, 9 July 2006 (UTC)
I see that temperatures have gotten rather higher, and so I'd prefer to invite others to comment as characterizations have now trended in an unfortunate direction. Thus, Comments? Observations? Agreement, disagreement? By others than the recent participants above? ww 17:31, 9 July 2006 (UTC)
You're not going to find much support around Wikipedia for making a change in favour of inserting a notable critic's reactive renaming of the technology into the very first sentence of the article. Really, you're not. No matter how much you may believe in the importance of the term "Digital Restrictions Management", it's our first obligation as an encyclopedia to define "Digital Rights Management" first, because that's the name of the article, and that's the subject of the article. Criticism always come after the definition. Always, always, always. Anyhow, Wikipedia:Third opinion and Wikipedia:Current surveys are available if you really feel an outside opinion is necessary here. -/- Warren 18:37, 9 July 2006 (UTC)
I don't believe in RMS's term, and I'm not sure how you can get that out of my comments, here, or in the archive noted in the head note here (I've changed the pointer back to the archive, not to just one heading in it -- the 'rasslin has been ratehr more extensive than that). I'm opposed to POV -- ANYONE's POV -- and object to sneaking the POV into a name and having WP not note this attempt early and prominently. You've misread my (and others) purpose on this POV point, and the others which have regularly been raised here. But, as I told AlistairM, in a side discussion on this, I'm tapped out on this subject. I'm going to leave it to another time. ww 21:36, 9 July 2006 (UTC)

Thanks to Warren, AMM & others for bringing sanity to the DRM article. I'm just as much an opponent of DRM as everyone else here but the persistence of those who insist on the DReM term up front and the pervasive POV throughout the article is embarrassing to Wikipedia. There are great NPOV articles on issues with far more polarized zealots than DRM. I've tried some NPOVing of DRM in the past but was reverted - I'm glad others have more stamina. 71.232.63.11 02:11, 11 July 2006 (UTC)

I'm jumping into this a bit late (and I hate DRM as much as anyone), but I think people are missing the point of the name Digital Rights Management. Nobody is claiming that the end user is being granted special rights via DRM that they don't have normally. The whole point is the word "Management". The copyright holder is trying to manage the limited rights you have when purchasing, say, an MP3 file. Those rights include downloading it, listening to it, etc. but do not include giving it away to all your friends. That's why the copyright holder must manage those rights. Now granted they do this by placing restrictions on what you can and cannot do, but in reality these restrictions are placed by the copyright laws and/or licensing agreement, DRM just attempts to set up technical hurdles to enforce whats there on virtual paper. But that doesn't change the name of the technology. Love it, hate it, as you wish-- but the real and proper name is "Digital Rights Management". --Rehcsif 19:01, 16 July 2006 (UTC)

I rewrote the leading paras a little, choosing to include the "restrictions" variation on the basis that:
  1. It is a significant alternative title, with more than a quarter of a million hits for a simple google search of the term.
  2. It was coined by Richard Stallman, a significant player in the debate.
  3. It could easily be noted, and I did, that it was not an official name.
Thought I should note this here, in case you want to change something. I'm pretty sure it no longer represents a POV claim, but I may have screwed it up. RandyWang (raves/rants) 12:33, 20 July 2006 (UTC)

Cleanup taskforce

This page was added to my desk, so I've been bold and started cleaning the article up as much as I can. I'm removing a lot of content, for any of several reasons (mostly to do with the density of the text, readability, usefulness or general style). If you believe I've screwed up, please do not revert the page, but instead manually re-add the specific text that you believe was superior to my rendering, then post about it here. Thanks! RandyWang (raves/rants) 09:21, 20 July 2006 (UTC)

Some things I've done:
  • Rewrite the introduction. It was nowhere near as streamlined as it could have been, contained irrelevant info (eg, DRM's legal status in the European Union, when no mention was given to its status in any other country - moved this snippet further down the page).
  • Removed the quotes section - moved to Wikiquote, and added reference.
  • Prune the links section. Apologies if I removed something good, but I simply removed any website that wasn't obviously notable and worth a mention here - I left a couple in place that I was uncertain about, but I'll fix that when I have a chance to take a closer look at them.
I'll keep the list updated with major changes as I work on the article. RandyWang (raves/rants) 10:14, 20 July 2006 (UTC)
More changes:

I tweaked some wording. I think the following three points are absolutely essential:

  • DRM "really" stands for Digital Rights Management, i.e. this are the phrase used by providers and users of the technology, and these are the words for which the initialism stands. Critics' attempt to redefine it as Digital Restrictions Management is a rhetorical device only.
As you know, strongly disagree, because of hte following point you make. ww 22:05, 20 July 2006 (UTC)
  • Nevertheless, critics are correct in calling the phrase "Digital Rights Management" loaded, or a misnomer, because there is absolutely nothing about DRM that aligns its use with the provider's actual legal rights. The provider can use DRM to enforce arbitrary restrictions, including restrictions which it is not legally entitled to make.
  • DRM overreach is not theoretical. It has unquestionably occurred. The occurrences may well have been due to mistakes on the provider's part (Adobe said this was true in the "Alice in Wonderland" case) or due to software bugs in the DRM implementation (e.g. malfunctions with Intuit's TurboTax product activation) but they are not hypothetical or potential.
concur, absolutely. ww 22:05, 20 July 2006 (UTC)

Dpbsmith (talk) 13:13, 20 July 2006 (UTC)

  • You're correct, that critics' redefinition of the term is secondary to its actual definition. However, the term "digital restrictions management" effectively characterises their opposition to such systems as a whole, and is an important term in and of itself - hence the mention, with the obvious caveat that it was coined by Richard Stallman.
  • Agreed. That should go in the ever more sparse-looking "legal enforcement" section, perhaps.
  • Agreed.RandyWang (raves/rants) 13:20, 20 July 2006 (UTC)
I heard the phrase before I became aware of Stallman using it. Cannot document it, needless to say, but it is a distortion to claim the term or opposition to DRM, is but yet another rms quixotic crusade. We are not doing well to support the rhetorical devices of the proponents by such comments, espeically in the article. NPOV forbids, in my view. ww 22:05, 20 July 2006 (UTC)
I got curious, so I looked through newsgroup histories and found this post from a Phil Hunt in a May 21 2001 posting where he brings up the term "Digital Restrictions Management". The earliest reference I can find to RMS using the term is in October 2001, but I'm sure he was using it before then.
IMO, I think it comes down to this: DRM technologies were created by people (i.e. copyright holders) who had an interest in defining limits on who could access their copyrighted material. Default access is zero, and you are granted "rights" to use the item. Conversely, critics of DRM look at it the other way: people (i.e. copyleft holders) who have an interest in there being no limits on their copyrighted material view the default access as everyone, and anything that inhibits this is a "restriction". The key difference is that the people who favour "open" want other people's closed stuff (copyrighted music, etc.) to also be open, whereas the people who favour "closed", only favour it for their own stuff, but don't care if other people prefer "open" distribution. This distinction is what makes Digital Restrictions Management a valid term, though most definitely reactive, but it also validates Digital Rights Management as a phrase... whether or not one believes it's a "loaded" term (as Dpbsmith puts it) really comes down to ones personal beliefs about copyright/copyleft issues. That's why we need to be extremely careful with how we present and describe the terms in this article. Ww is quite right in that we can't be pigeonholing the copyleft viewpoint here as some kind of RMS crusade, because it really isn't. -/- Warren 23:03, 20 July 2006 (UTC)
Actually, I'd take some issue with this etymology of the Dig Res Mgm version. I don't think, even for rms, that it's a continuation undera differetn flag of an crusade for open source or rather free as in liberty software. Maybe someone should ask him. I think it is actually an appreciation for the unsupportable extension of holder control via a shaey and probably impossible use of technology, chiefly crypto. Certainly that's the problem I see, as I fully concede that the Mouse (and Metallica's stuff, and all the rest) is certainly the property of <whoever> with the proviso that the law in most places provides for several explicit exceptions. for instance, first sale, in US terminology. My objection is that NO ONE knows how to actually do what the holders have a right to control, and their attempts to do so have been clumcy and an interference with users existing rights. I do NOT defend piracy, though I do note that the people RIAA and MPAA (US) and BPI (UKL) have been chasing aren't very significant menetarily. And my opposition to DRM is not a pro-piracy one. Several active editors on this article share that position I think. That the law permist lawyers to make arguments to that effect is a another issue, and one that should be addressed. Pirates with real economic impact own or control industiral production and distribution facilities. Exagerrated damages are merely PR (or lobbying) motivated and are unwarranted. ww 23:31, 20 July 2006 (UTC)

Would someone mind explaining how we say "...critics are correct in calling the phrase "Digital Rights Management" loaded, or a misnomer..." without breaking the NPOV rule? AlistairMcMillan 19:15, 20 July 2006 (UTC)

Ahmmm. Well, ... By explicitly noting (evenhandedly) that the initials DRM are disputed between two alternative readings. And doing so early and prominently, so that neitehr side ends up using Wikipedia to futher its loaded version. It is not the province of anyone, or any single interest group, to assign a name to something, unless in commercial practice and that requires trademark or similar. I've heard not a whisper of such protection for thsi phrase, but in any case such protection cannot apply ot the underlying technique, only to a particular commercial implementation/product. Languages just don't work that way. Even trademark is not sufficient proctectin in law in some cases as for instance in the case of cellophane and some others, and which accounts for the continued employment of many lawyers at Xerox as they write letters attempting to defend the company's exclusive rights to the name. ww 23:38, 20 July 2006 (UTC)

BTW Something else that probably needs fixed. The sub-sections of the external links section are composed almost entirely of internal links. AlistairMcMillan 19:17, 20 July 2006 (UTC)

Do I hear Pittsburg here? ww 23:38, 20 July 2006 (UTC)
Fixed. Was this what you wanted? :) RandyWang (raves/rants) 23:52, 20 July 2006 (UTC)

I suggest tightening the wording in the intro section to the following (so between the quotes is the entire intro): "Digital Rights Management (DRM) is an umbrella term referring to any of several technologies used by publishers or copyright owners to control access to a specific instance of digital data or hardware. The term is often confused with copy protection and technical protection measures, which refer to technologies that control access to digital content on electronic devices with such technologies installed, acting as components of a DRM design.

Digital Rights Management is a controversial topic. Advocates argue DRM is necessary for copyright holders to prevent unauthorized duplication of their work.[1] Some critics of the technology, including the Free Software Foundation, suggest that the use of the word "rights" is misleading and suggest that people instead use the term Digital Restrictions Management.[2] Their position is that DRM restricts use of copyrighted material in ways not typically covered by most countries' copyright laws. Additionally, the Electronic Frontier Foundation considers some DRM schemes to be an anti-competitive practice.[3]"

I also suggest moving the "E-DRM" section to far, far below. There are no citations of E-DRM and google search is very lean. I made these edits but they were reverted & it was requested that I submit this to the talk page.. 71.232.58.195 22:05, 12 March 2007 (UTC)

I agree with this, the EDRM text just clutters the introduction. It should really have its own section (or possibly its own page). (diff of reverted text) If nobody objects, I'd like to move EDRM to it's own section - the edits to the rest of the introduction should probably stay reverted, as they add little to the article. --h2g2bob 17:19, 15 March 2007 (UTC)

EFF and DBD

Why are they listed in the "Lobbying organizations" section? I'm all but sure they are against DRM. - Sikon 17:24, 22 July 2006 (UTC)

recent edits

One such removed the term criminalization fro the legalites discussion. This was in error as perhaps the most notable effect of much of this legislation is to move litigation from civil court (ie, torts) into criminal court. The act of copying some protected item has not be an a criminal offense hitherto. It is not scare language some of which recetn edits properly elided, but the fact. And so WEP notable. Reply from that editor, others? ww 02:10, 23 July 2006 (UTC)

Actually, I think the anon may be right. Isn't it legislation such as the DMCA that makes it a criminal act, not the technology called DRM? I could be wrong though, I'm not entirely clear on the history. Was DRM only introduced at the same time as DMCA type legislation? AlistairMcMillan 02:14, 23 July 2006 (UTC)
The removal of 'criminalisation' was technically correct, since DRM itself cannot make anything illegal, since it isn't a law. I suggest that we just rewrite the sentence to note that certain legislation enforces DRM by criminalising certain activities: the statement would remain technically correct, and communicate the same basic facts as the original. RandyWang (raves/rants) 02:18, 23 July 2006 (UTC)
But we already have a section on the DMCA that clearly states: that criminalizes the production and dissemination of technology that allows users to circumvent copyright protection methods, rendering all forms of DRM-stripping and circumvention software illegal. Is it a requirement that we have the word "criminalise" in every section? AlistairMcMillan 02:30, 23 July 2006 (UTC)
Fair call - I hadn't noted its section when I took a look at the diff. May as well just leave the change in place, methinks, since it's no less informative than before. RandyWang (raves/review me!) 02:52, 23 July 2006 (UTC)
Actually RW, that's precisely one of the things DMCA makes illegal. AM is correct, even though he framed his answer in the form of a question. DMCA makes research into DRM operation, even if not a single copyright is violated, illegal. See the linked article on Skylarov. Check out Felten's website, and check Macfergus.com for Niels Ferguson's reluctance to tell anyone about the flaws he found in Intel's design, even though Intel is reported to have said it has no objection. Ferguson is concerned about being arrested by some prosecutor with not a lick of understanding of what's going on technically -- as long as a case can be made. This subject is a mess and requires perspective to understand. Even one of the threads which bear on it -- and there's lots, most technical in one way or another. ww 03:01, 23 July 2006 (UTC)

Different from Copy Protection/TMP?

This article says drm is often confused with two other terms: copy proptection, and technical protection measures. Unfortunately, the explanation of the differences was terribly ineffective, at least for me. Here is what it says about drm: "technologies used by publishers to control access to digital data". The article then describes copy protection and tmp as follows: "technologies that control or restrict the use and access of digital media". No wonder people can't tell the difference! Can someone please explain the difference to me and/or make changes so that the differences are clearer? Thanks. Danielx 21:26, 26 July 2006 (UTC)

The difference is subtle at first glance, but there is a big difference: DRM systems are more "active" in that there is often some kind of direct communication between the provider and consumer of DRM content to confirm that the content may be used. iTunes Music Store is a good example of this; if you copy a DRM-protected iTMS purchase to another computer, that computer needs to be authorised over the Internet before you can play the song. A techncial protection measure is more passive... consider DVD's: Content Scrambling System provides protection of digital content, but is built into the product itself but requires no communication with an outside source. Copy protection is again different than both of these; regional lockout and Macrovision are two different technical approaches to preventing DVD copying.
You're quite right in noting that this article could be more clear about this, though. Hope this helps... -/- Warren 21:35, 26 July 2006 (UTC)

Clarifications made to 2nd paragraph

I've removed the reference to DRM being needed to prevent loss of revenue from unauthorised copying, as that's irrelevant. DRM does not prevent loss of revenue except indirecty, it prevents unauthorised copying, distribution or access. Obviously the indirect (hoped for) effect of DRM is one (but not the only) motive for using DRM. (Note that some copyright holders, e.g. Cory Doctorow, claim that DRM causes loss of revenue in at least some cases. That could be in interesting topic to discuss somewhere, but I don't believe it belongs on this page.) In any case, DRM can obviously be applied to works which are given away for free, so the "loss of revenue" argument is at best a side-issue.

I've also removed the description of Digital Restrictions Management as rhetorical. Both Rights and Restrictions are loaded terms used for rhetorical reasons, and it is unfair to single out the anti-DRM POV for special treatment without doing the same for Rights. That would be clumsy, especially in the opening paragraphs, so better to treat both POV matter-of-factly and on an equal footing. Limeguin 04:18, 30 July 2006 (UTC)

As has been discussed previously, we don't give equal validity to the actual name of the thing and a name that critics use to deride the thing. AlistairMcMillan 13:49, 30 July 2006 (UTC)
AM, As you say, it has been discussed previously. And many more times than just inthe last month or so. And it is not as you imply, settled. I was a participant in most (all) of those discussions, on either side on occasion, and I do not see that cosensus was reached as to how to handle this aspect of POV.
Limeguin makes precisely the point I (and many) have been making for a very long time, though using different words. It's NOT permissible to permit one POV to frame the discussion by claiming ownership of a term (in this case the expansion of a 3 ltr abbr, DRM). This IS non-neutral, and WP shouldn't be doing that, per long-standing policy. We should actually BE neutral in our accounts, not merely formally so. A review neutrality here by refering to the discussion on this talk page, much of it now archived though still available, will turn up claims of POV of one kind or another beginign with, IIRC, the very first comment here (in re a rather lower quality and far less complete article). POV problems are not resolvable by adopting (or permitting control of) loaded meaning and connotations for the terminology used. This is the definition of POV in a serious sense, after all. We should certainly leave Limeguin's version (or something like it) of the present phrase and I still think that alternative meanings of DRM whould be early (ideally in the first sentence) and equally prominent. Only then will WP have avoided taking any stance in a very seriously controversial and important issue. ww 19:55, 30 July 2006 (UTC)

I'm sorry but you are either mis-understanding or mis-representing Wikipedia policy. Please read the section "Balancing different views" in Wikipedia:Neutral point of view/FAQ. We are not supposed to give equal validity to both points of view. "Digital Restrictions Management" is a rhetorical device, which is exactly what we should say it is. AlistairMcMillan 20:50, 30 July 2006 (UTC)

Alistair, Digital Rights Management is equally a rhetorical device. "Rights" is one of those terms like Motherhood and Freedom that everyone is in favour of (or at least give lip-service to). If we write as if Rights was a neutral word, and single out Digital Restrictions Management for special treatment by emphasising the rhetorical nature of it without a corresponding, equally prominent note on the rhetorical nature of Rights, we are explicitly supporting one POV over another. We have a better balance by not mentioning rhetoric at all.

I'm removing the reference to the term "propoganda" in the second paragraph and replacing it with "misnomer". It may be deliberate propoganda: I'd wouldn't be surprised to learn that the term Digital Rights Management was invented by some advertising or PR consultant. But let's assume that the choice was well-intentioned and not deliberately chosen to manipulate people's thinking on the topic ("People love rights, and if anyone objects you can say they want to take away the artists' rights"). But we don't know that this was deliberate propoganda. However, it certainly is a misnomer! After all, DRM doesn't manage "rights" at all -- it manages restrictions. I know that some will argue that the Rights in DRM refers to the copyright holder's rights, but that's not true either: to give an example, DRM can and has been used to prevent eBooks from being read aloud. There is no right under copyright law for "no read aloud" rights. Likewise there is no "right" to prevent re-sale, and yet many DRM systems operate to prevent re-sale. Rights are granted by law, not by computer software. (Also, the term "misnomer" doesn't imply deliberate manipulation.)

It is enough to single out Restrictions as a minority viewpoint, used by critics. There are controversies where one side is way out on the fringe (e.g. Holocaust denial). This is not one of them. I'm not suggesting that we give both Rights/Restrictions equal treatment, but I do insist that we don't unfairly bias the discussion towards the Rights POV merely because that's the term used in the popular press. After all, an encyclopedia is meant to do more than merely parrot corporate press releases as the IT press so often does. Limeguin 02:47, 12 August 2006 (UTC)

I've changed "misnomer" to "misleading"; that's the actual word used in the citation, so that's the word we should use.
The way and order in which we present the DRM etymology is about as precise, neutral, and accurate as we're going to be able to get. No matter how much you, I, or other editors believe the "R" ought to be "Restrictions", the fact is that the term "Digital Restrictions Management" wouldn't even exist if it weren't for the phrase "Digital Rights Management", which is the phrase used by the people who created the technology. Please read through Wikipedia:Neutral point of view very, very carefully for a better understanding of why the article lays things out as it does. I've explained this before on this talk page, too, but it basically comes down to this: Even if millions of people called Dick Cheney "The Big Dick", or Microsoft "Micro$haft", that absolutely does not grant us the latitude to pre-empt the official name, as decided by its creators. -/- Warren 03:30, 12 August 2006 (UTC)
W, Great name choice! But I have to disagree that your analogy is apt. Microsoft has no meaning outside product / company identification. Like Kodak (a meaningless term chosen because George Eastmen though 'K' sounds would be helpful in the marketplace, in the account I've heard). Digital Rights Mgmt has such meaning outside mere labeling. Limeguin is correct in this instance that, regardless of intent by its first user, it is an attempt to bias the discussion as it is not any legal rights to which the term refers. DRM schemes are controlling 'rights' that holders have no legal basis for asserting, at least in countries with copyright law more or less consonant with international understanding in the developed world. DRM does not achieve a reduction in piracy, as claimed by its advocates (the pirates with disk pressing plants have not been noticeably impeded), but does have a significatn effect in changing the terms of the legislative debate (such as there has been, ie, almost nil in the US). As such, it's propaganda and NPOV.
I have been arguing in re this article (see archives almsot from the earliest note) that we are stuck with this term (priority has established a fact of name on the ground, just as sandwichs are not called bread holders), but that we should note early, and prominently, that there is considerable controversy about the meaning of DRM. It is _not_ POV to do so, as there does exist a substantial corporate, legal, and public interest in this quite real dispute. It is not merely another quixotic rms v the world crusade, though his voice is prominent. The word 'Rights' in an expansion of DRM is biasing rhetoric and most defintely should be noted here.
Indeed, it should be noted at the same point DRM is introduced, thus doing the best we can to remove the biasing sting. Not somewhat later as one point among many, some legally technical, some cryptographically technical, some computer security technical. We may expect our Average Reader's eyes to glaze over somewhat in those necessary sections (or while following pointers). The controversy itself must be covered, but not necessarily at the very beginning in my view. What should be done is to alert our Average Reader, for whom we are supposedly producing an NPOV introduction/overview in this and all articles, that there's a nomenclature problem. Kind of like highways signs in mountains warning about "Fallen Rocks Next 2 Miles (or 3km, for those with more rational mensuration systesm)".
I believe this so strongly that I will continue to resist attempts by either side to attempt to achieve rhetorical advantage here (in the hope, I suppose, of achieving a similar advantage in the mind of the Average Reader, up which which WP should not put). I have long done so here, and will continue to do so.
I welcome Limeguin to the fray on the side of NPOV and neutrality in the rhetorical wars. ww 18:51, 12 August 2006 (UTC)

About Gerbrant's last edit

(1) The essay is written by Richard Stallman. From the page itself "This essay is published in Free Software, Free Society: The Selected Essays of Richard M. Stallman."

(2) The paragraph about DRM starts with the words "Digital Rights Management software is..." That section is headlined "Digital Rights Management". The table of contents at the top of the page includes the phrase "Digital Rights Management". "Digital Restrictions Management" is mentioned once, as an alternative alongside "Digital Restrictions Malware" and handcuffware".

(3) The intent of the page as a whole essay is clear. Richard is recommending that people avoid using certain words or phrases. The essay does not use the DRestrictionsM phrase throughout, and it does not even recommend it as the only alternative.

(4) While we are on the subject of the FSF (who didn't write the cited essay), they do use the phrase Digital Rights Management "officially". For example, the bottom of http://www.fsf.org/licensing/compliancelab.html.

So if everyone could please stop changing the article to reflect what they personally want to say instead of what the cited source says, that would be real cool. AlistairMcMillan 18:54, 3 August 2006 (UTC)

  1. Who is the president of the FSF. Also that it is a selected essay, means that the FSF supports it. NoExec changed the link to a page showing indeed clear support of the FSF for the DReM expansion.
  2. It has to (otherwise lengthy circumlocutions would have been necessary). It's a list of words and phrases to be avoided. Check the other items on the list - they also include the word or phrase to be avoided.
  3. True, but it has propagated the DReM expansion, among others.
  4. NoExecs link is to a newer page. I don't know why the FSF hasn't made its older pages consistent, but the content of the newer page is unambiguous.
I think NoExecs edit will be satisfactory to us all, so let's just leave it at that. Shinobu 10:24, 4 August 2006 (UTC)
(1) RS wrote the essay, FSF support it. That does not mean FSF wrote it.
(2) Yep, but if they use the term DRightsM, then it is false to say that they don't use it.
(3) Great. But again, if we say "he suggests people use", then that is true. Saying he exclusively uses "DRestrictionsM" is false.
(4) Again. The FSF use the DRightsM phrase. Saying they use DRestrictionsM exclusively is false.
And I'm sorry, but no, NoExecs edit is not satisfactory. If we aren't going to explain the DRestrictionsM thing properly in the intro, perhaps we just shouldn't mention it at all. AlistairMcMillan 00:47, 5 August 2006 (UTC)
Splitting hairs, are we? Anyway, I've seen your last edit, and I really hope everyone is okay with it (I am), because too much squibblingsquabbling has been going on about it already, really. Oh, not mentioning DReM at all would not be NPOV, so that's not an acceptable solution (not for me and, I hope, not for you either). Shinobu 12:42, 5 August 2006 (UTC)
S, I wish to call your attention to a critically important point. I have checked and squibbling cannot be what you meant. If it was not a typo (a problem with which my fingers quiver in digital resonance), I suggest that what was meant was squ_a_bbling and that we correct all references to squibbling here in the interest of (hyper)correctness. Let the squabbling contiue!!
Sigh... Where is Rodney King when we need him? <-- rhetorical (and so appropriate) question ww 19:06, 12 August 2006 (UTC)
:-) Yes. It's the work of the embarrassing little typo fairy. And while we're being hypercorrect: contiue? Seriously though, I think we've squabbled quite enough. Shinobu 01:40, 26 August 2006 (UTC)

DRM = CRAP

Since I couldn't find it in the article anywhere, I thought I'd better note here that DRM is also being referred to as CRAP, an acronym for "Content Restriction, Annulment and Protection". [ælfəks] 00:23, 11 August 2006 (UTC)

Source? AlistairMcMillan 06:58, 11 August 2006 (UTC)
There are a few that show up with a Google search. Here's one.Brian 19:07, 12 August 2006 (UTC)btball
Yesterday, I added the sentence
ZDNet Executive Editor David Berlind also suggested the term Content Restriction, Annulment, and Protection or CRAP for short.<ref>{ {cite web|url= http://news.zdnet.com/2036-2_22-6035707.html |title=A lot of CRAP|accessdate=2006-09-07} }</ref>
just after the sentence explaining that some critics expand DRM as Digital Restrictions Management.
I believed this critical alternative name to be worthy of mention in the article, but an hour later it was removed as "inappropriate" by Warrens. Alphax was disappointed not to find it in the article. I too still believe this alternative name should be mentioned, attributed to ZDNet Executive Editor David Berlind, with some source, but I'm not going to start an edit-war over this.
— Adhemar 07:40, 8 September 2006 (UTC)
Ironically enough, Russians often expand the acronym "DRM" with additional letters so it becomes the Russian word for crap. - Sikon 07:51, 8 September 2006 (UTC)
If there is an authorative source for that, even that snippet of information is worthly of inclusion in the article, IMHO. — Adhemar 12:11, 8 September 2006 (UTC)
[2] [3] [4] are the Google search results for words that are cross between "DRM" and "der'mo" (дерьмо), Russian for crap, and are used to refer to DRM pejoratively - on Linux.org.ru, the "Russian Slashdot", and SecurityLab.ru. Although it probably isn't notable enough to warrant a note. - Sikon 14:49, 8 September 2006 (UTC)
Put simply, it doesn't belong in the Wikipedia:Lead section of the article. The lead isn't your (or anyone's) personal dumping grounds for POV-laden commentary about the technology, or what the Russian translation of the acronym'd format of the name is... in-depth criticism belongs in the body of the article, and things like the Russian translation belong, at best, in a "Trivia" section, and even then it's hard to justify its inclusion as encyclopedic. It doesn't contribute substantially to a knowledge-based definition of what Digital Rights Management is.
And that's what it comes down to, really. The content and wording of the lead section as it stands right now is very carefully balanced to state clearly what Digital Rights Management -is-, and to clearly state the primary controversy. If you or someone you read on the Internet thinks that "DRM = CRAP", fine, but surely you appreciate that it sounds like a churlish joke rather than sober, encyclopedic commentary. It's certainly not important when defining the subject as a whole... at best it goes into the DRM Opponents section. -/- Warren 15:09, 8 September 2006 (UTC)
Indeed, the lead section has been the subject oa considerable amount of discussion here. The current version is unsatisfactory to some, including myself, on grounds that it too readily concedes the terms of discussion to one side with a clear agenda. I favored (see comments above) an earlier and more prominent notice to the reader that DRM is a controversial name for the underlying topic and that there are other expansions. In this case, i agree with Warrens that this addition should not be in the lead, but if present at all, in the body of the article. That a prominent technical journalist coined the term and acronym, perhaps biases it toward inclusion, especially as it has become used in the blogoshere. ww 18:03, 10 September 2006 (UTC)
I looked a bit around and changed my opinion on the Russion дерьмо – I do not consider that worthy of inclusion. I agree with Warrens that Content Restriction, Annulment, and Protection sounds like a churlish joke, but sounding like a joke is not always a good reason for non-inclusion. I might agree that the term suits better in the Opponents section (or a Trivia section) than in the third paragraph.
So the central question is: does David Berlind's term Content Restriction, Annulment, and Protection (CRAP for short) belong in the article? [And if so, should en.w.o/wiki/CRAP link or redirect to the article?]
Pro: Shortly after Berlind coined it, the term made its way through the blogosphere. People (like Alphax) have heard of it – and (might) come to Wikipedia to look into the details of the term.
Contra: It's bound to fall in disuse. (That's a prediction, not a fact. You never know.)
— Adhemar 19:19, 9 September 2006 (UTC)
As suggested by Warrens, I added the CRAP note in the section on Opponents. Let's see if someone objects. — Adhemar 18:53, 12 September 2006 (UTC)

AE vs BE spelling in recent edits

A series of recent edits changed quite a few -ised instances to - ized. While this is an admirable devotion to the UK flavour, it is contrary to WP practice which is officially to allow both, regard neither as 'correct',and to attempt to keep individual articles consistent. The anon editor should refrain from making such revision in future. ww 14:16, 23 August 2006 (UTC)

Removal of examples

The examples section was removed recently and damages the article in so doing. Without examples, the article becomes rather over abstract and so less informative to the Average Reader. Should be restored.

In addition, the examples of softwae which removes various DRM schemes was also removed. It should be restored for exxentially the same reason.

Comments? ww 04:50, 2 September 2006 (UTC)

Review WP:NOT#Wikipedia is not a mirror or a repository of links, images, or media files for a better understanding of why AlistairMcMillan removed those lists. That said, it'd certainly be feasible to make a separate "List of Digital Rights Management implementations" type of article where those lists could live in a fashion more suitable to how we do things at Wikipedia. -/- Warren 05:18, 2 September 2006 (UTC)
I'm familiar with the policy you cite, but suggest that it is wrongly applied in this instance. We cannot convey to the Average Reader, via expository prose only (too abstract as a matter of good writing -- if a criterion is getting an understanding into the mind of the Average Reader), as we have at present, the nature of DRM. If only because some Readers are better at putting together a sense of what's being discussed from a list of examples than from what remains in this article. A fact of human psychology, a charactristic of those for whom we write; we are not writing solely for ourselves here. The lists as existed had the (more or less -- they were hardly ideal, though much better than nothing) considerable virtue of illustrating the issues in concrete cirrcumstances. In addition, several of the items in the list allowed the Reader to contemplate DRM in the isolation of a specific deployemnt instance, unbeset by other aspects of the subject.
So, while the policy is, in my view, a good one, it cannot apply in this instance (or similar ones) in which the list actually contributes to understanding in the mind of the Average Reader. The usual lists I've seen here are certainly to be abhorred and properly so. But not all are so. In some cases, the goal of writing a good ency. article takes precedence.
A separate article has the virtue of keeping length down (not a goal to be followed blindly if it results in lowered explanatory effect in the article) and of avoiding boredom (again not a goal to be followed blindly). Neither list in this case would help with Average Reader understanding if put in a separate article. However, the information in the lists (much of which is not in the rest of the article) should not be lost and so a separate article would at least keep it available, if at the cost of reduced understanding by the Average Reader. ww 14:02, 2 September 2006 (UTC)

Comments? ww 04:50, 2 October 2006 (UTC)

Would it be posible to have a list (short) of Devices, and applications which can be used as an alternative to DRM protected devices, such that people exspressing an intrest in DRM free solutions can see a list, and those who come to the artical, can see who/what is DRM free.

Impossibility of secure DRM?

Would it be worth mentioning that a secure DRM scheme is quite simply impossible to achieve on general purpose computing hardware? The argument goes as follows: Let's consider a DRM scheme intended to prevent copying of music files stored on a home PC. The scheme must clearly allow the user to play the music. Thus all information required to play the song is present on the user's computer. This might include some kind of ciphertext, decryption keys, signatures, certificates, whatever. The point is that every piece of information needed to make the music play is present. So it is possible to write an efficient algorithm which decodes the song and writes the bits to a file. Thus the entire scheme relies on security by obscurity - no-one but the proprietor of the DRM scheme knows the algorithm needed to do the decoding.

Of course, if the computer playing the music has a Trusted Platform Module the argument breaks down, because the official playback application can access keys stored in the TPM that an unofficial "pirate" decoder could not.

Not so... The trusted computing model only protects (defends?!) against software attack. The resourceful pirate will simply pull things out of main memory
Actually, one of the key components of Trusted Computing is Memory Curtaining, which would prevent pirates from pulling a key or the music out of main memory. Trusted Computing should secure DRM, although any implementation bugs probably would make this harder. -FutureDomain

Why make it so difficult? To play the music file it must at some point be converted into sound waves in the air. Now, even if you included a little big-brother device in every single microphone, which phones home about it every time the microphone is used, it is still perfectly possible to build a phonograph from scratch. That is, no matter how much encryption and trusted hardware you stick into a music player, DRM can still be circumvented with a device invented before electricity was even used for lighting, let alone media playback. DRM is not a matter of making copying content impossible, it is a matter of making it less convenient than buying it by imposing a hassle upon anyone who would wish to circumvent it. Stallman got it right. It is a malicious feature aimed at making it painful to do something yourself rather than paying media distributors from doing so (redistributing the media from artist to user ). 137.205.236.52 02:31, 20 March 2007 (UTC)

Let Me Get this Straight...

Am I corrent in assuming that DRM makes it impossible to play non-certified files on DRM complient OS's. What Im getting at is, well Ill just show u:

1. Download non-DRM identified content (i.e. Content off of Limewire that doesnt have a licence.

2. Open it in Windows Media Player.

3. WMP scans for DRM Header.

4. If it can't find one it doesn't play it.

5. Then reports you for using illegal files.

Am I correct in assuming that this is the process that DRM compliant software uses?

Thanks,


H a m m o

That's not the case. DRM is like encryption for files. If a file has DRM, it will only play on certain machines, and/or for a certain time limit, etc. If a file does not have DRM (ie, it's unencrypted), it can be played on any machine forever.
To play DRM'd files you need a special media player (whichever the authors tell you). Normally that's WMP or iTunes. But you would not be able to play it with an open source media player (eg vlc).
Things you get on peer to peer networks are DRM-free, but there may be copyright issues.
A different, but related issue is that some companies install spyware on your PC (normally through a trojan), which can stop you burning certain types of CDs. See Extended Copy Protection for an example. The EFF's website may also have some information.
It's worth noting that Windows Media Player has a privicy statement somewhere in the options, and it's not that bad (eg, they won't send what files you play to anyone, if I remember correctly). However, using Windows Vista will completely undermine that.[5]
Some good and bad news there I suppose --h2g2bob 13:27, 24 October 2006 (UTC)
Actually, it depends on the specific DRM being used. Some systems are designed to allow only authorized software to work, and block everything else. Others are designed to specifically block forbidden software, while allowing both permitted and unknown. -- kenb215 talk 02:46, 12 November 2006 (UTC)

I removed this from external links, but it's still quite interesting so I'm shoving it here.

  • Paradigmatic example of legislators hearing a very general computer buzzword ("caching" ) associated with infringement cases and banning it, not realizing it was a universal computer memory technique. Article itself demonstrates difficulty of explaining this to general public, writer does not seem to realize every computer and most digital devices of any kind would have to be destroyed.[6]

--h2g2bob 14:14, 2 November 2006 (UTC)

POV removal

This article has a significant POV against DRM. This is probably inherent of the topic, as most Wikipedia editors tend to be computer literate, and most, thought by no means all, computer literate people (me included) tend to be against DRM. It will probably be hard, perpetual work, but I am going to try and make the article more NPOV. If you have any complaints, please post here before reverting to discuss. I will try to check the page as often as I can. -- kenb215 talk 02:54, 12 November 2006 (UTC)


<below from User talk:Kenb215>

I've reverted your entire change to the lead section of this article. Sorry. We've been through the debate about the positioning and importance of the criticism of the technology, more than once, on the talk page. Please review those discussions. The key here is that we define "Digital Rights Management" -- literally, those three words and their precise meaning -- before we get into criticism and politically-motivated rebrandings by detractors. This is vitally important for an encyclopedia that prides itself on neutrality, and aims for high informative value. Hopefully you're in agreement with this. Thanks. -/- Warren 06:24, 12 November 2006 (UTC)

I saw the edit as leaving just an alternate name in, while moving any politically-motivated debate for after the lead section, as it is in there now. But if consensus is against this, I'll stay away from the lead for some time. -- kenb215 talk 17:25, 12 November 2006 (UTC)

Lead sentence

I changed the lead sentence from this:

Digital Rights Management (generally abbreviated to DRM) is any of several technologies used by publishers (or copyright owners) to control access to and usage of digital data (such as software, music, movies) and hardware, handling usage restrictions associated with a specific instance of a digital work.

to this:

Digital Rights Management (generally abbreviated to DRM) an umbrella term for any of several technologies used by publishers or copyright owners to control access to and usage of digital data or hardware, and to restrictions associated with a specific instance of a digital work or device.

My main goal here was to reduce the number of parentheses. Three is far too much for a lead sentence in an encyclopedia article. I also introduced the phrase "umbrella term"; it seems appropriate, since specific implementations of DRM use different terminology. -/- Warren 21:35, 15 November 2006 (UTC)

Example techs

I would find it informative if the article would mention some examples of common DRM-formats(like windows media drm etc) linked to corresponding articles.

Another aspect of DRM

There's another aspect regarding DRM that is not really touched on in this article. I just bought Half-Life2. It's version of DRM requires that users have an Internet connection and an account with a webserver in order to play the game (either single-player or multiplayer). That's all fine and good, but that means this game will only be playable so long as that webserver remains operational. Should the company ever go under (like, say, the makers of the Thief games did), then Half-Life2 and its spinoffs will likely become unplayable. To just add such a statement would probably violate NPOV and NOR - are there any sources that could be cited regarding this concern? There is a brief reference to DRM affecting archivability of data, but that's not quite the same thing as affecting the operation of purchased software. (Plus the DRM rights holder for the game has also demonstrated its ability to choose who has access to the game/data and who does not). 23skidoo 15:42, 3 December 2006 (UTC)

Try this and this. There hasn't been any other serious analysis of/research into this sort of thing, as far as I know. --Tom Edwards 15:58, 3 December 2006 (UTC)
This, too. --Tom Edwards 16:00, 3 December 2006 (UTC)

Lucky Green / Trusted Computing

I got a question for any experts on the subject: On the internet, there is an abundance of sources (all of them several years old, AFAIK) speaking of the Lucky Green patent incident. For underinformed laymen like me: The story goes something like, he filed a patent on using Trusted Computing for commercial purposes right after a conference where some Microsoft spokesperson talked about it, negating a commercial intent of Microsoft on the grounds of "we didn't even know it could be used for that". Sorry for any inaccuracies... I just wondered why there is no mention of that incident anywhere on wikipedia? Mostly, I'd like to know how things finally turned out, because there don't seem to be any up to date sources. Kncyu38 14:51, 30 December 2006 (UTC)

HDCP Key Revocation

I believe that this article should, whilst not delving completely into the topic, mention the safeguards Big Media had built into HDCP in the case of a key being discovered. If the discovered key belongs to a hardware device (HDTV, BluRay player etc.) the content providers have the authority under the license to revoke that key, potentially leaving the device in question unusable for high-definition content. It's an important topic in the gamut of DRM and one that isn't often talked about. —Preceding unsigned comment added by 85.211.140.78 (talk) 08:59, 7 September 2007 (UTC)

I agree this is an interesting topic, but would argue that it properly belongs under the HDCP page, rather than DRM Ianbetteridge (talk) 16:21, 25 February 2008 (UTC)

merge of Authorization Certificate into this article

This article does not deal, except in passing with implementational details, and so the proposed merger is inappropriate for this article as it has developed. It is already somewhat long and additional detail would be ill-advised for that reason. With the immiment release of Vista, DRM will be a very large topic as Vista has builtin degradation mechanisms which are poorly designed, forcing owners of expensive peripherals to junk them if they wish to run Vista in a protected data context. See Peter Gutmann review of the cost implications of Vista for some of the gory details. This article will be expanding considerably in the near future. I suggest we leave implemenational issues to other articles. I do suggest a link to the Authorization Certificate article here however.

Opposed. ww 00:50, 9 January 2007 (UTC)

Agreed, removing merge tags. -- intgr 06:35, 9 January 2007 (UTC)

Controversies Heading

"Some WMDRM restricted files will install spyware such as Zango when the user agrees to retrieve a license to play the file," has been marked as "Citation needed" for several weeks now. What is the timeline for removing something like this? Any attempts I've made to find reputable sources have just led back to Wikipedia. Leaving this type of information in the article only makes it more difficult to find neutral third-party support later. I would just go ahead and delete it, but I am obviously very new to editing. Nonetheless, I move that this bullet should be deleted if third-party references are not found within the next couple days. TomTwerk 08:51, 6 February 2007 (UTC)

The short answer: be bold. :)
The longer answer: There is no official timeline; several weeks is probably enough, especially if you tried looking for sources yourself. If you find something really dubious and without sources, you can remove it immediatelly, as the burden of proof lies with whomever wants to introduce new information, not with who wants to remove it. (Though naturally you're expected to act civilly when someone re-adds it, or disputes your removal) -- intgr 09:15, 6 February 2007 (UTC)
I have personally experienced this type of attack embedded in a license key, perhaps not from that exact company. With rewording to make it historical it could be 100% accurate for sure. I am not sure if this is currently possible because the security in windows media has been greatly enhanced. Group Policy Manager can also be used to completely disable downloadable licenses such as these, thus eliminating the problem entirely (while not allowing the content to be played, chances are you didn't really want to see such trick content in the first place, it was probably a case of not knowing what it was until too late) Zaphraud 08:17, 11 September 2007 (UTC)

Apple's Jobs Urges End to Copy-Protected Music Files

Apple CEO Steve Jobs stunned the tech and music industries Tuesday with a surprising challenge to the music industry to allow online stores — such as Apple's iTunes and Napster — to sell digital music files without the so-called digital-rights management (DRM) anti-piracy controls. http://www.foxnews.com/story/0,2933,250576,00.html Crocoite 01:51, 7 February 2007 (UTC)

This probably qualifies only as WP:DUST MikeURL 20:16, 12 February 2007 (UTC)

Nonpersistent DRM

I believe there should be a mention and short summary of Nonpersistent DRM. Here is a verbatim quote from Business Week's article A Few More "Thoughts on Music". I've bolded the most noteable part.

"Nonpersistent" DRM

There's another option that involves a different approach to copyright protection. It's called "nonpersistent" DRM. Karl Hirsch, the CEO of a DRM technology firm called Protexis described it to me like this: When you buy a song from an online store, it comes protected in such a way that it goes only to the person who bought it. Once you prove you're the person who paid for it, the song is "unwrapped," after which you have essentially no limits on what you can do with it. Put it on an iPod. And a Sansa. And a Zune, if you like. Plus three computers you have lying around the house—whatever suits your fancy.

This is pretty close to the way things works with a CD now. When we buy a CD, we can make copies for friends on a cassette tape or a recordable CD. A friend visiting with a laptop can rip the tracks from your CD to his computer, without having to pay the record label for the rights (although the industry considers this is a no-no—but that's another story, or column as the case may be). But the most important thing is that most people who buy a CD use it honestly after the initial transaction takes place.

And that transaction would be tracked by an independent third party, responsible to both the music retailer and the labels to make sure everyone gets paid. If Joe's Online Music Bistro sells 10,000 copies of the latest Norah Jones single, while iTunes sells 500,000 copies, each vendor's numbers get reported to the label the minute the song gets "unwrapped" by the consumer.

Under this nonpersistent model, the label and the artist still get paid for the initial transaction, which is by far the most important transaction, after which the consumer operates under an honor system, which in truth most people follow.

Most people. But not all people. You can augment a nonpersistent DRM system by adding limitations to the file once it has been unwrapped, Hirsch says. You could create a second layer within it that limits the number of copies you can make, but which is device-agnostic, meaning you could play that limited number of copies on whatever combination of devices you chose. Naturally Protexis offers just such a service—in the outlined scenario it would be the trusted third party that tracks and reports on sales. Hirsch's idea is certainly interesting.

--Eptin 20:01, 9 February 2007 (UTC)

Agree - this section is definitely worthy of inclusion. --Teque5

OK - We can certainly cite that (not quote verbatim). It does look like rather marginal marketing fluff to me. The same technology, with someone new trying to get in on it. How are they going to persuade everyone to interoperate with their format for instance? Ideally we need a more technical reference to put it in context, so we can understand how to incorporate it into the article. 172.213.231.215 08:02, 18 August 2007 (UTC)

SECTION: Inclusion within GNU General Public License version 3

The following block of text was removed from the frontpage because it was poorly integrated and lacked a clear relation to the article. Feel free to add it again and comply with wikipedia standards. This looks like a copy-paste to me.

Wikinews has related news:

The first proposed draft of the GPLv3 (released on 2006-01-16) contains language intended to neutralize the harmful effects of DRM (interference with users' rights to examine, alter, and redistribute) when implemented using GPL'd software. Although the draft in no way prohibits the use of GPL'd code in DRM systems, it does require binaries (or source code) to be distributed not only with source code, but also with the necessary cryptographic keys and other required mechanisms needed to modify the software and still have it interoperate. It also contains language intended to exclude GPL'd DRM code from the scope of the DMCA (and similar statutes elsewhere) anti-circumvention provisions.

—Preceding unsigned comment added by Teque5 (talk • contribs) 10:12, 13 Feb 2007 (UTC)

NPOV dispute

I tagged this article with the NPOV tag for the following reasons: Even the first paragraph makes me frown, wikipedia has stated that an article should describe the article, not be a page about critisism about the subject. My suggestion for fixing this would be to split this article into one article talking only about the technical meaning of drm without any personal opinions being drawn in and one discussing critisism of DRM showing both sides of the debate. Lyml 20:16, 15 February 2007 (UTC)

Wikipedia's WP:NPOV policy very strongly discourages separating all criticism off to a separate article. The only generally acceptable case where this is done is if WP:SUMMARY-style article editing is being employed to reduce an article's overall length. Aside from that, there's really not all that much that can be said about the technical aspects of "DRM" in general because it's a broad term that covers a wide range of technologies and implementations. -/- Warren 20:22, 15 February 2007 (UTC)
After reading this article again, aswell as reading through the neutral point of view articles I see your point, however I still think this article is using to many loaded terms and I have as a response to that tooned down the digital restrictions section. That is, I removed the bold wich gives a strong emphasis on Digital Restrictions Management to make it into a milder tone removing focus from what seems to be the most blatant POV piece of this article. Lyml 23:54, 15 February 2007 (UTC)
Sure, cleaning up unnecessary POV or general bias is welcome. -- intgr 16:28, 16 February 2007 (UTC)
The term "Digital Restrictions Management" was put forth by detractors of the technology, sure, but the phrase is quite widely used and is important in framing the debate that consumes most of the article... are they rights or restrictions? It's an important part of the subject being discussed -- it's a generic term, not a trademark or something, so the definition itself is up for debate. Bolding it in the lead also helps reduce the amount of vandalism that we get from the vandals who want to come in and edit the article to lead off with that term, instead of "Rights". That may sound like a dumb reason, but it does actually work. -/- Warren 22:52, 17 February 2007 (UTC)
I am opposed to bolding it like that personally I don't even think it deserves a place in the summary, Digital Restrictions Management is as you said it just a term put forth by by opposers. Having it like this is about equal to writing: "The Pro-Choice choice movement known as the anti-life movement by..." in the pro-choice article about abortion. We shouldn't be pushing for a deragatory term used almost exlusively by opposers of the technology as the same could be said about the abortion debate names. Protecting it against vandalism by bolding it in an attempt to appease the vandals is not something that should be done. I'm removing the boldness again as it puts to much focus on that term and shows a glaring POV in the article. Lyml 18:41, 18 February 2007 (UTC)
Your objection (or many similar variants thereof) has long been reflected, almost from the first comment on this talk page, (much now in the archives, which you should review for the background to the current structure and phrasing of sensitve parts of this article), and has been the subject of considerable to'ing and fro'ing for quite some time. My own preference is quite different than yours. I think WP should not allow DRM to be exclusively or most prominently read as Dig Rig Man, for I think that is POV and allows a polemical control of the naming of the subject. I have long advocated for early and prominent placement of the Dig Res Man reading, so as to reduce that particular sort of NPOV. I have acquised to the views of others, including Warrens in this and settled for less prominent placement than I think NPOV. Do please review early posts on this in the talk page. ww 20:26, 18 February 2007 (UTC)

(indentation reset) I have looked at most of the earlier posts both in the archives and on this talk page. And I can say the following: 1. I understand that the term Digital Rights Management is a term coined by the content-industry, an industry which has a very biased opinion about this technology.
2. I understand that calling it Digital Rights Management would be missleading as it doesn't actually manage any legal rights upon the user only restrictions.
3. I understand that calling it Digital Restrictions Management would perhaps give a more accurate description to someone who has none or slim to none understanding about the DRM concept.
However:
4. It is an undisputed fact that this technology known as DRM is by the vast majority who knows what the acronym stands for known as Digital Rights Management.
5. It is an undisputed fact that this page is to be an encyclopedic article about the technology known as DRM.
6. It is an undisputed fact that in an encylopedic article one should not be pushing for a particular organisations opinions upon the readers.
Consider theese situations:
In the article about pro-choice (abortion movement) the opposition strongly disagrees with the name pro-choice, since it doesn't give any choice to the woman, therefore they think that the term anti-life is more suitable and adds that to the article about the pro-choice movement.
In the article about microsoft, opposers of microsoft thinks that since microsoft doesn't really create software, they create suckware, they add MicroSuck into the article about microsoft and claim it is a more suitable term.
In the article about meat, extreme opposers to the meat industry thinks that meat is a bad term not really describing the suffering the animals have to go through so they add Murder into the begining of the article. etc etc
Not all of theese analogies will be apt, however, unless you can give concrete reason to why the alternate expansion Digital Restrictions Management is so different from all of theese situations that it deserves to be in bold in the very begining of the Digital Rights Management article I don't see a reason. For now though, I propose that it stays in the begining but not bolded like that. This action still gives it a very strong position and I feel that sometime later a more suitable place for the alternate expansion could be found, perhaps in a category named critic of DRM. Now becouse the alternate expansion is very tasteful and still informing about how the technology works I think it deserves a place in the article, just not such a prominent one and especially not bolded like that. Lyml 23:39, 18 February 2007 (UTC)

We've addressed all this in prior discussions. You've yet to bring anything new to the discussion that should lead us away from giving the most common alternate expansion some prominence. Look, I appreciate that you're new to working on the encyclopedia, so I encourage you to read Wikipedia:Neutral point of view and its ancilliary articles, in their entirety, so that you can come to an understanding of how we're supposed to present conflicting views. Have a look at Wikipedia:Consensus, too. User:Ww and I may have strongly differing viewpoints in the the issue of the prominence of "Digital Restrictions Management", but we've all invested a lot of time and thought into the lead section as it stands now, and IMO it's a satisfactory compromise. We're not talking about promoting offensive or derogatory terminology to the lead section here; it's merely a different, perhaps equally valid way of defining the name of the thing we're talking about. Read the articles on right and restriction for further backgrounding on the issue at hand. -/- Warren 00:56, 19 February 2007 (UTC)
Agree with Warrens. Digital Restrictions Managment is a commonly associated term, it is entirely encyclopedic to make the link early on. Further it is a succinct way of representing an major viewpoint on the subject. I think it still needs more prominent placement of technical as oppose to moral/legal objections to DRM and I may add those when I get a chance. 172.213.231.215 07:25, 18 August 2007 (UTC)

It's a perfectly acceptable and neutral to call Digital Restrictions Malware Digital Restrictions Malware, because it objectively fits in the description of restrictions (its only purpose is to restrict) and it is a malware, in the meaning that it's software installed and used against the will of most of the people who suffer it, and whose purpose is to reduce functionality, jeopardize fair use, and turn others' computers against their owners in the benefit of a much ethically questionable third-party entity. Therefore, I propose that "DRM" and so-called "Digital Rights Management" is made to redirect to Digital Restrictions Malware. 82.159.69.56 08:35, 30 September 2007 (UTC)

I tried to add a link to a paper that lists many of the obstacles in implenting DRM. It's: Challenges in designing content protection solutions. The paper was written by a company that sells DRM products. However, the paper itself is completely technical and does not endorse any product. The link itself is to a mirror of the paper (the authors website) and not to the vendor. Are there any opinions on whether or not it can be linked to according to the Wikipedia policy? Lohat 14:46, 16 February 2007 (UTC)

Yes. Cited papers needn't be unbiased/neutral, as long as it is clear from the article, who holds these positions, and implies what biases they might have. For details, see describing points of view, and reliable sources. Note that these are guidelines, and not policies. For neutral papers by recognized (enough) sources, this needn't be done if the position is not disputed. -- intgr 16:26, 16 February 2007 (UTC)
What Intgr said. Especially if the paper is as you represent. ww 20:28, 18 February 2007 (UTC)

Thanks. Actually, there is no bias there (to the best of what I saw). I will add the link to the document. Please let me know if anyone thinks it is inappropriate. Thanks. Lohat 09:49, 21 February 2007 (UTC)

Copy-restricted gamesaves

The article says:

The Playstation 2 version of Ape Escape: Pumped & Primed creates copy-restricted game saves which cannot be transferred between memory cards. This is the first known instance where a publisher has enforced DRM on private data, rather than just data copyrighted by the publisher.

I'm pretty certain that a few Dreamcast game saves were also copy-restricted, long before that. Phantasy Star Online, for example. - Stormwatch 00:51, 19 February 2007 (UTC)

Dat's Real Messed

DRM is so stupid, why qould I pay for an AAC that I cant even make use of when I can P2P an MP3 for free! DRM doesnt manage rigths it takes them away! RealG187 18:19, 5 March 2007 (UTC)

Society long ago made a determination that cretivity was to be encouraged, and so created an incentive to do so in the form of a limited exclusive right to benefit from the use of the created material. There have been several attempts to extend that right into perpetuity; (the Conger, ended with the Statute of Anne around 1700) was an early example, and today's overreaching by the lawyers and the purblind another. Your objection should probably be addressed to that aspect of copyright, a good deal of which is included in current approaches to DRM. The blinders with which the suits and lawyers have (mis)specified desired behavior (as a matter of law), or misunderstood the possibilites of the mechanisms available, or that the technical folk have misunderstood and misrepresented it to them, are in my view the probable causes. Poor engineering, hubris, greed, stupidity, ... It's an old and probably eternal story. Some of the worst of which is reflected into legislation on the subject by legislators who are even less informed than the rest, and even more rash (likely in the service of what are called lobbyists in the US, and other things elsewhere).
And there is surely annoyance -- I suspect you share -- that the artists themselves are, as things are currently done, rarely those who benefit from that grant of exclusivity. The tangled tale of Creedence Clearwater is a ghastly exemplar. Lots of good music was almost certainly lost because of that idiocy and greed.
But again, it's not copyright itself which causes such distortions and injustices, but assorted other mechanisms including artist blindness toward the law and its machinations, which are the offending party. Would you object to paying for a song in some form if all or most of the payment went directly to the artists?
But, yes, it's all very annoying. ww 18:37, 5 March 2007 (UTC)
This is not the right place to debate your points of view. -- intgr 07:49, 6 March 2007 (UTC)

Introduction, 2nd paragraph

Last sentence, 2nd paragraph, Introduction section: "And usually have, as the legal uses permitted in law are hard to match to the technical (ie, in almost all cases cryptographic systems) properties of the various DRM schemes." doesn't make sense to me - what usually has, and what is it that they usually have? It isn't clear to me - you mean most DRM schemes have additional restrictions? But that's just what was said in the previous sentence. And it isn't good style to start a sentence with 'And'. Maybe the author could clarify a bit, or reword it? Awmorp 14:48, 13 March 2007 (UTC)

My interpretation is that this is intended to note that cryptosystem designs permit certain things and not others, and that the intentions and desires of copyright holders rarely match. I would add somehow, that what the technical aspects of a DRM scheme rarely matches the actual legal situation of the copyrighted material. For instance, there are legal exceptions (statutory in some cases and common law in others) to the exclusivity of copyright holders privileges. For instance, parody use, quotation in reviews, radio broadcast, private use of sheet music, first sale (in the US) and fair dealing (Commonwealth), .. .None of which may the copyright holder prohibit. Someone should squash all that into a single replacement sentence. ??? ww 06:03, 14 March 2007 (UTC)

Table of DRM Technologies

I think the table should be organized either alphabetically by technology or chronologically. What order makes most sense and why? Stagefrog2 01:06, 19 March 2007 (UTC)

While alphabetic ordering is likely to be the most fair, it is inherently arbitrary. I'd vote for chronological ordering, but that introduces the problem of getting reliable release dates. -- intgr 03:26, 19 March 2007 (UTC)

Cleanup

Doing some cleanup to this article. A lot of it appears to be original research/personal knowledge and needs sources and attribution. Also, a lot of sections can probably be condensed into a representative example or two rather than an exhaustive list (proponents, opponents, controversies, etc.) A good bit of the article also reads like an anti-DRM essay, which, while I fully understand (I hate it too!) isn't really good for an article. Seraphimblade Talk to me 21:32, 30 March 2007 (UTC)

The second sentence of the article needs some work. No explanation is given why copy protection and tpm are distinct from DRM as claimed (which they aren't really anyway; they're under the "umbrella term") - the definition given for them just regurgitates the essence of DRM from the first sentence. How about moving it to the intro section? Also "scheme" seems to be overused in the article. Ripe 16:06, 1 April 2007 (UTC)

Ripe, I've reverted your changes to the lead section. Un-wikilinkig important words that are key to understanding the nature of the contention between "rights" and "restrictions" does nothing to aid reader understanding. Also, when working around acronyms, always write as if the acronym is fully expanded. Sentence formulations like "Some DRM such as FairPlay" makes no sense from a linguistic perspective. That's why words like "scheme" and "technology" are employed. Using acronyms in general is a bad idea because it leads to lazy English, and if there's one place in the article where we absolutely should not be lazy, it's in the lead section. -/- Warren 04:02, 2 April 2007 (UTC)
See Shinobu's discussion above; there seems to be consensus that that 'rights' in DRM means "access rights". Wikilinking to legal rights in that context is not correct. Legal/ethicalrights to fair use & personal property does have place in the discussion, but not in the context of defining the R in DRM. I unlinked restriction because it goes to a redirect page that's not informative. The applicable entry is the general usage one, which doesn't have its own page because wikipedia is not a dictionary. Being pointed to that disambig page adds nothing to the knowledge of anyone with a grasp of the English language. it's not even the first occurance of the word restrict in the article. Ripe 15:03, 2 April 2007 (UTC)
Actually, both variants of the term apply in some measure. How, precisely? It depends on who you ask. Some people view it in technical terms (typically groups like Microsoft that peddle a technological DRM solution; focus on "rights management"), whereas others such as the FSF draw more attention to the legal and moral issues; focus on "digital rights". Which is correct? I don't think there's a single correct answer here, nor are we going to have any luck finding a definitive declaration. We don't even know who coined the term!
As to the wikilinks: "Rights" are something that you're granted as an entitlement by law, whereas "restrictions" are focused more on what you aren't allowed to do. The wikilinks are there to help people gain some contextual understanding of the words themselves, which a simple dictionary definition isn't going to be sufficient to do. True, the restriction article is nowhere near as cohesive as right, but these are the words at the core of the debate. Read through Wikipedia:Only make links that are relevant to the context, and note, especially in the example at the end of the article, that it is suggested that linking simple words with complex meanings can aid in understanding. -/- Warren 23:38, 2 April 2007 (UTC)
I still strongly disagree on both. Since the legal-rights interpretation doesn't have a verifiable source, the interpretation shouldn't be asserted by wikilinking it. On restriction, the very first item in the wikilink policy that you pointed to says to not link plain English words. There's no special meaning of the word specific to DRM. Ripe 01:49, 3 April 2007 (UTC)
Should be in a lot better shape now. The article's currently at 33 kB, down from 57 at the beginning, and a lot of redundancy has been trimmed down. Also added sources where I could find them, some plausible but unsourced statements are left fact/attribution tagged. Definitely an important subject, and has the potential to be on the main page someday, hope to see it there! Seraphimblade Talk to me 18:13, 8 April 2007 (UTC)

Implementing DRM

What about adding a section on implementing DRM? The whole article seems to be focused on the DRM controversy, and while thats needed, it would be good to have a couple sections on how it is implemented.

FutureDomain 14:28, 5 April 2007 (UTC)

DRM- the Mis-Understood monster?

I guess I know where the negativity surrounding DRM comes from. Music should be free, art, video, audio files should be free for the taking for anyone who wants them.

This is what our society has become- idiot elite running the show, every 12 year old with an Interweb connection- a pirate on the high seas; i've seen all good people filled with a boundless sense of entitlement that spans generations...

Reading some of the above comments- makes me more concerned about the overall understanding of DRM as a technology, the reasons for its use and why DRM will be around for EVAR, more powerful and even more restrictive than it is now.

Consumers and governments cry for interoperability- keep in mind the phrase, "Be careful what you wish for..." -Interoperability will provide for a higher level of restriction and control and even less freedom for a thing which was never meant to be free in the first place.

I can't go into your house and rip that CRAPpy water-color your kid did off the fridge and walk out and you should not be able to download my bands music without paying for it. Okay, I'm not in a band, I'm a nerd and I hate like floppy disks that I can't play my iPod music on my Zune- and that is the big issue. Or is it(?)

Is the whole "controversy" (which isn't really a controversy :~) based on the lack of Interoperability or is it that people would rather steal media than paying a few bucks a month to access it legally?

Artists, vidoegraphers, music groups have the right to protect their media from theft, right? Then surely they have the right to be able to monetize their assets.

Right now, the only way to accomplish both of those goals is through use of a file or application level DRM solution. DRM like most ScoobyDoo villians is not a Monster but soon, thanks to DRM, you will be able to download and stream every Scooby Doo episode, anytime, from any machine/handset. I think some of us here owe DRM an apology.

-dwyane hoobler

dwyanehoobler@hotmail.com —The preceding unsigned comment was added by 75.212.244.235 (talk) 08:39, 9 April 2007 (UTC).

DH,
You misunderstand the purpose of copyright. Since the Statute of Anne ca 1710, copyright has not been an unlimited grant of exclusivity to a creator or assignee. That Statuteextablished that the grant was for a limited time. Assorted other enactments by, for instance, the US Congress have further restricted the copyright grant. For instance, no band can establish their own royalty rate for broadcast -- it's handled by a joint mechanism (ASCAP and BMI in the US, and BPI in the UK) and by the print copy clearance mechanism for Xerox copies, the settlemenet the US Supreme Court made for video tape in the Betamax case, ... The piano roll folks also got a exception about a century ago, and so on. See Lessig's Free Culture for the historical background. So your assumption of an unlimited grant is ill made.
In fact, the assorted disputes today about DRM (some of which is reflected on this talk page and its archives) is about what provisions to make for this new media... ww 03:52, 6 May 2007 (UTC)
I'm against DRM because it means that the user and owner of a computer hasn't control over the system. I can't accept that. --mms 20:29, 29 July 2007 (UTC)

DRM always leads to the loss of the content by the person who paid for it. Just wait long enough. The company will go out of business or the software will be upgraded. You have no control of what you have paid for. Consumers lose in the end. —Preceding unsigned comment added by 72.66.2.69 (talk) 03:39, 19 March 2009 (UTC)

And the artists don't lose? I can steal any song, movie, or game from any company at any time. The only thing requiring me to compensate the artist is my conscience. This is not sustainable, and this is not right.
-Eric
eric-the-blue@hotmail.com
Why isn´t conscience sustainable? Are people that bad? Besides, I thought the law enforcement agencies had been handling copyright enforcement up till now, why should we let buggy (ie. they will get it wrong, and probably go beyond the law anyway, given who they´re written for) computer programs handle it instead. I personally don´t want to let computers rule my life, they´re a tool, not a god. —Preceding unsigned comment added by 91.105.253.209 (talk) 11:31, 5 March 2010 (UTC)

Full DRM?

I found that there are some players claimed that Full DRM is supported. And most of them are having DRM ported in the chip.

What is Full DRM? Is it specific DRM technology that provided by microsoft? I wonder if DRM is ported in the chip is stable for different DRM site and usage scenerio, as those players are low cost comparing with others in the market. I really doubt about what does "Full DRM" means.

By the way, if it is support DRM 10, does it mean that it is able to do all DRM feature, such as metering?

Any idea? —The preceding unsigned comment was added by Chcchris (talk • contribs) 03:43, 11 April 2007 (UTC).

"Full DRM", like many phrases, has no particular agreed upon meaning. DRM scheme A has been incompatible with DRM schmee B and both with DRM scheme C and so on. I suspect what's involved here is marketing puffery from the player maker or vendor. Like much of the marketing blarney we encounter, it has little actual meaning. ww 03:57, 6 May 2007 (UTC)


Proper casing: must not use capital letters

This is obvious and shouldn't have to be explained, but digital rights management is not a proper noun: i.e. it is not a protocol, a publication, a standard, or anything else that would make it deserving of capitalisation in the English language. Therefore, it absolutely must not be capitalized. I ask an administrator to fix this error as soon as possible. (The correct title has an edit history, but it is devoid of any article content.)  –radiojon 05:01, 26 April 2007 (UTC)

That's a fine opinion to have, but your assertion isn't backed up by reliable sources. The vast majority of our sources (and a majority of what you're going to find in use around the Internet) use capital letters. That's why Wikipedia does the same. If you want to demonstrate otherwise, do so with sources, not with an emphatically-stated opinion. -/- Warren 05:09, 26 April 2007 (UTC)
A google search will show that there is no standard for capitalization. Based on Wikipedia's manual of style this should be changed to lowercase letters, as "digital rights management" is not a proper noun. Whatever we decide on, though, please keep it consistent throughout the article. Currently the titla and lead section use lowercase and the rest of the article uses caps. Rhobite 03:42, 15 May 2007 (UTC)
Warren is wrong in his assertion as per Rhobite... even the title of the article has the correct usage!!!--Cerejota 04:22, 18 May 2007 (UTC)
I have corrected this articles use of capital letters. It was only a minor problem, and only three letters were changed to their lowercase version. Lyml 08:03, 24 May 2007 (UTC)

key leak - yes or no?

Are we going to mention the Blu-Ray encryption key or whatever it is (I'm not entirely sure) leak? On either this page or the Blu-Ray page? and if so, is anyone going to post the key, or is it going the be mentioned without any indication of what the key is? I think we should, but I'm not very boned up on what the rules are, and I'd be reluctant to do it myself anyway as I don't really get the full issue. So what's going to happen? --Anoma lee 02:44, 3 May 2007 (UTC)

We certainly should note it. I'd suggest we be bold. If you understand the issue (and ideally can source it), I'd suggest that you note it here. With perhaps a pointer here from the Blu-ray article. And if you can't write it up fully, an idication that Blu-ray DRM may have been compromised might be appropriate. Be bold... ww 04:05, 6 May 2007 (UTC)
I think the key itself would be unencyclopedic - its inclusion in the article would not really enlighten the reader. The fact that the key has been widely disseminated and references to it are relevant however. Ripe 17:09, 6 May 2007 (UTC)

Digital Audio Tape

Digital Audio Tape was developed "mid-80s", whereas Compact Discs were on the market in 82. I think someone needs to find a source to the assertion that consumer DAT failed b/c of copying potential as opposed to CDs being both market-ready sooner & handier. Ripe 15:44, 6 May 2007 (UTC)

ITunes Info Embedding

I absolutely think the embedding of identifying information in downloaded tracks is relevant to any discussion on DRM, which explains this reversion Diff --RandomHumanoid 08:26, 8 June 2007 (UTC)

Well, you're wrong. This is at best a privacy issue, not a digital rights management issue. Please take a moment to re-read the description of what the term "digital rights management" means, and help us keep a coherent article by keeping anything unrelated to DRM out of the article. Thanks. -/- Warren 17:42, 10 June 2007 (UTC)

These all need to be evaluated for their quality and relevance. Printed and academic literature seems to be underrepresented as well. —Ruud 23:51, 28 July 2007 (UTC)

Further reading

  • Lawrence Lessig's Free Culture, published by Basic Books in 2004, is available for free download in PDF format. The book is a legal and social history of copyright. Lessig is well known, in part, for arguing recent landmark cases on copyright law. A Professor of Law at Stanford University, Lessig writes for an educated lay audience, including for non-lawyers. He is, for the most part, an opponent of DRM technologies.
  • Consumer's Guide to DRM, published in 10 languages (Czech, German, Greek, English, Spanish, French, Hungarian, Italian, Polish, Swedish), produced by the INDICARE research and dialogue project
  • Eberhard Becker, Willms Buhse, Dirk Günnewig, Niels Rump: Digital Rights Management - Technological, Economic, Legal and Political Aspects. An 800 page compendium from 60 different authors on DRM.
  • Fetscherin, M., Implications of Digital Rights Management on the Demand for Digital Content, provides an excellent view on DRM from a consumers perspective. [7]
  • Bound by Law, by James Boyle et al, at Duke University Law School (http://www.law.duke.edu/cspd/comics/zoomcomic.html), a comic book treatment of the US Fair Use doctrine (with some relevance to other jurisdictions, for example in the Commonwealth usually called Fair Dealing), that is a license fee or permission free, under statute and common law precedent, use of copyrighted material.
  • DRM on Open Platforms - A paper by Hagai Bar-El and Yoav Weiss on ways to partially close open platforms to make them suitable for DRM implementations. It has been released under a Creative commons by NC-SA license.
  • The Pig and the Box, a book with colorful illustrations and having a coloring book version, by 'MCM'. It describes DRM in terms suited to kids, written in reaction to a Canadian entertainment industry copyright education initiative, aimed at children.
  • Present State and Emerging Scenarios of Digital Rights Management Systems - A paper by Marc Fetscherin which provides an overview of the various components of DRM, pro and cons and future outlook of how, where, when such systems might be used.
  • DRM is Like Paying for Ice - Richard Menta article on MP3 Newswire discusses how DRM is implemented in ways to control consumers, but is undermining perceived product value in the process.
  • Challenges in Designing Content Protection Solutions - A paper by Hagai Bar-El and Discretix that addresses technical dilemmas and difficulties met when designing DRM products.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Digital_rights_management/Archive_3&oldid=1224782855"