자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

This page is for documenting Q&A about XFN in addition to the official XFN FAQ. It is likely that objects right here will likely be integrated there. Or perhaps GMPG may select to redirect the FAQ here - this is to be determined. For now, if you have a new question to ask about XFN, please consider first asking your query on the microformats-focus on mailing listing. Please first learn the official XFN FAQ. How do I reference the XFN profile in HTML5? AKA the obsolete profile attribute problem. The profile attribute on the top element is obsolete. Does it's at all times implied as a romantic relationship, since one could certainly find someone else inspiring without being romantically concerned/involved? Certainly "muse" was not meant to only be purely romantic within the literal "romantic relationship" sense (though it is evident how that might easily be misconstrued), and of course that which means is included. The XFN spec defines muse in addition to crush, and one ought not to be confused with the opposite.

Either manner, romantically or figuratively, the muse evokes. How do I markup my relationship to companies I used to work for? Markup corporations that you used to work for on your resume web page with hResume. Agreement in the English language it each job is captured as an hCalendar event with a nested hCard that represents your identity (title, url, org-unit and so forth) whilst you had been at that firm. For current companies and organizations that you are a part of, take a look at the rel-group microformat brainstorm proposal. How do I markup those who I used to work with? Use the XFN 'colleague' relationship to markup your current relationship to your former co-employees. In addition, you need to use XFN on hyperlinks to people within a weblog put up set a date and time context for when that relationship was true. Thus over time, it is feasible to make use of totally different XFN values to reflect the evolving nature of your relationships. See XFN: Background: Out of time for extra.

Is there anything in there for locative information, like 'my workplace,' and so forth.? We now have "rel" tags for humans. Is there an equal for location and place? Markup location info related to your workplace as a part of your sort work address (adr) in your hCard. Wondering why XFN definitions do not embrace "idiot", "enemy", "jerk", "pedant", and so forth. Negative relationship terms have been omitted from XFN by design. The authors think that such values wouldn't serve a optimistic ends and thus made the deliberate resolution to depart them out. From "XFN Background: Positive or neutral relationships only" - more causes and explanation provided there. Is there such a factor as an asymmetric xfn relationship? Most XFN relationships aren't required to be symmetric and are due to this fact typically asymmetric in real world use. This might probably use extra actual world analysis. All different XFN 1.1 relationships aren't required to be symmetric, nor can they essentially or ought to be expected to be.

Is there a 'fans' or 'fan of' kind of XFN relationship? See XFN Brainstorming: followers and followers. If I'm a fan of somebody, what XFN rel worth ought to I exploit when linking to them? Right now there is no such thing as a good inverse time period for stating that you are a fan of someone. Follow-up: Would I establish as an acquaintance of that individual? Not necessarily. rel-acquaintance asserts greater than that, that is, that you've got at the least had a conversation or some kind of interaction with them. You do not essentially have any interplay with people that you're a fan of. For now, you may use rel-contact to at the very least assert that you've some contact information for that person (their URL presmably) or consider that person to be a contact, but even that doesn't convey the meaning that you are a fan of theirs. Wondering how individuals intend to validate xfn… Use the rel-lint validator by Drew McLellan which checks a page for customary rel values from HTML 4.01 and XFN 1.1, and reveals warnings for any unrecognized values.