W3C home > Mailing lists > Public > www-rdf-interest@w3.org > December 1999

I-D ACTION:draft-ietf-webdav-binding-protocol-02.txt (fwd)

From: Dan Brickley <Daniel.Brickley@bristol.ac.uk>
Date: Thu, 23 Dec 1999 13:57:51 +0000 (GMT)
To: www-rdf-interest@w3.org
Message-ID: <Pine.GHP.4.21.9912231353410.21487-100000@mail.ilrt.bris.ac.uk>
RDF IG,

On the RDF/WebDAV front, this new draft is interesting as it relates to 
some of the issues we've discussed w.r.t. 'anonymous' nodes and the
relationship between resource identifiers (URIs) and the resources
themselves.  I'd really like to see this nailed down explicitly for
RDF: is RDF happy with the notion that one single resource can have
multiple URI names bound to it? 

--dan

---------- Forwarded message ----------
Date: Thu, 23 Dec 1999 06:36:56 -0500
From: Internet-Drafts@ietf.org
To: IETF-Announce:  ;
Cc: w3c-dist-auth@w3.org
Subject: I-D ACTION:draft-ietf-webdav-binding-protocol-02.txt
Resent-Date: Thu, 23 Dec 1999 06:37:06 -0500 (EST)
Resent-From: w3c-dist-auth@w3.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the WWW Distributed Authoring and Versioning Working Group of the IETF.

	Title		: WebDAV Bindings
	Author(s)	: J. Slein, E. Whitehead,  J. Davis,
                          G. Clemm, C. Fay,  J. Crawford
	Filename	: draft-ietf-webdav-binding-protocol-02.txt
	Pages		: 22
	Date		: 22-Dec-99
	
This is one of a pair of specifications that extend the WebDAV 
Distributed Authoring Protocol to enable clients to create new access 
paths to existing resources.  The two protocol extensions have very 
different characteristics that make them useful for different sorts of 
applications.
 
The present specification defines bindings, and the BIND method for 
creating them.  Creating a new binding to a resource indirectly creates 
one or more new URIs mapped to that resource, which can then be used to 
access it.  Servers are required to insure the integrity of any bindings 
that they allow to be created.

The related specification, RFC xxxx, defines redirect reference 
resources.  A redirect reference resource is a resource whose default 
response is an HTTP/1.1 302 (Found) status code, redirecting the client 
to a different resource, the target resource.  A redirect reference 
makes it possible to access the target resource indirectly, through any 
URI mapped to the redirect reference resource.  There are no integrity 
guarantees associated with redirect reference resources.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-webdav-binding-protocol-02.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-webdav-binding-protocol-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-webdav-binding-protocol-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Received on Thursday, 23 December 1999 08:58:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:42 GMT