relationship-status: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎relationship status examples: add socialight and plurk, via links found on http://wiki.activitystrea.ms/heart)
(→‎relationship status brainstorming: add more to schema based on additional real world examples, analysis, and suggestions for possible new XFN values as well)
Line 79: Line 79:


=== schema ===
=== schema ===
There seems to be quite a variety of different values for "relationship-status", here are the ones that appear on more than one of the above-mentioned examples:
Full set - union of above examples:


* single
Here is a unified enumerated list of all the above relationship statuses (parenthetical text provided for turning the statuses into sentences and optional person parameter where it might apply, note that not all instances of optional with person parameter have been found in the wild, but they may be possible in UIs - indicated as "possible optional").
* taken (in a relationship)
* open (in an open relationship)
* unspecified (blank, rather not say)


While this might be a good start for a set of enumerated values, we lack sufficient data to be confident in such an enum. If we had perhaps half dozen or so examples total which showed a clear set of common values, then we could be more confident defining an enum.
* (blank - unspecified)
** aliases: Rather not say, Not Saying
* (is) <strong>single</strong>
* (is in a) <strong>complicated</strong>&nbsp;(relationship)
* (is in an) <strong>open </strong>(relationship optional: with person)<strong>&nbsp;</strong>
* (is in a) <strong>relationship</strong> (optional: with person)
** aliases: Taken
* (is) <strong>engaged</strong> (optional: to person)
* (is) <strong>married</strong> (optional: to person)
* (is) <strong>separated</strong> (possible optional: from person - no real world examples found yet)
* (is) <strong>divorced</strong> (possible optional: from person - no real world examples found yet)
* (is) <strong>widowed</strong> (possible optional: from person - no real world examples found yet)
 
From this variety of different values for "relationship-status", here are the ones that appear on more than one of the above-mentioned examples (in frequency order, clustered)
 
* unspecified (all examples)
* single (all examples)
* taken (all examples)
 
* open (Facebook, Flickr, Plurk)
* married (Facebook, Socialight, Plurk)
* divorced (Facebook, Socialight, Plurk)
 
* engaged (Facebook, Plurk)
* complicated (Facebook, Plurk)
* widowed (Facebook, Plurk)
 
While this might be a good start for a set of enumerated values, we lack sufficient data to be confident in such a set. If we had perhaps half dozen or so examples total which showed a clear set of common values, then we could be more confident defining an enum.


Until then, it may make the most sense to simply use a text string value.
Until then, it may make the most sense to simply use a text string value.


In addition to the description of the relationship-status, some number of values take a "with" parameter referring to a person.
In addition to the description of the relationship-status, as noted, some number of values take a "with" parameter referring to a person.
 
As it's a reference to a person, a link to that person makes the most sense, using [[XFN]] on that link to indicate the relationship with/to that person. XFN already has the following rel values which correspond roughly to the above relationship statuses:
* taken: XFN [[rel-sweetheart]]
* married: XFN [[rel-spouse]]
 
For "engaged", there is nothing that corresponds in XFN, e.g. "fiance" or "fiancee" - this may be worthy of writing up as a potential new XFN value on [[xfn-brainstorming]]:
* "fiancee/fiance" - used on a link to someone who is the person is engaged to. both spellings accepted, neither implies the gender of either person.
 
For "open", XFN's rel-sweetheart can be used but might not convey sufficient semantics, since rel-sweetheart states "typically exclusively".  Thus this is another case where another it might make sense to add another proposal to [[xfn-brainstorming]]:
* "open-sweetheart" (other suggestions encouraged) - Someone with whom you are intimate and at least somewhat committed, but open to other romantic relationships. Symmetric. Not transitive.  Essentially like "sweetheart" but without implication of exclusivity.


As it's a reference to a person, a link to that person makes the most sense, using [[XFN]] on that link to indicate the relationship with/to that person.
The other relationship values that involve another person (divorced, separated, widowed) so far have no documented examples in the wild which refer to another person, thus it is premature to brainstorm possible XFN values for them.


=== relationship-status property name ===
=== relationship-status property name ===

Revision as of 17:45, 10 December 2010

<entry-title>relationship status</entry-title>

Part of hcard-brainstorming for post-vCard3 additions. Per the microformats process:

relationship status examples

(move to a separate page relationship-status-examples when this section gets too big to include inline)

Facebook

From http://www.facebook.com/editprofile.php?sk=relationships (must be logged in)

Relationship status has two parts, one a discrete enumerated set provided as a select pop-up menu choice:

  • (blank) - unspecified
  • single
  • in a relationship
  • engaged
  • married
  • it's complicated
  • in an open relationship
  • widowed
  • separated
  • divorced

And then for *some* of those enumerated values, there is an optional field that indicates a person

  • with person - chosen by selecting another profile (URL)

Flickr

From http://www.flickr.com/profile_edit.gne?from=personal (must be logged in)

Expressed as Singleness: by Flickr, the following mutually-exclusive radio button choices are given:

  • ( ) Single
  • ( ) Taken
  • ( ) Open
  • ( ) Rather not say

Socialight

2476366643_35a474a682_o.png

Relationship Status pop-up menu with the following choices:

  • (blank) - unspecified
  • Single
  • Divorced
  • Married
  • Taken
  • In a relationship
  • Swinger!

Plurk

2545866260_166fc6c4d9_o.png

Relationship: pop-up menu with the following choices:

  • Not Saying
  • Single
  • Married
  • Divorced
  • Engaged
  • In Relationship
  • Complicated
  • Widowed
  • Open relationship

relationship status formats

(move to a separate page relationship-status-formats when this section gets too big to include inline)

OpenSocial

OpenSocial has a "relationship-status" field, plain text.

XFN

XFN was not directly intended as a relationship status format, however, it's use can imply some relationship.

Specifically the following family and romantic values imply relationship status:

  • spouse - implies married
  • sweetheart - implies in a relationship (or an open relationship)

relationship status brainstorming

(move to a separate page relationship-status-brainstorming when this section gets too big to include inline)

schema

Full set - union of above examples:

Here is a unified enumerated list of all the above relationship statuses (parenthetical text provided for turning the statuses into sentences and optional person parameter where it might apply, note that not all instances of optional with person parameter have been found in the wild, but they may be possible in UIs - indicated as "possible optional").

  • (blank - unspecified)
    • aliases: Rather not say, Not Saying
  • (is) single
  • (is in a) complicated (relationship)
  • (is in an) open (relationship optional: with person) 
  • (is in a) relationship (optional: with person)
    • aliases: Taken
  • (is) engaged (optional: to person)
  • (is) married (optional: to person)
  • (is) separated (possible optional: from person - no real world examples found yet)
  • (is) divorced (possible optional: from person - no real world examples found yet)
  • (is) widowed (possible optional: from person - no real world examples found yet)

From this variety of different values for "relationship-status", here are the ones that appear on more than one of the above-mentioned examples (in frequency order, clustered)

  • unspecified (all examples)
  • single (all examples)
  • taken (all examples)
  • open (Facebook, Flickr, Plurk)
  • married (Facebook, Socialight, Plurk)
  • divorced (Facebook, Socialight, Plurk)
  • engaged (Facebook, Plurk)
  • complicated (Facebook, Plurk)
  • widowed (Facebook, Plurk)

While this might be a good start for a set of enumerated values, we lack sufficient data to be confident in such a set. If we had perhaps half dozen or so examples total which showed a clear set of common values, then we could be more confident defining an enum.

Until then, it may make the most sense to simply use a text string value.

In addition to the description of the relationship-status, as noted, some number of values take a "with" parameter referring to a person.

As it's a reference to a person, a link to that person makes the most sense, using XFN on that link to indicate the relationship with/to that person. XFN already has the following rel values which correspond roughly to the above relationship statuses:

For "engaged", there is nothing that corresponds in XFN, e.g. "fiance" or "fiancee" - this may be worthy of writing up as a potential new XFN value on xfn-brainstorming:

  • "fiancee/fiance" - used on a link to someone who is the person is engaged to. both spellings accepted, neither implies the gender of either person.

For "open", XFN's rel-sweetheart can be used but might not convey sufficient semantics, since rel-sweetheart states "typically exclusively". Thus this is another case where another it might make sense to add another proposal to xfn-brainstorming:

  • "open-sweetheart" (other suggestions encouraged) - Someone with whom you are intimate and at least somewhat committed, but open to other romantic relationships. Symmetric. Not transitive. Essentially like "sweetheart" but without implication of exclusivity.

The other relationship values that involve another person (divorced, separated, widowed) so far have no documented examples in the wild which refer to another person, thus it is premature to brainstorm possible XFN values for them.

relationship-status property name

Simple brainstorm proposal: use the property name relationship-status as a class name on an element marking up a textual value / description of the person's relationship status.

E.g. 

<span class="vcard"> 
 <a class="fn url" href="http://alice.example.com">Alice Exemplar</a>, 
 <span class="relationship-status">single</span>
</span>

or 

<span class="vcard"> 
 <a class="fn url" href="http://bob.example.com">Bob Exemplar</a>, 
 <span class="relationship-status">taken</span> - in a relationship with 
 <a rel="sweetheart" href="http://dana.example.com">Dana Person</a>
</span>

external resources

see also

Retrieved from "http://microformats.org/wiki/index.php?title=relationship-status&oldid=43381"