Quote:
Originally posted by RawAlex@Jul 2 2004, 10:33 AM
KK, I am techy type person, and I don't see DRM being able to do what you are suggesting. DRM controls the usage of a file, it doesn't lend itself to model identification beyond the obvious clip ID matching to a paper or electronic file.
|
All you had to do was ask sweets
The easiest, and most effective way to do it and be able to keep it updated is to initiate an html call from a window popped through the DRM laws the first time a user -- defined by any number of unique identifiers -- views the content. The user then has the ability to click the 2257 link and see the information if they so desire. Rather than embedding the information in the encoding or the DRM, you host the 2257 information on a separate (segregated per the rules actually) server. When the license acquisition request is made, the DRM also knows exactly where that call originates, be it an IP in the case of P2P, or a url in the case of someone displaying the content on their site. These files are logged and should (keep in mind I'm not a lawyer but we've had 3 look at it so far) satisfy the cross indexing requirements. Thus, if an inspector came to your business, you could immediately produce the records they want, and by having the 2257 come in the process of an html call from a separate server, you can update the 2257 records any time you need to and they will be globally changed, you wouldnt have to go back and re-wrap, or God forbid, re-encode, the video in order to be current.
One could figure that if the government were looking at say, 5 sites, of equal size in revenue (or what they assumed to be equal), the ones that are the most comprehensive in their record keeping would be the last ones they would want to take on, especially if some of the targets were obviously using what they consider to be sloppy methods of record keeping