/lists.whatwg.org/pipermail/whatwg-whatwg.org/2005-November/005050.html
https://github.com/whatwg/whatwg.org · HTML · 85 lines · 73 code · 5 blank · 7 comment · 0 complexity · ac5329c3e54fdfb607226453cb5add90 MD5 · raw file
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
- <HTML>
- <HEAD>
- <TITLE> [whatwg] rel/rev for <form> ?
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20rel/rev%20for%20%3Cform%3E%20%3F&In-Reply-To=%3CBAY101-DAV135FFFF5755A4F17B33B8ED8620%40phx.gbl%3E">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="005047.html">
- <LINK REL="Next" HREF="005051.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] rel/rev for <form> ?</H1>
- <!--htdig_noindex-->
- <B>Mike Dierken</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20rel/rev%20for%20%3Cform%3E%20%3F&In-Reply-To=%3CBAY101-DAV135FFFF5755A4F17B33B8ED8620%40phx.gbl%3E"
- TITLE="[whatwg] rel/rev for <form> ?">mdierken at hotmail.com
- </A><BR>
- <I>Sat Nov 5 18:37:17 PST 2005</I>
- <P><UL>
- <LI>Previous message: <A HREF="005047.html">[whatwg] rel/rev for <form> ?
- </A></li>
- <LI>Next message: <A HREF="005051.html">[whatwg] rel/rev for <form> ?
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#5050">[ date ]</a>
- <a href="thread.html#5050">[ thread ]</a>
- <a href="subject.html#5050">[ subject ]</a>
- <a href="author.html#5050">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>
- ><i> > * Do you think being able to provide semantics between 2 resources
- </I>><i> > -- between 2 URI's -- is important?
- </I>><i>
- </I>><i> Yes, but not really for <form>.
- </I>><i>
- </I>><i> Reason: generally speaking, an URI specified in the ACTION
- </I>><i> attribute of the <form> is not a web page that shows general
- </I>><i> information, good for web crawlers nor the like. I wouldn't
- </I>><i> like bots going crazy in my <form>s :).
- </I>
- 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).
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="005047.html">[whatwg] rel/rev for <form> ?
- </A></li>
- <LI>Next message: <A HREF="005051.html">[whatwg] rel/rev for <form> ?
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#5050">[ date ]</a>
- <a href="thread.html#5050">[ thread ]</a>
- <a href="subject.html#5050">[ subject ]</a>
- <a href="author.html#5050">[ author ]</a>
- </LI>
- </UL>
- <hr>
- <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
- mailing list</a><br>
- <!--/htdig_noindex-->
- </body></html>