xfn-issues

These are externally raised issues about XFN 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.

IMPORTANT: Please read the xfn-faq before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered. 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. — Brian

Please add new issues to the top of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

Issues

• accepted issue! 2007-06-07 raised by Chris Messina.
  1. A question came up about fragment identifiers on the OpenID list. Does the presence of a fragment identifier have any impact on an identity URL in XFN.
     • XFN doesn't define how to process a part of a page, only an entire page.

• open issue! 2007-06-08 raised by Brian Suda.
  1. Does the presence of a query string have any impact on an identity URL in XFN.
     • Well, if you want to follow web architecture, all urls are opaque, so it doesn't matter whether the URL has a query string or not.

Template

Please use this format (copy and paste this to the end of the list to add your issues):

• open issue! YYYY-MM-DD raised by YOURNAME.
  1. Issue 1: Here is the first issue I have.
  2. Issue 2: Here is the second issue I have.