[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: OPES and XSLT
- From: "Bullard, Claude L (Len)" <firstname.lastname@example.org>
- To: Xml-Dev <email@example.com>
- Date: Tue, 14 Aug 2001 08:49:07 -0500
Just for background:
"The Open Pluggable Edge Services architecture (OPES) defines how
participating transit intermediaries can be extended to incorporate services
executed on application data. The services are written to an open standard
for use with the intermediaries." http://www.ietf-opes.org/
"The protocols to be defined provide a framework for integrating a wide
range of services into application-level intermediaries. The advantage of
standardizing such protocols is that services can be re-used across vendor
products without modifying the intermediaries or services.
Intermediary services provided in this way are not transparent: They must be
authorized by the application endpoint (either the content requestor or the
content provider) that requests the intermediary service.
A key task for the working group is to specify an appropriate authorization
Intermediaries may employ services executed either locally or on a remote
("callout") server. One task for this working group is the development of
callout protocols that enable the receiving callout service to either
receive encapsulated HTTP or RTP/RTSP messages or, through some other
mechanism, for the callout service to receive the application data necessary
to perform its services"
And I was so hoping it was just another Mayberry thing...
>1. who owns the copyright on transformed data? At what threshold does
>butchering stops and originality starts?
No one knows. The legal precedents for this are very murky. Thinking about
problems made researchers realize that 404 is not a sufficient answer to
hypertext linking. But hey, this is the web; what care we...
Contract law is the emerging governing force. My guess is that as has been
said in the past, one has to assert all claims prior to publication. This
means stating explicitly what other systems can do with your copyrighted
material. The real problem is enforcement which must start at the
the source to ensure any subsequent party is subject to the contract.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Don Park [mailto:firstname.lastname@example.org]
Recent firestorm over OPES got me wondering:
1. who owns the copyright on transformed data? At what threshold does
butchering stops and originality starts?
2. is the legal protection at the consuming end or at producing end?
3. what about transforming or modifying common parts of copyrighted material
like HTML during transit ? Is it illegal to inject popups at routers?
Interesting questions that affect all of us, I am afraid. BTW, if you are
going to join this thread, bring your flame-protection suit.