PubIDPubID

Technical Report

IndustryTR

Description

Ecma Technical Reports — informative documents providing technical guidance, rationale, or experimental results that support Ecma Standards. Identified by the 'TR/' separator between the publisher token and the sequence number.

Syntax

ECMA identifiers follow three shapes depending on the document class. Standards: 'ECMA-<number>[-<part>]' (the publisher token joins the number directly with no space; part only appears for multi-part standards like ECMA-418-1). Technical Reports: 'ECMA TR/<number>'. Mementos: 'ECMA MEM/<number>'. Edition is separate metadata and is NOT rendered in the printed identifier string.

Examples 2

ECMA TR/101
ECMA TR/53

Components Used

ECMA Technical Report identifiers are composed of these elements:

Publisher

ECMA — joined directly to standard number with no space ('ECMA-262'), separated by a space for TR/MEM ('ECMA TR/101')

e.g.ECMA
Type Prefix

nil for Standards, 'TR' for Technical Reports, 'MEM' for Mementos

:type_prefix
Number

Document number, kept as a string to preserve any leading zeros

e.g.262
:number
Part

Part number for multi-part standards, appended with hyphen (e.g. '-1' in ECMA-418-1)

e.g.1
:part
Edition

Edition metadata (separate from the printed identifier). Decimal editions like '5.1' occur. NOT rendered in to_s.

:edition

Algebraic Relations

Relations that can involve Technical Report identifiers:

RelationDescriptionSyntaxExample
StandardPublisher joined directly to number with no spaceECMA-<number>[-<part>]ECMA-262
Multi-part StandardStandard split into multiple partsECMA-<number>-<part>ECMA-418-1
Technical ReportTR separated by space + slashECMA TR/<number>ECMA TR/101
MementoMEM separated by space + slash, year as numberECMA MEM/<year>ECMA MEM/1970
Without PublisherBare form, no leading ECMA token-<number> | TR/<number> | MEM/<year>-262

URN Mapping

Patternurn:ecma:[type]:[number]:[part]

See Also