Difference between revisions of "abcd2:UnitExtension"

Revision as of 10:02, 7 September 2016 (view source) Terms Upload Bot (Talk | contribs) (→‎top: mass importing all ABCD 2.06 concepts)		Latest revision as of 13:49, 24 January 2017 (view source) Terms Upload Bot (Talk | contribs) (added ABCD2 Hierarchy segment)
Line 50:		Line 50:
	|type=anyType		|type=anyType
	}}		}}
		+
		+	== ABCD2 Hierarchy ==
		+	{{XPathSegments|abcd2:|/DataSets|/DataSet|/Units|/Unit|/UnitExtension}}

---

Latest revision as of 13:49, 24 January 2017

Scheme: ABCD 2 
Collection: ABCD Unit 

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

RDF feed | Browse properties | SMW-prop.

Search for values

UnitExtension (also /DataSets/DataSet/Units/Unit/UnitExtension): The extension is temporary and serves only to accommodate urgent inter-version additions to the unit-object schema [in the future to the the various schemas/objects used in ABCD].

For example, if a specific community (e.g. culture collections) discover that there are elements missing in the current version of ABCD (as they did for 1.2), they communicate that to the group responsible for schema development, who will discuss whether these elements are already accommodated in the schema, if they are not and if they can and should be generalized, and where they should end up in the schema. IF the culture collection community needs to move rapidly (e.g. due to project pressures), they can add these elements to the current version as an extension schema under a structure that follows SDD's CustomExtensions element (CustomExtensions-CustomExtension-Any ##other). In future modular versions of ABCD, such a structure should exist in the root of every object/schema.

Constraints in the context of ABCD 2:

• cardinality 0..1 (=optional single occurrence)

ABCD2 Hierarchy

XPath Segments: /DataSets /DataSet /Units /Unit /UnitExtension