Talk:Digital rights management/Archive 1

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

Topic needs to balance technical and political aspects

The topic of DRM is very political, and this should be reflected in the article, but at the centre of the topic there is a core technical subject. There is a problem with the definition at the moment, and it is that it only talks about the restrictive aspects of DRM. In theory and in the specialised literature, DRM refers to ALL types of management of rights online, even if these are not restricitve (such as placing a tracker to count acces, or XML with legal elements on it, or even Creative Commons banners). Restrictive DRMs have a name: Technical Protection Measures. Anduin13 08:00, 17 Nov 2005 (GMT)

Aw, you just made up the term "Technical Protection Measures". Nobody really uses it. (27,000 hits in Google, most of which are from DRM industry papers, the WIPO, etc.) And very few people refer to written copyright notices as "digital rights management"... in fact, you're the first I'm aware of.
This is one example of many where common usage trumps technical picayunity. DRM is used by the vast majority of people to refer to software or hardware mechanisms for preventing "unauthorized use" of digital works. Someone searching for a definition of DRM in Wikipedia would be misled by your overly-broad definition. 12.103.251.203 19:14, 6 December 2005 (UTC)
The TPM term is widely used by copyright lawyers, although it is somewhat WIPO specific. It would be good to explain that DRM is often popularly understood to mean TPM (or vice versa); perhaps there can be a separate article on Rights expression language. Schoen 22:09, 6 December 2005 (UTC)

merge w/ copy protection?

This article needs to be merged with copy protection. -- Pde 06:30, 27 Oct 2003 (UTC)

Disagree. There are copy protection methods that are not digital, hence cannot be classified as DRM. GRAHAMUK 06:50, 27 Oct 2003 (UTC)

I also disagree. There is enough information specific to DRM to warrant a separate article.

Ditto. I don't reckon it's the same thing. Copy protection prevents copying, DRM doesn't — it controls (usually by preventing) use; as POV as that may sound, it is actually the truth of the matter, no? — SirPavlova

POV problems?, cover only technical aspects?

This page seems to have substantial POV problems, as well as many markup and presentation errors. It looks as if it was reformatted from an email message. I would suggest, at a minimum, that the main article ought to concentrate on just the technical aspects of DRM, and the politics in various countries should be moved to separate articles. 18.24.0.120 02:05, 26 Jan 2004 (UTC)

I would disagree that 'technical aspects' of DRM (in its various forms which differ substantially technically) are currently separable from policy aspects, including political reactions. The engineering problem for DRM generally is a considerable one given the assorted expectations (legal, commercial, traditional, ...) of any DRM system. Furthermore, those establishing the 'protection expectations' for DRM (in re music, or movies, or ...) have unclear and to some extent mutually contradictory desires about the desired performance. For instance, prevent all unauthorized copying while interfering not at all with a customer's experience.

Until these problems are addressed, there is, can be, and will not be any 'technical solution'.

On the other hand, it is certainly possible to adopt DRM solutions which merely provide what the engineering supplies. Unfortunately, many of the provisions the engineering supplies are problematic under one or another existing law or regulation -- as for instance in the US, the 'fair use' provisions of copyright law. Or such provisions are in conflict with commercial desirata for a DRM policy, most notably convenience for customer and his use of the property.

It would be, perhaps, ideal if such a separation were possible, but the current state of things (engineering, law, copyright owners' desires, ...) do not permit. It's a structural problem(s) and this article ought not to allow readers to conclude (by absence of information on the point) that there are not such problems.

ww

Agree there are significant POV issues. Tried to edit the use of quote marks on things and the use of "so-called" before terms but the edits were reverted. :P. Ripe 02:25, 6 February 2006 (UTC)

needed opponent's view; dead link

There was no opponent's view of DRM which I just added, and will expand upon. Some argue that DRM is nothing less then the beginning of the age of internet censorship, the digital imprimatur, so I think it important to share their viewpoints. Especially important since one opponent of DRM is Richard M. Stallman of Linux / GNU / GPL who calls it 'trusted computing', and wrote a story where DRM is the mainstay and people revolt for the 'Right to Read'. ShaunMacPherson

The link to Edward Felton's webpage is broken.

--Furrykef 00:39, 23 Feb 2004 (UTC)

DRM is wrong term for this

A more neutral term would be Digital Copy Protection (DCP). It's not a term that's in vogue, but it's clearly more NPOV. Connelly 03:44, 31 Jul 2004 (UTC)

IMHO the very term "digital rights management" expresses a non-neutral point of view, since what is being managed has no relationship to anybody's legal rights at all, neither those of the vendor who makes use of DRM nor the customer who buys DRM-protected material. The restrictions placed on the use of the material are whatever restrictions the seller wishes them to be, independent of the legal situation. One example of this was Adobe's release of an Adobe eBook Reader edition of "Alice's Adventures in Wonderland"--which was based on Project Gutenberg's eText--which did not permit use of the "read aloud" text-to-speech feature of the software. The article addresses this by presenting the alternate reading of DRM as "digital restrictions management," but I feel there is still an issue. Dpbsmith 00:57, 23 Feb 2004 (UTC)

Agree 100%. —Psychonaut 09:58, 23 Feb 2004 (UTC)
Disagree strongly. Copyright law grants the (restricted under some -- more or less vanishing as changes are progressively made as on behalf of Disney in the US) the copyright holder the privilege of controlling the use of the copyrighted material by anyone else. If the copyright holder wants to prevent it being read aloud (as in the example cited) that's their privilege which will be enforceable at law; the various uses of copyrighted material are separable in law. Whether this separability or particular limitations on use grants make any sense in any particular context is another thing altogether. Whether the example text was copyrightable (though based on a public domain original) is another, and distinct, question.
Well, for the record... Alice's Adventures in Wonderland is well and truly in the public domain. Adobe never has claimed that it wasn't. Adobe never said they had created a derivative work or anything of the sort. In fact, they eventually acknowledged that their text was derived from Project Gutenberg's eText (which all have GPL-like language in them requiring redistributors not to place restrictions on it). Sure, a copyright holder has certain rights to control the use of their work. The point is that in the real world, the use of so-called DRM has no connection whatsoever to those rights. Adobe can and did use their technical mechanism to place restrictions on a work to which they held no rights whatsoever. They claimed it was a mistake, and (guessing here) it very likely was, in that I'll bet their system was set up to make restriction the default and nobody bothered to override the default for a case in which it was incorrect. DRM places all control in the hands of the vendor. Errors in the application tend to be one-sided, consisting of the vendor exercising "rights" that it does not, in fact, possess. The Adobe incident is an absolutely crystal-clear example of this.

The term DRM is indeed awkward, and in some usages is probably non-POV, but the Wikipedia is not the place to reform offending usage. The term is unfortunate, but it is the term in wide use -- however unfortunatly misused, sometimes in an attempt to pervert the discourse for private benefit -- and we're stuck with it in my view.

There will always be an issue in this instance (both terminological and otherwise) as long as there is no generally accepted solution to the conflict which now exists and which has every prospect of getting much more intense in the next few years. The release of 'Longhorn' which will apparently incoporate some (all) aspects of Palladium and the TCPA (whatever they're being officially called of late) will put the fox amongst the chickens in a large way. Next year if I understand the release schedule correctly. We here would do well to have the best possible account of the issues (under whatever term) available when the terminal material hits the rotating impeller.
On the Wikipedia, I think the solution is to set up redirects from this or that alternative term.
ww


Sorry to complicate this further, but there is another definition of DRM floating around that focuses on it as a shared ruleset between vendor and consumer that happens to be implemented/enforced using digital technologies. In this view, it's a matter of contract: the vendor offers content under a specific set of conditions and a consumer decides whether or not to purchase accordingly. This is of course problematic itself for a variety of reasons including 1) the consumer often won't know what all the conditions are and had no voice in designing them; 2) is it a contract of adhesion if the content isn't fungible?; 3) should we let contracts trump fair use (US version; called other things elsewhere)?; 4) DRM can enable a vendor to exert control over content that it doesn't actually own the rights to in the name of controlling its physical media (assuming analog distribution).

To give the pro-DRM crowd its due, DRM is intended to re-level the playing field. The physical limitations of analog media meant that the content vendor was limited in the terms he could set on use of his content but it also pretty effectively limited the consumer's ability to undermine the vendor's return on his investment through mass piracy/redistribution/copying (however you want to look at it). Digital technologies enable property rights relationships that were previously impossible and, if pricing follows, could make more content available to more people via price differentiation. For example, your medieval Gutenberg Bible had to be sold with the understanding that you could use it forever and it could be freely copied, albeit slowly and at high cost. Now a digital book can (well, effectively maybe someday) be sold for short-term use only and without the ability to be copied. That digital version ought to be substantially cheaper than the digital analog of the Gutenberg Bible. I don't personally believe the pricing differential will follow appropriately, but that's at least one argument.

mysterious cruft! what to do?

In the article is a < sentence within > followed by EDIREC. Can anyone figure out what was intended here? I'll try to remember to come back and clean it out if no one can. ww 16:15, 13 Apr 2004 (UTC)

Oops, that would be my "EDIREC"...I've been linking up a couple of "REDIRECTs" today, and presumably some tab grabbed the keyboard focus at the wrong time, and I didn't notice that "addition" ;-) — Matt 16:37, 13 Apr 2004 (UTC)
OK. I don't have to remember now. Thanks, lowers the overhead load. ww 13:49, 14 Apr 2004 (UTC)

to what exactly?

Matt, I had in mind here the recent spate of organizational decisions to use Linux as the standard OS (in assorted countries, Munich, ...). Didn't want to say so for POV reasons. Got a way to say it that wouldn't be obscure (I agree with you there) or POV (by mentioning/'endorsing' a competitor)? ww 17:22, 15 Apr 2004 (UTC)

I think its quite legit to mention that organisations may be favouring, say, Linux over MS because of DRM, if that's a verifiable matter of fact. (Is DRM the only factor?) — Matt 17:38, 15 Apr 2004 (UTC)
Matt, Without access to the inner thoughts of those concerned... That's too high a bar as a test to avoid POV.
My understanding, tagged as 'reliable' in my dustbin of a mind, is that such decisions are largely the result of several factors:
  • cost (initial and administrative) vs open source
  • reliability (even NT/2000/WP has bugs and bugs and goofs and goofs and ...); Linux / BSD not perfect, but orders of magnitude better
  • security (see above) and note in addition MS not so stellar record of getting crypto stuff right. Gutmann has documented a large goof in the core piece MS' CryptoAPI.
  • in the case of China the NSAkey flap over a string found in MS Windows (CryptoAPI, I believe it was) seems to have been a significant factor, as likewise the current flap over Chinese wireless standards being imposed on the chip/software industry
Which factor predominates in any particular procurement decision may not be identifiable, even if the decision maker is available for rubber hose interrogation by you or me or Imran. Linus and Arvindn seem to be more gentle souls, maybe they'd use soggy noodles.
I'm not sure how we can do much better in avoiding even the hint of POV. Even when it's the truth. What would you recommend on a technical basis if Munich came to you? The execs might decide otherwise for assorted reasons (fanatsies about 'better' support if they pay for $oftware, fear of swimming against the tide (the Canute courtier syndrome), terminal dumbth about the nature of open source (ie, =illegal hacking), ...), but what you recommend technically?
ww 18:15, 16 Apr 2004 (UTC)
(What would I recommend? Well, Linux, but only because I don't support non-free software out of principle; not sure what would be best technically). As regards mentioning what motivates Munich etc., if access to their "inner thoughts" is required, I'm afraid it's not suitable for Wikipedia (see Wikipedia:Verifiability). For this, we really need some quotable source where group X states that they choose Linux over MS (in part) because of DRM. — Matt 18:51, 16 Apr 2004 (UTC)
The problem is that most of the sources out there that mention those concerns (DRM in particular, with Windows media player) also tend to have an RMS-like views on Microsoft - and the two tend to be tied together, which causes a lot of folks to associate concerns about DRM with "tin foil hat-ism" or RMS and similiarily radical folks. Pakaran. 04:42, 17 Apr 2004 (UTC)
Ross Anderson is a strong opponent of trusted computing, and is fairly respectable in the "tin foil hat" stakes. — Matt 18:00, 17 Apr 2004 (UTC)
Is that enough ':'. Darned things.
Two too many, but who's counting? — Matt 18:52, 17 Apr 2004 (UTC)
I will defend RJA's rep on his behalf. He is not fairly respectable at all. There is no one more so. Including Schneier, who has been involved in some odd patent stuff in connection with a patent holding firm. I don't really understand it or quite how BS got flypapered (it's legal and contingent and all that; I don't have time to unravel it all, even if I were certain I could if I had time....). Fairly respectable doesn't in my view, cut the rhetorical (or factual) mustard in re RJA.
Anyone who thinks RJA wears even a metaphorical tin hat can just stuff his own tin hat where... Cautious phrasing is admirable, but can be carried too far into misleading trepidation. Or something. ww 18:29, 17 Apr 2004 (UTC)
I'm a little confused by this comment, but just to clarify, I meant that I consider Professor Anderson less of a crank than, say, Richard Stallman. — Matt 18:52, 17 Apr 2004 (UTC)
Ahemmmm. Undone by British understatement yet again. Never mind. ww 19:54, 17 Apr 2004 (UTC)

on the reversion this date

The anonymous edit here reverted removed w/o explanation some associated with DRM examples. Perhaps they shouldn't be here, but w/o any explanation of why, ... ww 16:11, 22 Jun 2004 (UTC)

DivX is referred to here as "a video compression protocol, akin to MPEG-4". In fact, DivX is an implementation of MPEG-4. I suggest "an implementation of the MPEG-4 video compression protocol." -Peter

Revision of definition

The paragraph previously read:

Digital Rights Management or Digital Restrictions Management (DRM) is an umbrella term for any of several arrangements by which the usage of (primarily) copyrighted digital work can be restricted by the owner of the rights to the work. The actual arrangements are called technical protection measures (although the distinction between the two terms is not particularly clear).

This is simply not correct and expresses the point of view of the vendors and users of DRM systems. There is absolutely nothing about DRM that connects its use to the "owner" of the rights to the work, or ensures that the restrictions enforced by the system are in accord with the owner's rights. The previous definition is analogous to defining "handcuffs" as "a system used by police to restrain criminals."

I basically agree, but feel we're caught in the flypaper of established usage, however not quite right. See earlier discussion above which is somewhat related to this point. There is certainly a lot of special pleading in this arena and the use/misuse of terms is an example. Indeed, much of the "it's our property and we should be aided by statute/police/prosecutors to protect our control of (and profiting from) it" arguement is skew to the history in any case. See Free Culture by Lessig (an expert legal scholar of this stuff) for some of the history. The 'Conger', ended in Queen Anne's time by Parliament, is merely an earlier example of what is going on now. ww 20:01, 5 Oct 2004 (UTC)
Off topic, but is there any chance you could do up an article on the Conger? Provided you know enough, anyway. It sounds intriguing, I must say. — Me. (SirPavlova, but I forgot the password.)
One thing that I feel is missing from the defenition is the tech being internet-based. You wouldn't call a CD key DRM, yet I can't think of a reason why it doesn't fall under the current defenition. It works at the other end too of course, so we have to be careful: logging in to a website, MMORPG client or similar to access your paid account isn't DRM either (unless anyone disagrees).
Perhaps something along the lines of "the practive of restricting use of material, usually copyrighted and purchased, on a client computer based on authorisation from a remote one, when that authorisation would not otherwise be needed"? That's not a very good defenition, I'm hoping someone can improve on it. --Tom Edwards 14:36, 8 August 2005 (UTC)

Y'all can't seriously think this even remotely approaches a neutral take on the subject, can you?

Well, why don't you try and improve it then?—Ëzhiki (erinaceus europeaus) 17:22, Nov 16, 2004 (UTC)
Or, at least, please point out particularly problematic parts so that we can discuss what needs fixing. Thanks! — Matt 17:27, 16 Nov 2004 (UTC)

I believe it is important to be factually correct, which this definition currently is not. The copyright holder is not one of the two possible entities that can directly control communications devices as only the device vendor or the owner can be in control.

Whether or not the vendor of the device, under a license agreement from the DRM vendor, should be in control of the device rather than its owner is a political debate. Whether these DRM vendors should be required by law to obey the license agreements of copyright holders, *only* those agreements, and *only* as far as those agreements are legal, is also an appropriate debate.

Clarifying who the two options are, and that the copyright holder is not one of those options, is a fact.

I have commented on this definition on my own site: http://www.digital-copyright.ca/node/view/609

Dec 7, 2004

The current definition seem to be too much biased (27-mai-2006) to political terms (usurpation, capitalists, etc.), although the article is overall good.
Anon poster (above), There is a long history of objection to this article as biased in various respects. This talk page records some of that debate. Please note that the WP procedure -- not always followed by all, regrettably -- is to propose changes to repair alleged defects. I have been working in and around this article for a very long time and would welcome actual suggestions as to how to remove the bias here alleged. Thus far, there have been rather more complaints than proposals. It is unlikely that any side will ever be fully satisfied in and around DRM, but if you can improve the article, please help. Wahtever you can do to imporve this article will be welcome. ww 08:13, 28 May 2006 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Digital_rights_management/Archive_1&oldid=376283175"