throbber
W3C Staff Note on HTTP Distribution and Replication Protocol Submission
`
`W3C Staff Note on HTTP Distribution and Replication Protocol
`Submission
`
`The Consortium is pleased to have received this specification as a submission, and acknowledges the
`interest in such a mechanism indicated by several Member companies.
`
`The proposal will be discussed at the W3C workshop on "push" technology in September.
`
`That workshop will give participants a chance to comment on the path the consortium should take. At this
`time we are not promising any allocation of further W3C resources to this proposal after the Push
`Workshop.
`
`This technology impacts URI specifications, HTTP, and includes anew XML mime type. Much of the
`functionality should be able to be provided by the Resource Description Framework currently being
`developed in the metadata activity. There are other components of the DRP proposal that have
`requirements in common with other W3C and IETF activities(notably DSig Manifests and WEBDAV
`versioning) and should this proposal be actively considered, W3C will work to insure the harmonization of
`the related activities.
`Note: Patent rights
`
`On 1997 August 27, I received a message from Albion Fitzgerald of Novadigm Inc, asserting that Novadigm
`may have patent rights in this area, and revealing in their enclosed press release made the same day, that
`Novadigm sued Marimba in March 1997. I bring this to your attention.
`
`Tim Berners-Lee, W3C Director
`$Date: 1997/08/28 16:22:40 $
`
`http://www.w3.org/Submission/1997/10/Comment.html[1/8/2013 12:35:01 PM]
`
`Page 1 of 1
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket