Difference between revisions of "abcd2:UnitContentContact-InheritedName"

Revision as of 08:42, 7 September 2016 (view source) Terms Upload Bot (Talk | contribs) (→‎top: mass importing all ABCD 2.06 concepts)		Latest revision as of 11:41, 24 January 2017 (view source) Terms Upload Bot (Talk | contribs) (added ABCD2 Hierarchy segment)
Line 50:		Line 50:
	|type=String255		|type=String255
	}}		}}
		+
		+	== ABCD2 Hierarchy ==
		+	{{XPathSegments|abcd2:|/DataSets|/DataSet|/Units|/Unit|/UnitContentContacts|/UnitContentContact|/Person|/AtomisedName|/InheritedName}}

---

Latest revision as of 11:41, 24 January 2017

Scheme: ABCD 2 
Collection: ABCD UnitContentContact 

UnitContentContact-InheritedName No type definition was found for "UnitContentContact-InheritedName" in the abcd2 import. URI: http://rs.tdwg.org/abcd2/terms/UnitContentContact-InheritedName

RDF feed | Browse properties | SMW-prop.

Search for values

UnitContentContact-InheritedName (also /DataSets/DataSet/Units/Unit/UnitContentContacts/UnitContentContact/Person/AtomisedName/InheritedName): The inherited name of the administrative contact for the unit record. This may consist of family names, generational names, a clan name, parents or grandparents personal names, etc. The inherited name (this being the lastname in western cultures) may be compound (e.g. 'Fischer von Waldheim', 'da Selva', 'Silvano Morales'). Depending on culture, the inherited name is not necessarily the name of the parents nor common to a married couple. Therefore, 'family name' should be avoided even though used in vCard (vCard: N-Family).

Constraints in the context of ABCD 2:

• cardinality 1..1 (=mandatory single occurrence)

ABCD2 Hierarchy

XPath Segments: /DataSets /DataSet /Units /Unit /UnitContentContacts /UnitContentContact /Person /AtomisedName /InheritedName