xfolk-issues

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

Template

Please use this format:

• 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.

Issues

• 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.

• 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-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...

• 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?.