xfn-issues

XFN Issues

These are 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.

Closed Issues

Resolved issues that have no further actions to take. These will likely be moved to a separate page like xfn-issues-closed.

• ...

Resolved Issues

Issues that are resolved but may have outstanding to-do items. As issues are resolved, they will be moved from the top of the Issues list to the bottom of this section.

• 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.
     • RESOLVED FAQ. XFN doesn't define how to process a part of a page, only an entire page.
• accepted 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.
     • RESOLVED FAQ. 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, so no, the presence of a query string has no impact on an identity URL in XFN.

Issues

2007

• accepted issue! 2007-10-24 raised by Mark Ng

• 1. How to express automatically generated user relationships in XFN (f.e those gleaned from the Facebook API) ?
     • ACCEPTED. To-do - examine the Facebook API to see if it returns any information about the nature of the relationship and then choose respective XFN values accordingly.

2008

• open issue! 2008-01-16 raised by Andy Mabbett

• 1. XFN values lack gender-specificity (e.g. "spouse" rather than "husband" or "wife"; "parent" rather than "father" or "mother"). This may limit their usefulness in, for example, genealogy (unless an alternative method of expressing gender is found).

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>