1 Introduction
This document specifies the metadata registration practices used by the UK Access Management Federation for Education and Research (the UK federation) in its role as a metadata registrar. The terms “UK federation registrar” and “the registrar” in this document are to be understood to refer to the UK federation operator or its agents acting in this role.
This document includes documentation of some of the UK federation’s conventions with respect to the elements of metadata included in its published metadata aggregates. Fuller coverage of this topic can be found in [UKFTS].
1.1 Document Status
This edition describes the metadata registration practices of the UK federation with effect from its date of publication as shown on the cover page.
1.2 Notation
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 [RFC2119].
Conventional XML namespace prefixes are used throughout this document to stand for their respective namespaces as follows:
| Prefix | XML Namespace | Defined in |
|---|---|---|
md: |
urn:oasis:names:tc:SAML:2.0:metadata |
[SAML2Meta] |
mdrpi: |
urn:oasis:names:tc:SAML:metadata:rpi |
[SAML-Metadata-RPI-V1.0] |
mdui: |
urn:oasis:names:tc:SAML:metadata:ui |
[SAML-Metadata-UI-V1.0] |
shibmd: |
urn:mace:shibboleth:metadata:1.0 |
[ShibMetaExt] |
This document uses the following typographical conventions in text:
-
<prefix:XMLElement>to signify an XML element. If the prefix is omitted, “md:” can be assumed. -
XMLAttributeto signify an XML attribute. Attributes accompanied by values are written asXMLAttribute="value".
1.3 Changes in this Edition
This is a new document.
1.4 Future Directions
Where appropriate, major sections of this document contain a sub-section called “Future Directions” describing likely future developments in the area under consideration. These notes are provided to allow members to incorporate this information into planning activities.