/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

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  2. <HTML>
  3. <HEAD>
  4. <TITLE> [whatwg] rel/rev for &lt;form&gt; ?
  5. </TITLE>
  6. <LINK REL="Index" HREF="index.html" >
  7. <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">
  8. <META NAME="robots" CONTENT="index,nofollow">
  9. <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10. <LINK REL="Previous" HREF="005047.html">
  11. <LINK REL="Next" HREF="005051.html">
  12. </HEAD>
  13. <BODY BGCOLOR="#ffffff">
  14. <H1>[whatwg] rel/rev for &lt;form&gt; ?</H1>
  15. <!--htdig_noindex-->
  16. <B>Mike Dierken</B>
  17. <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"
  18. TITLE="[whatwg] rel/rev for &lt;form&gt; ?">mdierken at hotmail.com
  19. </A><BR>
  20. <I>Sat Nov 5 18:37:17 PST 2005</I>
  21. <P><UL>
  22. <LI>Previous message: <A HREF="005047.html">[whatwg] rel/rev for &lt;form&gt; ?
  23. </A></li>
  24. <LI>Next message: <A HREF="005051.html">[whatwg] rel/rev for &lt;form&gt; ?
  25. </A></li>
  26. <LI> <B>Messages sorted by:</B>
  27. <a href="date.html#5050">[ date ]</a>
  28. <a href="thread.html#5050">[ thread ]</a>
  29. <a href="subject.html#5050">[ subject ]</a>
  30. <a href="author.html#5050">[ author ]</a>
  31. </LI>
  32. </UL>
  33. <HR>
  34. <!--/htdig_noindex-->
  35. <!--beginarticle-->
  36. <PRE>
  37. &gt;<i> &gt; * Do you think being able to provide semantics between 2 resources
  38. </I>&gt;<i> &gt; -- between 2 URI's -- is important?
  39. </I>&gt;<i>
  40. </I>&gt;<i> Yes, but not really for &lt;form&gt;.
  41. </I>&gt;<i>
  42. </I>&gt;<i> Reason: generally speaking, an URI specified in the ACTION
  43. </I>&gt;<i> attribute of the &lt;form&gt; is not a web page that shows general
  44. </I>&gt;<i> information, good for web crawlers nor the like. I wouldn't
  45. </I>&gt;<i> like bots going crazy in my &lt;form&gt;s :).
  46. </I>
  47. The 'rel' attribute establishes a relationship between the identified
  48. resource and the current document. It looks like the suggested 'rel'
  49. attribute identifies the meaning of the identified resource, independent of
  50. the current document. A rel value of &quot;this document is a description of the
  51. service at 'foo'&quot; would be more appropriate. I do think an attribute that
  52. describes the 'type' of service that the action attribute references would
  53. be good.
  54. Doing a 'HEAD' request on the URI in the action attribute could provide the
  55. data that indicates the 'purpose' of that resource. Not that this is the
  56. best approach, but using 'rel' might be overkill. What you want is a
  57. resource description framework and some documented means of getting metadata
  58. about a resource (service).
  59. </PRE>
  60. <!--endarticle-->
  61. <!--htdig_noindex-->
  62. <HR>
  63. <P><UL>
  64. <!--threads-->
  65. <LI>Previous message: <A HREF="005047.html">[whatwg] rel/rev for &lt;form&gt; ?
  66. </A></li>
  67. <LI>Next message: <A HREF="005051.html">[whatwg] rel/rev for &lt;form&gt; ?
  68. </A></li>
  69. <LI> <B>Messages sorted by:</B>
  70. <a href="date.html#5050">[ date ]</a>
  71. <a href="thread.html#5050">[ thread ]</a>
  72. <a href="subject.html#5050">[ subject ]</a>
  73. <a href="author.html#5050">[ author ]</a>
  74. </LI>
  75. </UL>
  76. <hr>
  77. <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
  78. mailing list</a><br>
  79. <!--/htdig_noindex-->
  80. </body></html>