On 9/17/05, Tantek Çelik <<a href="mailto:tantek@cs.stanford.edu">tantek@cs.stanford.edu</a>> wrote:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On 9/17/05 12:54 PM, "Luke Arno" <<a href="mailto:luke.arno@gmail.com">luke.arno@gmail.com</a>> wrote: > I am trying to get my head around microformats still. Hi Luke, welcome to the list! > I asked this already but I think it got lost in the previous thread. > > Does it make sense to do this: > > <atom:link > atom:rel="contact" > atom:href=" <a href="http://examle.org/hCard.html">http://examle.org/hCard.html</a>" > atom:type="text/xhtml"/> I believe you don't actually need the namespace qualifiers on the attributes, since the attributes belong to the element rather than the global atom namespace.  Also, text/xhtml is not a registered mimetype AFAIK. <atom:link rel="contact" href="<a href="http://example.org/hCard.html">http://example.org/hCard.html</a>" type="text/html" /></blockquote><div> That _was_ a poor and hastily composed example. <blush/> </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Now, that being said, I'm not sure what you're trying to express with that link. I.e. what content problem are you trying to solve? Are you trying to state that you consider the person represented by <a href="http://example.org/hCard.html">http://example.org/hCard.html</a> to be a "contact"? If so, then yes, that could make sense.</blockquote><div> Yes. I am toying with the idea of including social network info via XFN into atom feeds. </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> As a side note, has there been considerations of using the IANA registry for > rel values. Not yet, but it's a reasonable proposal to consider. To date, W3C has kept the "canonical" list of rel values.  They're adding a few in XHTML2, e.g. rel="profile", which we're thinking of making explicit even independent of XHTML2 (i.e. before it progresses all the way to REC).</blockquote><div> Cool. That is much nicer than the head@profile thing (and makes sense in more types of documents). </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">E.g. in your above example, in order to explicitly indicate that you were using the XFN 1.1 profile to define the rel="contact" value, you could include the following: <atom:link rel="profile" href="<a href="http://gmpg.org/xfn/11">http://gmpg.org/xfn/11</a>" /></blockquote> <div> Ah, yes. That is it. </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Could prefixing help avoid conflicts going forward (rel=" > xfn.contact "?) If conflicts were a real problem to worry about.  Certainly for experimental values, or odd values for very specialized applications, one might want to consider some form of prefixing to discourage both premature adoption, and adoption outside the particular uses you are thinking of.  But for general purpose 80/20 applications, we have found that such prefixes are unnecessary/undesirable and nothing but syntactic vinegar that are to be avoided.</blockquote><div> I see your point.  I suppose it would run counter to the spirit of microformats. </div> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Like I said, I am just trying to get my head around this. Once again, welcome Luke.  Keep asking good questions. </blockquote><div> Thank you (and Ryan King) for the welcome. This is very exciting stuff. - Luke </div></div>