From Microformats Wiki
Revision as of 20:08, 12 August 2007 by TomMorris (talk | contribs)
Jump to navigation Jump to search

xFolk issues

These are externally raised issues about xFolk with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Bud


Please use this format:

  • {{OpenIssue}} YYYY-MM-DD raised by AUTHORNAME
    1. Issue 1: Here is the first issue I have.
    2. Issue 2: Here is the second issue I have.


  • open issue! 2007-01-01 raised by Andy Mabbett
    1. Applying a tag in an xFolk entry also applies it to the linking page. However, certain tags (e.g. "NSFW") may apply to the page linked to, but not to the linking page.

2007-01-03 addressed by Bud Gibson. Well, we had a lot of list discussion on this while creating xFolk. Actually, that was pre-list. The rationale is that the tags apply to the items in the container not the page simply by convention in xFolk. It's a specialization of reltag. The real question I think is what are the scoping rules for reltag. The assumption here is that the reltag tags only apply to the link within xfolkentry.

  • open issue! *Why is this called "xFolk", and not, say, xBookmark(s) or hBookmark(s)? Andy Mabbett 09:16, 19 Nov 2006 (PST)

2007-01-03 addressed by Bud Gibson. Mainly because the purpose of the microformat was originally to allow harvesting into aggregation services for creating "folksonomies".

  • open issue! 2006-06-12 raised by singpolyma
    1. using title attribute for the tagged link <a> element, if it exists, as the entry title -- I use the title attribute for a summary description, since this is more XOXO 1.0: Extensible Open XHTML Outlines-compatible. While I lose the ability to have xfolk harvest my descriptions that way, I'm not really worried about that. What I'm more worried about is xfolk using my descriptions as the title...

2007-01-03 addressed by Bud Gibson. I'm in a quandary as to how to address this one. It seems like a basic incompatibility.

  • open issue! 2006-04-20 raised by Ryan Cannon
    1. Issue 1: As xFolk is intended as a list, it seems tedious to have to place class="xfolkentry" on every element. Are there implementation problems with creating a container class with that implies class="xfolkentry" on every child node?.
  • open issue! 2007-04-27 raised by Kevin Marks
    1. I wondered why xfolk uses class="taggedlink" rather than rel="taggedlink" as a rel value seems more semantic for labelling the link.

Related pages