Difference between revisions of "relationship-status"

From Microformats Wiki
relationship-status
Jump to navigation Jump to search
(→‎relationship status examples: add socialight and plurk, via links found on http://wiki.activitystrea.ms/heart)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<entry-title>relationship status</entry-title>
+
{{DISPLAYTITLE:relationship status}}
  
 
Part of [[hcard-brainstorming]] for post-vCard3 additions.  Per the microformats process:
 
Part of [[hcard-brainstorming]] for post-vCard3 additions.  Per the microformats process:
Line 9: Line 9:
  
 
From http://www.facebook.com/editprofile.php?sk=relationships (must be logged in)
 
From http://www.facebook.com/editprofile.php?sk=relationships (must be logged in)
 +
 +
[http://www.facebook.com/editprofile.php?sk=relationships http://i.huffpost.com/gen/248929/FACEBOOK-CIVIL-UNION.jpg]
  
 
Relationship status has two parts, one a discrete enumerated set provided as a select pop-up menu choice:
 
Relationship status has two parts, one a discrete enumerated set provided as a select pop-up menu choice:
Line 21: Line 23:
 
* separated
 
* separated
 
* divorced
 
* divorced
 +
Added 2011-048:
 +
* in a civil union
 +
* in a domestic partnership
  
 
And then for *some* of those enumerated values, there is an optional field that indicates a person
 
And then for *some* of those enumerated values, there is an optional field that indicates a person
Line 34: Line 39:
 
* ( )  Open
 
* ( )  Open
 
* ( )  Rather not say
 
* ( )  Rather not say
 +
 +
=== Google+ ===
 +
[http://www.flickr.com/photos/wnorris/6024276982/ http://farm7.static.flickr.com/6198/6024276982_e0581a5834_o.png]
 +
 +
Relationship Status pop-up menu with the following choices:
 +
* I don't want to say
 +
* Single
 +
* In a relationship
 +
* Engaged
 +
* Married
 +
* It's complicated
 +
* In an open relationship
 +
* Widowed
 +
* In a domestic partnership
 +
* In a civil union
  
 
=== Socialight ===
 
=== Socialight ===
Line 60: Line 80:
 
* Widowed
 
* Widowed
 
* Open relationship
 
* Open relationship
 +
 +
=== OKCupid ===
 +
 +
On signup:
 +
 +
* Gender:
 +
** I'm female
 +
** I'm male
 +
* Orientation:
 +
** I'm straight
 +
** I'm gay
 +
** I'm bisexual
 +
* Status:
 +
** I'm single
 +
** I'm seeing someone / here for friends
 +
** I'm married / here for friends
  
 
== relationship status formats ==
 
== relationship status formats ==
Line 79: Line 115:
  
 
=== 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:
 +
 
 +
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) <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 in a) <strong>domestic partnership</strong> (optional: with person)
 +
* (is in a) <strong>civil union</strong> (optional: with 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)
  
* single
+
all examples:
* taken (in a relationship)
+
* unspecified (all examples)
* open (in an open relationship)
+
* single (all examples)
* unspecified (blank, rather not say)
+
* taken (all examples)
 +
4:
 +
* open (Facebook, Flickr, Google+, Plurk)
 +
* married (Facebook, Socialight, Google+ Plurk)
 +
3:
 +
* divorced (Facebook, Socialight, Plurk)
 +
2:
 +
* engaged (Facebook, Plurk)
 +
* complicated (Facebook, Plurk)
 +
* domestic partnership (Facebook, Google+)
 +
* civil union (Facebook, Google+)
 +
* 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 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.
+
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.
+
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.
 +
 
 +
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 ===
Line 116: Line 192:
 
</source>
 
</source>
  
== external resources ==
+
== related ==
* http://wiki.activitystrea.ms/w/page/28041547/heart - I did some previous research on relation status, specifically within the context of an activity of changing it, on the Activity Streams wiki. Should incorporate that here too. - [[User:Tantek|Tantek]]
+
* relationship status <em>update</em> - ActivityStreams deal with the changing of relationship status, and I've started documenting research and brainstorming specifically regarding *updates* to relationship status. - [[User:Tantek|Tantek]]
 
+
** http://wiki.activitystrea.ms/heart
 +
* blog posts about this:
 +
** 2010-12-02 [http://tantek.com/2010/336/b1/dating-preferences-public-profiles-formats-federating Of Dating Preferences, Public Profiles, and Formats For Federating It All]
 
== see also ==
 
== see also ==
 
* [[interested-in]]
 
* [[interested-in]]
Line 125: Line 203:
 
* [[user-profile]]
 
* [[user-profile]]
 
* [[vcard-suggestions]]
 
* [[vcard-suggestions]]
 +
* [[gender]]

Latest revision as of 16:32, 18 July 2020


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)

FACEBOOK-CIVIL-UNION.jpg

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

Added 2011-048:

  • in a civil union
  • in a domestic partnership

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

Google+

6024276982_e0581a5834_o.png

Relationship Status pop-up menu with the following choices:

  • I don't want to say
  • Single
  • In a relationship
  • Engaged
  • Married
  • It's complicated
  • In an open relationship
  • Widowed
  • In a domestic partnership
  • In a civil union

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

OKCupid

On signup:

  • Gender:
    • I'm female
    • I'm male
  • Orientation:
    • I'm straight
    • I'm gay
    • I'm bisexual
  • Status:
    • I'm single
    • I'm seeing someone / here for friends
    • I'm married / here for friends

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 - The XHTML Friends Network 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 in a) domestic partnership (optional: with person)
  • (is in a) civil union (optional: with 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)

all examples:

  • unspecified (all examples)
  • single (all examples)
  • taken (all examples)

4:

  • open (Facebook, Flickr, Google+, Plurk)
  • married (Facebook, Socialight, Google+ Plurk)

3:

  • divorced (Facebook, Socialight, Plurk)

2:

  • engaged (Facebook, Plurk)
  • complicated (Facebook, Plurk)
  • domestic partnership (Facebook, Google+)
  • civil union (Facebook, Google+)
  • 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 - The XHTML Friends Network 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>

related

see also