Difference between revisions of "directory-inclusion-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
=Directory Inclusion Brainstorming=
 
=Directory Inclusion Brainstorming=
This page is dedicated to brainstorming ways to do distributed directory inclusion, based on the research done in [[directory-inclusion-examles]] and  [[directory-inclusion-formats]].
+
This page is dedicated to brainstorming ways to do distributed directory inclusion, based on the research done in [[directory-inclusion-examples]] and  [[directory-inclusion-formats]].
  
 
== Editor ==
 
== Editor ==

Revision as of 14:59, 30 August 2005

Directory Inclusion Brainstorming

This page is dedicated to brainstorming ways to do distributed directory inclusion, based on the research done in directory-inclusion-examples and directory-inclusion-formats.

Editor

Authors

Questions

  • Is rel="tag" sufficient?
    • Probably not. There's lots of cases where there are preexisting directory links, which are not taggable. It would be nice to have the ability to make those explicit. - Ryan

Straw proposal

  • rel="directory" - thoughts by Tantek
    • indicates that the referenced resource is a directory which does or should contain the current page. Note that this has some resemblance to (but with important differences from) several existing HTML4 rel values: Contents, ToC, Index, Appendix. A directory implies something more though, perhaps aspects like pointing to a bunch of things at different locations/sites, perhaps one or more canonical orderings (whether alphabetical or by some other metric). I know this is a bit rough, but I ran the idea past a few key folks at FOO Camp (David Weinberger, Josh Kinberg, Blaine & Rabble of ODEO), and after a bit of discussion it seemed to make sense to them too.