| Data Category: keyValuePair | |
|---|---|
| Key | 3898 |
| PID | http://www.isocat.org/datcat/DC-3898 |
| Type | complex/open |
| Owner | Krivanek, Julia |
| Scope | public |
| 1. Administration Information Section | |
| 1.1 Administration Record | |
| Identifier | keyValuePair |
| Version | 1:0 |
| Registration Status | private |
| Administration Status | private |
| Justification | Common metadata data category |
| Origin | IMDI: session.keys.key |
| 1.1.1 Creation | |
| Creation Date | 2011-04-20 |
| Change Description | Creation of the new data category. |
| 1.1.2 Last Change | |
| Last Change Date | 2012-01-17 |
| Change Description | Clean up according to DCSpecificationForm.pdf |
| 2. Description Section | |
| Profile | Metadata |
| 2.1 Data Element Name Section | |
| Data Element Name | keyValuePair |
| Source | CMDI |
[-]2.2 English Language Section | |
| Language | English (en) |
| 2.2.1 Name Section | |
| Name | keyValuePair |
| Name Status | preferred name |
| 2.2.2 Definition Section | |
| Definition | Indication of an entity consisting of a pair with a key and a value to specify a property. |
| Source | NaLiDa |
| 2.2.3 Example Section | |
| Example | length=182, transcription-convention=HIAT, segmented=false, etc. |
| Source | NaLiDa |
| 2.2.4 Explanation Section | |
| Explanation | Especially in legacy data there are data categories that are idiosyncratic. To allow for these to be included, key-value pairs can be used. Note that key-value-pairs may contain both key and value as separate structures or as a string consisting of both parts. While the description elements are free text elements, keys are more formal notations that can also be exploited by search engines. The name of a key-value-pair can be stored as an attribute of a keyValuePair element. |
| Source | NaLiDa |
| 3. Conceptual Domain | |
| Data Type | string |