1.1 Relationship to other work

This specification depends upon the following XBRL specifications:

• XBRL 2.1 Specification [XBRL 2.1]
• Generic Link Specification [GENERIC LINKS]
• Generic Label Specification [GENERIC LABELS]
• Generic Reference Specification [GENERIC REFERENCES]

In the event of any conflicts between this specification and the specifications upon which it depends, this specification does not prevail.

1.2 Namespaces and namespace prefixes

Namespace prefixes [XML Names] will be used for elements and attributes in the form ns:name where ns is the namespace prefix and name is the local name. Throughout this specification, the mappings from namespace prefixes to actual namespaces is consistent with Table 1.

The prefix column in Table 1 is non normative. The namespace URI column is normative.

1.3 URI resolution

This specification requires Uniform Resource Identifier (URI) [IETF RFC 3986] resolution to honor xml:base attributes.

1.4 Language independence

The official language of XBRL International's own work products is English and the preferred spelling convention is UK English.

1.5 Document conventions

1.6 Terminology

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, in this specification, are to be interpreted as described in [IETF RFC 2119].

The key words schema, substitution group, substitution group affiliation, target namespace, element declaration, content model and actual value in this document are to be interpreted as described in the XML Schema Structures Specification [XML Schema Structures].

The key words element, attribute, local name, namespace name and namespace prefix in this document are to be interpreted as described in the XML Names Specification [XML Names].

The key words arc, base set, concept, DTS, fact, instance, item, linkbase, DTS discovery, roleURI, role type definition, taxonomy and taxonomy schema in this document are to be interpreted as described in the XBRL Specification [XBRL 2.1].

The key words label and generic label in this document are to be interpreted as described in the Generic Labels Specification [GENERIC LABELS].

The key words reference and generic reference in this document are to be interpreted as described in the Generic References Specification [GENERIC REFERENCES].

The key phrase XLink simple link in this document is to be interpreted as described in the XLink Specification [XLINK].

2.1 Versioning Report

2.2 Assignments

An Assignment is a grouping of related Actions.

The grouping of Actions provided by an Assignment allows common documentation (see Section 6) or categorisation (see Section 2.3) to be associated with a set of related Actions.

2.3 Assignment Categories

The specification provides an extensible mechanism for categorising Assignments. This mechanism MAY be used to group Assignments according to the motivation behind the change.

An Assignment Category is a category that may be associated with an Assignment.

This specification defines three standard Assignment Categories:

2.4 Actions

An Action is a grouping of related Events to represent a single, discrete change to the taxonomy.

The group of related Events is used to represent a replacement or renaming relationship, by grouping deleted components in the From DTS with added components in the To DTS. The semantics to be understood from such groupings are defined on the indivdual event types, where applicable.

The @ref attribute of a <ver:assignmentRef> element MUST identify a <ver:assignment> element. Error code vere:invalidAssignmentRef is raised otherwise.

3.1 Namespace Mappings

A Namespace Mapping is the association of a From Namespace with a corresponding To Namespace.

A Namespace Mapping is defined by a Namespace Rename Event. A single namespace name  MAY be involved in more than one Namespace Mapping.

3.2 Role Mappings

A Role Mapping is the association of a From Role URI with a corresponding To Role URI.

A Role Mapping is defined by a Role Change  Event. A single roleURI  MAY be involved in more than one Role Mapping.

4.1 XML Representation

An Event is represented by an element in the <ver:event> substitution group . The <ver:event> element has an open content model; specific Events are represented by non-abstract elements defining specific content models.

4.2 Namespace Rename Event

A Namespace Rename Event associates a namespace name in the From DTS with a namespace name in the To DTS via From Namespace and To Namespace identifiers.

A single namespace name MAY be involved in more than one Namespace Mapping.

4.3 Role Change Event

A Role Change Event associates a roleURI in the From DTS with a roleURI in the To DTS via From Role URI and To Role URI identifiers.

Role Change events MAY be used to describe changes to either extended link roles or resource roles. Note however that the definition of a Role URI Identifier prevents the event from being used with arcroles.

5.1 URI Reference

A URI Reference is an abstract Identifier for any URI.

5.2 DTS identifiers

A DTS Identifier is a specific Identifier, consisting of a set of one or more URIs that are the starting point for DTS discovery for the identified DTS .

5.3 Namespace Name Identifier

A Namespace Name Identifier is a URI Reference that identifies a Namespace Name.

A From Namespace is a namespace name that is the target namespace of a schema in the From DTS.

A To Namespace is a namespace name that is the target namespace of a schema in the To DTS.

5.4 Role Identifier

A Role URI Identifier is a URI Reference that identifies a roleURI.

A From Role URI identifies a roleURI that is defined by a role definition in the From DTS.

A To Role URI identifies a roleURI that is defined by a role definition in the To DTS.

7.1 Versioning Report References

A Versioning Report Reference is a reference to a Related Versioning Report.

Each related versioning report SHOULD be a valid Versioning Report, as defined by this specification. However, a conformant processor is not required to validate related versioning reports.