ChristopheDucamp: [fr:sync'd with english version]

2008-02-03T09:52:45Z

[fr:sync'd with english version]

New page

<h1>XFN Problématiques</h1>
{{TOC-right}}

Ce sont les problématiques concernant XFN avec différents degrés de mérite. Par conséquent quelques problématiques sont REJETEES pour un bon nombre de raisons évidentes (mais encore documentées ici dans le cas où elles reviendraient) et d'autres qui contiennent des discussions plus longues. Quelques problématiques peuvent être ACCEPTEES et peut-être amener des changements ou des explications améliorées dans la spec.

IMPORTANT : Lisez svp les [[xfn-faq-fr|xfn-faq]] avant de donner toute réaction ou de soulever une problématique car votre réaction/problématique peut avoir déjà été résolue ou été répondue.
Les problématiques proposées peuvent (et seront probalement) être éditées pour une meilleure concision, clarté, rationalité et sous un point de vue aussi neutre que possible. Ecrivez bien vos problématiques

Ajoutez svp les nouvelles problématiques en haut de la liste. Relancer svp les problématiques résolues/rejetées avec de la nouvelle information plutôt que de reproposer de telles problématiques. Les ajouts de problématiques en doublons seront révoquées.

== problématiques fermées ==
Les problématiques résolues sur lesquelles il n'y a plus d'action à prendre. Elles seront probablement migrées vers une page distincte comme [[xfn-issues-closed-fr|xfn-problématiques-fermées]].
* ...

== problématiques résolues ==
Les problématiques qui ont été résolues mais peuvent avoir des items en [[to-do]]. Du fait que les problématiques sont résolues, elles seront migrées en haut de la [[xfn-issues-fr#problématiques|liste des problématiques]] en bas de cette section.

=== 2007 ===
<div class="vevent">
* {{AcceptedIssue-fr}} <span class="summary vcard"><span class="dtstart">2007-06-07</span> raised by <span class="fn">[http://factoryjoe.com Chris Messina]</span></span>
<div class="description">
*# 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.
*#* <strong style="text-transform:uppercase">Résolue</strong> FAQ. XFN doesn't define how to process a part of a page, only an entire page.</div>
</div>

<div class="vevent">
* {{AcceptedIssue-fr}} <span class="summary vcard"><span class="dtstart">2007-06-08</span> raised by <span class="fn">[http://suda.co.uk Brian Suda]</span></span>
<div class="description">
*# Does the presence of a query string have any impact on an identity URL in XFN.
*#* <strong style="text-transform:uppercase">Résolu</strong> 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.
</div>
</div>

=== 2008 ===
<div class="vevent">
* <span class="summary vcard"><span class="dtstart">2008-01-16</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
<div class="description">
*# 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).
*#* REJETE PAR DESIGN. See http://gmpg.org/xfn/background#gender for explanation. Gender should be represented as part of a profile / person description, either as an extension to hCard or as a separate [[gender]] microformat.
*#** Per the [[process]], where is the evidence that people publish links using terms like "parent", rather than "mother" or "father" ? [[User:AndyMabbett|Andy Mabbett]] 12:57, 2 Feb 2008 (PST)

</div>
</div>

<div class="vevent">
* <span class="summary vcard"><span class="dtstart">2008-01-30</span> soulevée par <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span>
<div class="description">
*# XFN has no <code>rel="guardian"</code> property, for children who have no (biological or legal) parent. (See: http://www.google.co.uk/search?q=%22parent+or+guardian%22)
*#* ACCEPTEE FAQ. The XFN meaning of parent includes guardian per http://gmpg.org/xfn/background#family . This should be better documented in an FAQ.
*#** XFN may intend that definition, but that is not the commonly-used definition; and such muddying will be offensive to some people. [[User:AndyMabbett|Andy Mabbett]] 11:40, 2 Feb 2008 (PST)
</div>
</div>

== Issues ==
=== 2007 ===

<div class="vevent">
* {{AcceptedIssue}} <span class="summary vcard"><span class="dtstart">2007-10-24</span> [http://twitter.com/markng/statuses/359428672 raised] by <span class="fn">Mark Ng</span></span>
<div class="description">
*# 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.</div>
</div>

=== 2008 ===
<div class="vevent" id="relparentoverloaded">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-29</span> raised by <span class="fn">[[User:Tantek|Tantek Çelik]]</span></span>
<div class="description">
*# Apparently experience with XFN crawling tools has shown that there are non-trivial instances in the wild of rel="parent" that don't mean the XFN definition (e.g. on http://Tv.com ). We need a way to distinguish the XFN [[rel-parent]] from the non XFN uses. A few possibilities:
*#* If there is a reference to the XFN 1.0 or 1.1 [[XMDP]] profile in the <code>head</code> element, then uses of rel="parent" have the XFN meaning.
*#* Otherwise, require [[hCard]] at the from (where the hyperlink is, to make it clear that it is a link to a person) OR at the destination (thus making it clear that the destination is a person) for the XFN rel-parent relation.
*#**Alternatively, extend XFN to use rel="mother" and rel="father". [[User:AndyMabbett|Andy Mabbett]] 00:07, 30 Jan 2008 (PST)
</div>
</div>

<div id="relmeinjection">
* {{OpenIssue}} 2008-02-01 raised by [[User:Tantek|Tantek]]
*# rel-me injection. If a site allows 3rd parties to enter markup into their pages, it may be possible for a 3rd party to enter a hyperlink, perhaps even a hyperlink with a rel attribute, which would enable errant rel-me links. No such known example exists, but the issue has been raised as a possibility, since such sites (or web site software) might exist. If any example is found, please add them to [[rel-me-injection-sites]].
</div>

== gabarit ==
{{issues-format-fr}}

==pages en rapport==
{{xfn-related-pages-fr}}

xfn-issues-fr - Revision history

ChristopheDucamp: [fr:sync'd with english version]