The GEDCOM X Standard Header Set
This document specifies a standard set of headers used to supply metadata for genealogical resources such as those defined by the GEDCOM X standard conceptual model, and requests discussion and suggestions for improvements.
The current state of this document is as a "stable draft", and as such, the document may be subject to limited changes, BUT NOT backwards-incompatible changes, according to the discussion and suggestions for improvement.
Copyright Intellectual Reserve, Inc.
This document is distributed under a Creative Commons Attribution-ShareAlike license. For details, see:
The GEDCOM X Standard Header Set spec specifies the set of metadata terms that are recognized for genealogical resources and the mechanism for providing that metadata. It supports the GEDCOM X File Format. The spec includes notational conventions, providing headers, header values, and the standard header set.
When processing a set of genealogical resources (such as those defined by the GEDCOM X standard conceptual model) it is often useful--sometimes even necessary--to process metadata for the resource before processing it. Examples of this kind of metadata include:
- The data format for the resource.
- Caching directives such as the last modified timestamp or version.
- Identifiers for the resource.
- Bibliographic metadata, such as a bibliographic citation.
- Display names or titles.
The GEDCOM X Standard Header Set specifies the set of metadata terms that are recognized for genealogical resources and the mechanism for providing that metadata.
Table Of Contents
- 1. Introduction
- 2. Providing Headers
- 3. Header Values
- 4. The Standard Header Set
1.1 Identifier, Version, and Dependencies
The identifier for this specification is:
For convenience, this specification may be referred to as "GEDCOM X Standard Header Set 1.0". This specification uses "GEDCOM X Headers" internally.
This specification depends on the GEDCOM X Date Format identified
1.2 Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC2119, as scoped to those conformance targets.
2. Providing Headers
Headers are provided follow the same generic format as that given in Section 3.1 of RFC 822. Each header consists of a name followed by a colon (":") and the header value. Header names are case-insensitive. The value MAY be preceded by any amount of LWS, though a single SP is preferred. Headers can be extended over multiple lines by preceding each extra line with at least one SP or HT. The header values contain either text or combinations of token, separators, and quoted-string as specified by RFC 822.
The order in which header fields with differing field names are received is not significant.
3. Header Values
Each header MAY supply multiple values. This is done either in a single name-value pair by separating each value by a comma OR in multiple headers of the same name. Order of the values MUST be preserved and MAY be significant based on the definition of the header.
3.1. Text Headers
Values of headers designated as text headers are to be interpreted as text.
3.2. URI Headers
Values of headers designated as URI headers are to be interpreted as a URI that identifies the value of the metadata. For cases in which the value of the metadata may not have an identifier except for its text value, the text value is encoded according to the data URI scheme defined by RFC 2397.
3.3. Date Headers
4. The Standard Header Set
The GEDCOM X Standard Header Set includes the following headers:
|Content-Type||text (media type)||The media type of the resource, as defined by RFC 2616, Section 14.|
|Content-Encoding||text||The encoding of the resource, as defined by RFC 2616, Section 14.|
|Content-Language||text||The language of the content of the resource, as defined by RFC 2616, Section 14.|
|Content-Length||text||The size of the resource, as defined by RFC 2616, Section 14.|
|Content-Location||text||The location of the resource, as defined by RFC 2616, Section 14.|
|Content-MD5||text||The MD5 sum of the resource for integrity checks, as defined by RFC 2616, Section 14.|
|ETag||text||Version of the resource, as defined by RFC 2616, Section 14.|
|User-Agent||text||Information about the user agent originating the request or file, as defined by RFC 2616, Section 14.|
|X-DC-created||date||Date of creation of the resource, as defined by http://purl.org/dc/terms/created.|
|X-DC-creator||URI||Identifier for an entity primarily responsible for making the resource, as defined by http://purl.org/dc/terms/creator.|
|X-DC-conformsTo||URI||Identifier for an established standard to which the described resource conforms, as defined by http://purl.org/dc/terms/conformsTo.|
|X-DC-modified||date||Date on which the resource was changed, as defined by http://purl.org/dc/terms/modified.|