Quote:
Originally posted by Mutt
ok now i understand - it's a centralized3rd party service to take the workload off content providersin getting the required documentation to customers. hmmm....... will webmasters have to show you proof they actually have a license for the content they want the documentation for?
|
That's a great question...
It is one of the logistical issues that has come up in introducing the new functionality of delivering model ID (encrypted) to webmasters.
There is the potential that a webmaster could have stolen images and then with the 2257lookup service, be able to atleast save themselves from 2257 inquiry....
Being able to validate with the content producers on domains that have licensing is a big logistical challenge.
That's the best answer i have for now, I will be doing some more research into that.
What;s your take? What if you were part of 2257lookup, would it be an issue to you if a webmaster received the DRM files if they had stolen your content?
2257lookup was not designed to be "centralized3rd party service to take the workload off content providersin getting the required documentation to customers"... it's original intent is the creation of a cross-indexed report.
The recent 2257 changes made it clear to me that this posed a new problem of getting model info out to webmasters, so I have undertaken the challenge.
Only webmasters who are subscribers to 2257lookup would get the model info from 2257lookup.
For those thinking ahead... a webmaster could come to a content producer to ask for the info, and the content producer (who could be overwhelmed with customer service to answer everyone), could direct people to 2257lookup.. which would require them to subscribe to the service.
-brandon