tag:blogger.com,1999:blog-13185724.post113109394527155074..comments2023-08-12T10:41:27.950+03:00Comments on Hello World: More on a tagging standardYanivGhttp://www.blogger.com/profile/14262812323511365206noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13185724.post-1131389429228469272005-11-07T20:50:00.000+02:002005-11-07T20:50:00.000+02:00Kevin, I'd love to update the issues page, but for...Kevin, I'd love to update the issues page, but for some reason the create new user page on the wiki returns an error message.YanivGhttps://www.blogger.com/profile/14262812323511365206noreply@blogger.comtag:blogger.com,1999:blog-13185724.post-1131112042766362442005-11-04T15:47:00.000+02:002005-11-04T15:47:00.000+02:00Based on the current relTag format, it should be e...Based on the current relTag format, it should be easy for tool developer to provide some UI to edit a tagged URI since (as Kevin noted), relTag's data (URI) and representation (node text) are attached and available to the tool. In, Zoundry, when you edit an existing link (with relTag), the tag words and tagspace are displayed in two different fields (performing necessary UTF-8 uri encode/decode).<BR/><BR/>We (Zoundry) are also experimenting with microformats - specifically the hReview format for product recomendations. Currently, if you use Zoundry's toolbar plugin and perform a "BlogThis" on a supported merchant product page, the content is formatted as hReview.Pidgehttps://www.blogger.com/profile/00720849954544379839noreply@blogger.comtag:blogger.com,1999:blog-13185724.post-1131104226530964092005-11-04T13:37:00.000+02:002005-11-04T13:37:00.000+02:00Lots of points there - consider adding the substan...Lots of points there - consider adding the substantive ones to the <A HREF="http://microformats.org/wiki/rel-tag-issues" REL="nofollow">issues page</A><BR/>* Mixing data and representation is by design. If the tags are embedded in the content they don't get detached.<BR/>* Redundancy is not a problem in practice (I have 18 million examples). The URL provides a defined encoding as it is in escaped utf8, which avoids encoding issues in the document<BR/>* Usability: straw man argument here. Bloggers know how to make links. Adding rel="tag" is very easy to remember. In any case, if a tool is generating it this is moot. XML is no more robust<BR/>* Tag Spaces: these are there for disambiguation, and to provide alternatives. You should pick an appropriate one for each tag, bearing in mind that it should make sense to your readers if clicked on. See your own complaint of redundancy supra<BR/>* Scope: this is deliberately left unspecified in the rel="tag" definition. Other microformats that use rel="tag" such as <A HREF="http://microformats.org/wiki/hreview" REL="nofollow">hReview</A> and the <A HREF="http://microformats.org/wiki/rel-directory" REL="nofollow">rel="tag directory"</A> compound can specify the scope appropriately.Kevin Markshttps://www.blogger.com/profile/18338939297948690534noreply@blogger.com