genealogy-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:22:42Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:22, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Genealogy Brainstorming~~</entry-title>~~		{{DISPLAYTITLE:Genealogy Brainstorming}}
	Per the microformats [[process]], towards the development of a [[genealogy]] microformat, this page documents brainstorms that should be based on modeling the 80/20 of real world [[genealogy-examples\|examples of genealogy]] publishing on the web, preferably re-using terminology from [[genealogy-formats\|existing genealogy formats]].		Per the microformats [[process]], towards the development of a [[genealogy]] microformat, this page documents brainstorms that should be based on modeling the 80/20 of real world [[genealogy-examples\|examples of genealogy]] publishing on the web, preferably re-using terminology from [[genealogy-formats\|existing genealogy formats]].

Madmurphy: /* Issue */

2017-02-24T12:50:26Z

Issue

← Older revision		Revision as of 12:50, 24 February 2017
Line 67:		Line 67:
	** Could use <code>abbr</code>		** Could use <code>abbr</code>
	** See also [http://www.getsemantic.com/wiki/GenderHack GenderHack]		** See also [http://www.getsemantic.com/wiki/GenderHack GenderHack]
			* What about the hierarchical uses of "parent" and "child" that had been proposed in [https://www.w3.org/TR/relations.html HTML 4.0 Specification]?
			** "parent": the target document is the hierarchical parent, or container, of the current document
			** "child": the target document is a hierarchical child, or subdocument, of the current document

	===Relationships===		===Relationships===

Tantek: entry-title, intro

2011-09-28T02:17:08Z

entry-title, intro

← Older revision		Revision as of 02:17, 28 September 2011
Line 1:		Line 1:
	=Genealogy Brainstorming=		<entry-title>Genealogy Brainstorming</entry-title>
			Per the microformats [[process]], towards the development of a [[genealogy]] microformat, this page documents brainstorms that should be based on modeling the 80/20 of real world [[genealogy-examples\|examples of genealogy]] publishing on the web, preferably re-using terminology from [[genealogy-formats\|existing genealogy formats]].

	==Contributors==		==Contributors==
Line 23:		Line 24:

	===Gender===		===Gender===
			'''Update''': note that [[vCard4]] has a "gender" property that is likely to be incorporated into the next version of [[hCard]].

	To make life easier for publishers, the following values could all equate, without requiring the use of <code>abbr</code> to:		To make life easier for publishers, the following values could all equate, without requiring the use of <code>abbr</code> to:

TobyInk: /* Relationships */ XFN scoping issue

2008-08-31T19:10:11Z

Relationships: XFN scoping issue

← Older revision		Revision as of 19:10, 31 August 2008
Line 95:		Line 95:
	*Each page {{should}} or {{must}} have one and only one hCard for a person, who {{must}} be the person in the relationship (this allows for non- personal hCards for publishing organisations, in hResume, etc. Otherwise, the system would fail if, say, rel-spouse linked to page, about a person whose sibling or colleague was also hCarded on that page, even if that page was primarily about the person referred to by the "rel".		*Each page {{should}} or {{must}} have one and only one hCard for a person, who {{must}} be the person in the relationship (this allows for non- personal hCards for publishing organisations, in hResume, etc. Otherwise, the system would fail if, say, rel-spouse linked to page, about a person whose sibling or colleague was also hCarded on that page, even if that page was primarily about the person referred to by the "rel".
	**This could be avoided by linking to page-fragments using IDs <code><a href="myfamily#dad" rel="father">Dad</a></code>; <code><a href="myfamily#mom" rel="mother">Mom</a></code> with a stipulation of one hCard per ID (or that only the first hCard at that fragment is considered); since the [http://www.w3.org/TR/html401/struct/links.html#adef-rel defined purpose of "rel"] is to "[describe] the relationship from the current document to the anchor specified by the href attribute" and not "the page specified by the href attribute".		**This could be avoided by linking to page-fragments using IDs <code><a href="myfamily#dad" rel="father">Dad</a></code>; <code><a href="myfamily#mom" rel="mother">Mom</a></code> with a stipulation of one hCard per ID (or that only the first hCard at that fragment is considered); since the [http://www.w3.org/TR/html401/struct/links.html#adef-rel defined purpose of "rel"] is to "[describe] the relationship from the current document to the anchor specified by the href attribute" and not "the page specified by the href attribute".
			***Although the link can point ''to'' a fragment ID, it can't point ''from'' a fragment ID. This is a general weakness with the <code>rel</code> and <code>rev</code> attributes — it can only be solved using [http://www.w3.org/TR/rdfa-syntax/ RDFa] which amongst other things provides scoping for <code>rel</code> and <code>rev</code>. This is not just a theoretical problem — any solution that tried to use XFN to provide relationship links within a page while ignoring this issue would break virtually all existing [[xfn-implementations\|XFN implementations]].

	See also: [[xfn-brainstorming#Extending_family_relationships]]		See also: [[xfn-brainstorming#Extending_family_relationships]]

RobSalzman: /* Locations */

2008-04-07T17:11:10Z

Locations

← Older revision		Revision as of 17:11, 7 April 2008
Line 123:		Line 123:
	* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk\|TobyInk]] 00:41, 7 Apr 2008 (PDT)		* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk\|TobyInk]] 00:41, 7 Apr 2008 (PDT)

	[[User: RobSalzman\|Rob Salzman]] Unless there is only a single person on an html page, I don't see how you can use an hCalendar event for marriage, or XRel's for relationships either.		----

			'''[[User: RobSalzman\|Rob Salzman]] 10:10, 7 Apr 2008 (PDT)''' Unless there is only a single person on an html page, I don't see how you can use an hCalendar event for marriage, or XRel's for relationships either.

	My Family Sheets are organized like this:		My Family Sheets are organized like this:

RobSalzman: /* Locations */

2008-04-07T17:09:39Z

Locations

← Older revision		Revision as of 17:09, 7 April 2008
Line 123:		Line 123:
	* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk\|TobyInk]] 00:41, 7 Apr 2008 (PDT)		* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk\|TobyInk]] 00:41, 7 Apr 2008 (PDT)

	Unless there is only a single person on an html page, I don't see how you can use an hCalendar event for marriage, or XRel's for relationships either.		[[User: RobSalzman\|Rob Salzman]] Unless there is only a single person on an html page, I don't see how you can use an hCalendar event for marriage, or XRel's for relationships either.

	My Family Sheets are organized like this:		My Family Sheets are organized like this:

RobSalzman: /* Locations */

2008-04-07T17:08:45Z

Locations

@@ Line 122: / Line 122: @@
 * The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk|TobyInk]] 00:40, 7 Apr 2008 (PDT)
 * For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk|TobyInk]] 00:41, 7 Apr 2008 (PDT)
 ==See also==
 {{genealogy-related-pages}}

TobyInk: /* Locations */

2008-04-07T07:41:48Z

Locations

← Older revision		Revision as of 07:41, 7 April 2008
Line 121:		Line 121:
	x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.		x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.
	* The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk\|TobyInk]] 00:40, 7 Apr 2008 (PDT)		* The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk\|TobyInk]] 00:40, 7 Apr 2008 (PDT)
	* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees?		* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees? [[User:TobyInk\|TobyInk]] 00:41, 7 Apr 2008 (PDT)

	==See also==		==See also==
	{{genealogy-related-pages}}		{{genealogy-related-pages}}

TobyInk: /* Locations */

2008-04-07T07:41:32Z

Locations

← Older revision		Revision as of 07:41, 7 April 2008
Line 120:		Line 120:
	These things are very difficult to encode in an hcard. I did it on my genealogy website by coding		These things are very difficult to encode in an hcard. I did it on my genealogy website by coding
	x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.		x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.
	** The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk\|TobyInk]] 00:40, 7 Apr 2008 (PDT)		* The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk\|TobyInk]] 00:40, 7 Apr 2008 (PDT)
	** For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees?		* For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees?

	==See also==		==See also==
	{{genealogy-related-pages}}		{{genealogy-related-pages}}

TobyInk: /* Locations */ Ideas re births, deaths and marriages.

2008-04-07T07:40:55Z

Locations: Ideas re births, deaths and marriages.

← Older revision		Revision as of 07:40, 7 April 2008
Line 120:		Line 120:
	These things are very difficult to encode in an hcard. I did it on my genealogy website by coding		These things are very difficult to encode in an hcard. I did it on my genealogy website by coding
	x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.		x-birth-location, x-marriage-date, x-marriage-location, x-death-date, and x-death-location, but this, i am confident is NOT the correct way to do this.
			** The new vCard draft has properties called "dday" (for date of death) and "birth" and "death" for locations of each. [[User:TobyInk\|TobyInk]] 00:40, 7 Apr 2008 (PDT)
			** For marriage, perhaps a hCalendar Event with the bride and groom each given as attendees?

	==See also==		==See also==
	{{genealogy-related-pages}}		{{genealogy-related-pages}}