건축
문화
세계고층건물디자인 사진
개인이야기
www.example.net.net/
Example
The following example is assumed to have been found at http://alice.example.net. For simplicity's sake, we assume the low-bandwidth situation.
Friends & Contacts
Page maintained by >Eve Ville. Contact >eve@example.net for corrections. (I know I'm not the most trustworthy
of sources.)
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in step two of the representative hCard parsing procedure because it contains rel="me".
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their foaf:name and foaf:page. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.
Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking hcard:fn to be equivalent to foaf:name.
Organisation hCards and XFN
If either the subject or object hCard represents an organisation (rather than a person), the following relationships are meaningless:
acquaintance
friend
child
parent
sibling
spouse
kin
crush
date
sweetheart
Reverse Relationships
Explicit reverse relationships may be provided by authors using the rev attribute. These should be interpreted by parsers in exactly the same manner as described above, however subject and object must be swapped.
The XFN 1.1 profile (http://gmpg.org/xfn/11) explicitly mentions inverses for some XFN relationships, and lists which relationships are symmetric (i.e. their own inverse). For example, as Alice met Bob, it is implied that Bob met Alice. Parsers may use the information in the profile to make explicit the implicit reverse relationships.
XFN
XFN+hCard supporting friends lists - examples in the wild of XFN usage.
xfn-implementations
xfn-cheatsheet - see http://gmpg.org/xfn/join and existing-rel-values
xfn-faq
xfn-clarifications - should eventually be rolled into XFN info on GMPG.org.
xfn-issues
xfn-brainstorming
xfn-to-foaf - extracting Upper-Case Semantic Web data from XFN and hCard
[edit]Microformats to RDF
XFN → FOAF
xFolk → RDF
See also:
FAQs for RDF
건축법
댓글 없음:
댓글 쓰기