Prosopography - Revision history

Joewiz: /* Projects */ updated link to william still project - the old one yielded a 404 error

2015-08-02T03:18:24Z

Projects: updated link to william still project - the old one yielded a 404 error

← Older revision		Revision as of 03:18, 2 August 2015
Line 227:		Line 227:
	*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])		*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])
	*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])		*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])
	*[http://~~www.~~hsp.org/william-~~still~~ The William Still Digital History Project]		*[http://hsp.org/history-online/digital-history-projects/uncovering-william-stills-underground-railroad The William Still Digital History Project]

	[[Category:Markup]]		[[Category:Markup]]

Dana Dorman: /* Projects */

2013-07-23T18:46:49Z

Projects

← Older revision		Revision as of 18:46, 23 July 2013
Line 227:		Line 227:
	*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])		*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])
	*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])		*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])
			*[http://www.hsp.org/william-still The William Still Digital History Project]

	[[Category:Markup]]		[[Category:Markup]]

Mholmes: /* Projects */

2013-07-03T15:29:26Z

Projects

← Older revision		Revision as of 15:29, 3 July 2013
Line 226:		Line 226:

	*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])		*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])
			*[http://bcgenesis.uvic.ca/ The Colonial Despatches of BC and Vancouver Island] ([http://bcgenesis.uvic.ca/bios.xml XML personography])

	[[Category:Markup]]		[[Category:Markup]]

Mholmes: /* Relations */

2013-07-03T15:27:56Z

Relations

← Older revision		Revision as of 15:27, 3 July 2013
Line 220:		Line 220:

	If the relation element could be placed inside the element which describes the subject (e.g. a person element) then the subject attribute would be implicit.		If the relation element could be placed inside the element which describes the subject (e.g. a person element) then the subject attribute would be implicit.

			==Projects==

			This is a list of projects which have significant prosopography components. Feel free to add your project here. If possible, include links to the XML resources you have created.

			*[http://mapoflondon.uvic.ca/ The Map of Early Modern London] ([http://mapoflondon.uvic.ca/PERS1.xml XML personography])

	[[Category:Markup]]		[[Category:Markup]]

Tfinney: /* Relations */

2011-03-09T08:19:52Z

Relations

← Older revision		Revision as of 08:19, 9 March 2011
Line 219:		Line 219:
	<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>		<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

	If the relation element ~~was allowed~~ inside a person element ~~(which would be a good thing~~) then the subject would be implicit ~~and need not be specified~~.		If the relation element could be placed inside the element which describes the subject (e.g. a person element) then the subject attribute would be implicit.

	[[Category:Markup]]		[[Category:Markup]]

Tfinney: /* Relations */

2011-03-09T08:17:09Z

Relations

← Older revision		Revision as of 08:17, 9 March 2011
Line 219:		Line 219:
	<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>		<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

	If the relation ~~object~~ was allowed inside a person element then the subject would be implicit.		If the relation element was allowed inside a person element (which would be a good thing) then the subject would be implicit and need not be specified.

	[[Category:Markup]]		[[Category:Markup]]

Tfinney: /* Traits, States, and Events */

2011-03-09T08:14:51Z

Traits, States, and Events

← Older revision		Revision as of 08:14, 9 March 2011
Line 208:		Line 208:

	==Traits, States, and Events==		==Traits, States, and Events==
	The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).		The Guidelines use traits, states, and events as basic categories for prosopography. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

	==Relations==		==Relations==

Tfinney: /* Traits, States, and Events */

2011-03-09T08:14:15Z

Traits, States, and Events

← Older revision		Revision as of 08:14, 9 March 2011
Line 208:		Line 208:

	==Traits, States, and Events==		==Traits, States, and Events==
	The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are ~~defined~~ by states and state-transitions (i.e. events).		The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are described by states and state-transitions (i.e. events).

	==Relations==		==Relations==

Tfinney: /* Relations */

2011-03-09T08:12:39Z

Relations

← Older revision		Revision as of 08:12, 9 March 2011
Line 214:		Line 214:

	<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>		<pre><relation name="parent" active="#p1 #p2" passive="#p3 #p4"/></pre>

			An alternative would be to use RDF-like subject, predicate, object triples:

			<pre><relation subject="#p1" predicate="child-of" object="#p2"/></pre>

			If the relation object was allowed inside a person element then the subject would be implicit.

	[[Category:Markup]]		[[Category:Markup]]

Tfinney: /* Traits, States, and Events */

2011-03-09T08:07:01Z

Traits, States, and Events

← Older revision		Revision as of 08:07, 9 March 2011
Line 208:		Line 208:

	==Traits, States, and Events==		==Traits, States, and Events==
	The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. ~~Why have traits when states will do? This would simply leave~~ states and events ~~for describing a person, organization, etc. Every change of state could have an associated event~~.		The Guidelines use traits, states, and events as basic categories. Traits differ from states in being generally immutable. It may be that the distinction between states and traits is unnecessary. Almost every member of model.persTraitLike (age faith langKnowledge nationality s*x socecStatus trait) can change. Dropping "trait" leaves a simple yet expressive model where entities are defined by states and state-transitions (i.e. events).

	==Relations==		==Relations==