- From: Mike Dierken <mdierken@hotmail.com>
- Date: Sat, 5 Nov 2005 18:37:17 -0800
> > * Do you think being able to provide semantics between 2 resources > > -- between 2 URI's -- is important? > > Yes, but not really for <form>. > > Reason: generally speaking, an URI specified in the ACTION > attribute of the <form> is not a web page that shows general > information, good for web crawlers nor the like. I wouldn't > like bots going crazy in my <form>s :). The 'rel' attribute establishes a relationship between the identified resource and the current document. It looks like the suggested 'rel' attribute identifies the meaning of the identified resource, independent of the current document. A rel value of "this document is a description of the service at 'foo'" would be more appropriate. I do think an attribute that describes the 'type' of service that the action attribute references would be good. Doing a 'HEAD' request on the URI in the action attribute could provide the data that indicates the 'purpose' of that resource. Not that this is the best approach, but using 'rel' might be overkill. What you want is a resource description framework and some documented means of getting metadata about a resource (service).
Received on Saturday, 5 November 2005 18:37:17 UTC