Module Info
- Reference
BT4PT-GeneralElementsV1-0- Numeric OID
1.3.6.1.4.1.17218.1.2.1.1.0
BT4PT-GeneralElementsV1-01.3.6.1.4.1.17218.1.2.1.1.0This module explicitly exports all symbols.
This module does not import any symbols.
This data structure is used throughout this standard when encoding as identifier for some object, event, entity, etc. The exact values and their meaning are defined by the context in which the identifier is used.
When encoding an identifier, an implementation of this standard SHALL:
idNum variant, if the value to be encoded is contains only numerical characters;idStr variant, if the value to be encoded is contains only alphanumerical character, or;idOct variant, if the value to be encoded is binaryThe choice of variant has no differentiating effect on the value in equality comparisons.
That is, 1234 encoded as an idNum is the exact same logical value as the string "1234" encoded as idStr,
and the same logical value as the binary string '31323334'H.
The value of this choice may be one of the following:
To be used for numeric IDs.
To be used for alphanumeric IDs.
To be used for binary IDs, such as UUIDs.
This data structure is used throughout this standard to specify which dataset an identifier references. This avoids possible confusions between, e.g. station identifier 1312 being assigned to different stations in different national schemes.
This sequence contains the following fields:
This field defines which organisation or entity controls or otherwise administers the dataset to which an identifier refers.
The value of this choice may be one of the following:
Identifiers are defined by the issuer. When decoding this variant SHALL be dereferenced to
the contextually relevant CompanyCode. When encoding, this variant SHALL be preferred over the variant
Company where possible, to save encoding space.
Identifiers are defined by the product owner. When decoding this variant SHALL be dereferenced to
the contextually relevant CompanyCode. When encoding, this variant SHALL be preferred over the variant
Company where possible, to save encoding space.
Identifiers are defined by the carrier. When decoding this variant SHALL be dereferenced to
the contextually relevant CompanyCode. When encoding, this variant SHALL be preferred over the variant
company where possible, to save encoding space. If there are multiple possible contextually relevant
carriers, this variant SHALL NOT be used, as its meaning is then ambiguous.
Identifiers are defined by entity responsible for the relevant 'Concerned Area'. When decoding this variant SHALL be dereferenced to the contextually relevant NUTSArea. If there are multiple possible contextually relevant concerned areas, this variant SHALL NOT be used, as its meaning is then ambiguous.
This variant SHALL NOT be used for an identifier before it is registered with [insert registration authority]. The registration authority will make a determination on whether the suggested dataset can accurately be considered a regional dataset, covering all possible identifiers in a given context for multi-modality in that area.
Identifiers are defined a national authority for a country. This field contains the ISO 3166-1 numeric code of that country.
This variant SHALL NOT be used for an identifier before it is registered with [insert registration authority]. The registration authority will make a determination on whether the suggested dataset can accurately be considered a national dataset, covering all possible identifiers in a given context for multi-modality in that country.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
999
Identifiers are defined by the given company.
This field is used in case of multiple datasets being maintained by the same entity for the same purpose, to differentiate between them. Examples could include BeispielBahn having two different possible identifiers for a station.
Note: this field is not used to differentiate between different datasets used by the same entity for different purposes. That is, the dataset of, e.g., BeispielBahn for areas and for stations may both be given version 0. It is evident from the context in which this structure is used, to which dataset the identifier refers.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
255
This field, when unset, defaults to the following value:
0
This object class has the following fields:
This field accepts any value of the following type:
CodeTableThis field must be unique within an object set.
This assignment is parameterised, accepting the following parameters:
This sequence contains the following fields:
Denotes to which dataset the identifier references.
This type is constrained in the following way:
The value must come from the &table column of the object set: Parameter TableSet
The identifier, as defined by the dataset referenced in codeTable.
This data structure is used throughout this standard when referring to the various organisations or authorities responsible for the various aspects of ticketing and carriage of passengers. In Transmodel terms it identifies a TRANSPORT ORGANIZATION (EN 12896-1:2016 § 5.6.8).
The value of this choice may be one of the following:
For companies within the EU this field SHALL be their ERA assigned Organisation Code, as available from teleref.era.europa.eu. For others this field SHALL be their UIC assigned RICS, as available from uic.org/support-activities/it/rics.
This type is constrained in the following way:
All the following must be true:
The length of the value must exactly:
4
AND
The characters in the string value must satisfy the following constraint:
Any of the following can be true:
The value must be greater than or equal to:
A
The value must be less than or equal to:
Z
OR
The value must be greater than or equal to:
0
The value must be less than or equal to:
9
This variant is to be used when a company does not have an ERA Organisation Code nor a RICS. It SHALL NOT be used when a company has an ERA Org Code or RICS assigned to it, except where the situation requires identifying the company within the context of a local coding system.
This sequence contains the following fields:
The company identifier format is constructed according to one of the following options:
+ (U+002B, PLUS SIGN), concatenated with a 2-character uppercase ISO-3166 country
code, concatenated with a string chosen by the national standards body of that country._ (U+005F, LOW LINE), concatenated with a 4-character ERA Organisation Code or RICS,
concatenated with a string chosen by that company.* (U+002A, ASTERISK), concatenated with privately chosen string. Note: this variant has no guarantees
of avoiding clashes in assignment, and SHOULD NOT be used unless no other option is available.
If an organisation has a ERA Organisation Code or a RICS, this variant SHALL NOT be used.The 1st and 2nd variant SHOULD be registered before their first use. The 4th variant SHALL be registered before its first use. Registrations SHALL be made with [insert registration authority].
This type is constrained in the following way:
All the following must be true:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
AND
Any value, except any satisfying the following:
Any of the following can be true:
The value must be exactly:
!I
OR
The value must be exactly:
!C
OR
The value must be exactly:
!P
This type is constrained in the following way:
The value must come from the &id column of the object set: CompanyCodeFormats
The meaning of this field is defined by value of format.
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
This object class has the following fields:
This field accepts any value of the following type:
VisibleStringThis type is constrained in the following way:
All the following must be true:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
AND
Any value, except any satisfying the following:
Any of the following can be true:
The value must be exactly:
!I
OR
The value must be exactly:
!C
OR
The value must be exactly:
!P
This field must be unique within an object set.
When a company does not have an ERA Organisation Code, an entry from this list SHALL be used to signify which alternative dataset is being used to identify the company.
The entries in this list are managed by [insert registration authority].
This object set has the following members:
| &id |
|---|
+DEVDV
|
+GBNOC
|
+CHSBOID
|
| Other members may be added at runtime. |
This sequence contains the following fields:
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
32
This data structure is used throughout this standard for the encoding of text which is intended to be displayed to a human being. This standard utilises the Unicode character set for such purposes.
Implementations of this standard SHALL be compliant to DIN 91379, with regards to processing text in this structure. That is, they are able to handle (store, transfer, recall, and represent) all characters as specified in DIN 91379 without error.
This sequence contains the following fields:
The textual data, encoded according to the Standard Compression Scheme for Unicode (SCSU). All Unicode text, before being fed into the SCSU compressor, SHALL be in Normalisation Form C.
For encoders than only ever output US-ASCII and ISO 8859-1 (Latin-1) between U+0020 and U+00FF, no special
handling is required to generate SCSU data, the Latin-1 encoding is already valid SCSU.
All decoders MUST be able to handle the full SCSU specification when reading and parsing data.
If you are unsure which implementation to use, the International Components for Unicode is the recommended implementation of SCSU, although it is by no means required.
The IANA language subtag of the text.
This type is constrained in the following way:
All the following must be true:
The length of the value must exactly:
2
AND
The characters in the string value must satisfy the following constraint:
The value must be greater than or equal to:
a
The value must be less than or equal to:
z
This data structure is used fo the encoding of a person's name. The encoding considerations and rules of UnicodeText apply equally to this structure.
When comparing names with identity documents, or when a Latinized representation of a name is required, the system SHALL transliterate according to ICAO 9303 Part 3, specifically sections 4.6 and 6. The text stored in the ticket SHOULD be in its original script, with transliteration performed by the reading device. The reading device SHOULD show both the original script, and the Latinized form.
The language field, if present, SHALL be used to select to correct Latinization of Cyrillic characters.
The relevant languages for special considerations in ICAO 9303 Latinization are:
be: Belarusianbg: Bulgarianuk: Ukrainianmk: Macedoniansr: SerbianThe language field MAY also be used to influence other transliterations, e.g. the different handling of diaereses by language.
All 3 name parts are encoded with SCSU compression (as per UnicodeText). The language tag applies to all 3 name parts. That is, the name parts are to be construed as 3 UnicodeText SEQUENCEs with the same language tag set.
This sequence contains the following fields:
The forename(s) of the person.
The middle name(s) of the person, if applicable.
The surname(s) of the person.
In the case of a mononym, this field SHALL contain the name, and the forename and middleName fields
SHALL be unset.
The IANA language subtag of the names' language.
This type is constrained in the following way:
All the following must be true:
The length of the value must exactly:
2
AND
The characters in the string value must satisfy the following constraint:
The value must be greater than or equal to:
a
The value must be less than or equal to:
z
This data structure is used to identify a station, stop, or other such boarding/alighting point. In Transmodel terms, it identifies a STOP PLACE (EN 12896-2:2016 § 5.4.3).
This sequence contains the following fields:
Contains the identifier used for the station.
The value of this choice may be one of the following:
Identification of the station by its ERA assigned Primary Location Code, as per teleref.era.europa.eu. This variant SHALL be used when a station has such a code assigned.
Note: a PLC is not equivalent to a UIC station ID, an IBNR (Internationale/Interne Bahnhofsnummer), nor a MERITS reservation code. Although there may be some equivalence between these numbers in certain countries, these are identifiers for separate systems and are not interchangeable.
This sequence contains the following fields:
The ISO 3166-1 numeric code of the country of the PLC.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
999
The national part of the PLC.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
99999
If a station does not have an ERA Primary Location Code assigned, this variant is to be used. This variant SHALL NOT be used when a station has as assigned ERA Primary Location Code.
This type is concretely parameterised with the following:
This field MAY be used to provide a human-readable name for the station, to assist in cases where the
device reading a ticket does not have the appropriate dataset to deference the identifier encoded in station.
This field SHALL NOT be processed automatically, including, but not limited to, string matching the provided station to a dataset. It SHALL only be used for display to a human being.
When a Station does not have an ERA Primary Location Code, an entry from this list SHALL be used to signify
which alternative dataset is being used to identify the station.
The entries in this list are managed by [insert registration authority].
This object set has the following members:
| &table |
|---|
SEQUENCE
|
SEQUENCE
|
SEQUENCE
|
SEQUENCE
|
| Other members may be added at runtime. |
This sequence contains the following fields:
The value of this choice may be one of the following:
This data structure is used to identify a service line, for which many services may run in a day. In Transmodel terms, it identifies a LINE (EN 12896-2:2016 § 5.3.7.4).
The value of this choice may be one of the following:
An end-user-visible (i.e. published in timetables) identifier for the line.
This sequence contains the following fields:
The identifier of the line; e.g. "RE1", "S1", etc.
This type is constrained in the following way:
The characters in the string value must satisfy the following constraint:
Any of the following can be true:
The value must be greater than or equal to:
A
The value must be less than or equal to:
Z
OR
The value must be greater than or equal to:
0
The value must be less than or equal to:
9
The carrier that operates the line.
A non-end-user-visible identifier for the line.
This type is concretely parameterised with the following:
When a LineId is being identified with a non-end-user-visible identifier, an entry from this list SHALL be used to signify which dataset is being used to identify the line.
The entries in this list are managed by [insert registration authority].
This object set has the following members:
| &table |
|---|
SEQUENCE
|
SEQUENCE
|
| Other members may be added at runtime. |
This data structure is used to identify a singular transport service, ideally unique within a day. In Transmodel terms, it identifies a SERVICE JOURNEY (EN 12896-3:2016 § 5.3.2).
The value of this choice may be one of the following:
An end-user-visible (i.e. published in timetables) identifier for the service.
This sequence contains the following fields:
The identifier of the service; e.g. "ICE107", etc.
This type is constrained in the following way:
The characters in the string value must satisfy the following constraint:
Any of the following can be true:
The value must be greater than or equal to:
A
The value must be less than or equal to:
Z
OR
The value must be greater than or equal to:
0
The value must be less than or equal to:
9
The carrier that operates the service.
This type is concretely parameterised with the following:
When a TransportId is being identified with a non-end-user-visible identifier, an entry from this list SHALL be used to signify which dataset is being used to identify the service.
The entries in this list are managed by [insert registration authority].
This object set has the following members:
| &table |
|---|
SEQUENCE
|
SEQUENCE
|
SEQUENCE
|
| Other members may be added at runtime. |
This structure identifies a geographic area defined under the Nomenclature of Territorial Units for Statistics (Regulation EC 1059/2003), or a compatible system for those countries outside of the NUTS system.
Divisions all the way down to the Local Administrative Unit are permitted.
LAUs must be appended to their NUTS3 code, e.g. 270942 for Emmendingen, Stadt is coded with the subdivision 133270942.
Functional Administrative Unit codes are not permitted.
NUTS codes are only defined for members of the EU, the EFTA, and EU candidate countries. For those countries outside the NUTS system:
subdivision field.This sequence contains the following fields:
The ISO 3166-1 numeric code of the country of the area.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
999
The NUTS code, without the country-code prefix. If this field is unset, the structure refers to the entire country.
This type is constrained in the following way:
The characters in the string value must satisfy the following constraint:
Any of the following can be true:
The value must be greater than or equal to:
A
The value must be less than or equal to:
Z
OR
The value must be greater than or equal to:
1
The value must be less than or equal to:
9
This structure identifies one or more areas of geographic validity, e.g. fare zones.
The value of this choice may be one of the following:
A list of European NUTS codes, or compatible.
This variant SHOULD be used over the generic variant where possible.
A list of area identifiers defined in terms of an identified code list.
The same rules of equivalence under equality comparisons that apply to GenericId apply here as well,
except to the idBit variant.
Lists which contain the same values but in a different order are also equivalent.
This type is concretely parameterised with the following:
The value of this choice may be one of the following:
To be used for numeric IDs.
To be used for alphanumeric IDs.
To be used for binary IDs.
An encoding in which each area is encoded as one bit.
That is, when a bit is set the area/zone is included in the AreaSet,
when it is not set the area/zone is excluded from the AreaSet.
For example, where bit n (with bit 0 being right-most bit) encodes zone n+1, the value
'10101110010'B encodes zones 2, 5, 6, 7, 9 and 11.
When an AreaSet is being identified with a non-NUTS identifier, an entry from this list SHALL be used to signify which dataset is being used to identify the area.
The entries in this list are managed by [insert registration authority].
This object set has the following members:
| &table |
|---|
SEQUENCE
|
| Other members may be added at runtime. |
This data structure is used to locate seats/places within a coach/carriage. It is used, for example, when encoding a seat reservation barcode. The data SHALL be construed according to ERA TEL TSI B.5.
This sequence contains the following fields:
A human readable number/letter/identifier of the coach/carriage within one transport service.
Individual places within the above coach.
This field MAY be used to provide more details about the seats/places, in accordance with ERA TEL TSI B.5.
This field MAY contain a human-readable description of the place, if it cannot be represented using any of the other above fields.
This data structure identifies an individual seat/place within a single coach/carriage.
The value of this choice may be one of the following:
This variant SHALL be used when the seat/place identifier is a number.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
999
This variant SHALL be used when the seat/place identifier is not a number.
This data structure provides additional details about a seat/place/compartment, according to ERA TEL TSI B.5.
This sequence contains the following fields:
This field SHALL contain a value per ERA TEL TSI Code List B.5.51.1.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
This field SHALL contain a value per ERA TEL TSI Code List B.5.51.2.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
This field SHALL contain a value per ERA TEL TSI Code List B.5.51.3.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
99
This field MAY contain a human-readable description of any details about the seat/place that can't be represented with the above fields.
This data structure is used to represent points on the globe. It SHALL contain a latitude and longitude as measurements compatible with the World Geodetic System 1984, as used by GPS navigation satellites.
This sequence contains the following fields:
The exact point being referenced if no accuracy is given, or the centre of the possible circle of positions if
accuracy is given.
If known, the accuracy of the measurement given in position.
If the degrees of accuracy is more than 0.1 degrees, this value SHALL not be provided.
This enumeration is used to describe the accuracy of a geographic position measurement, in terms of variance range from the given centre coördinate.
To convert between meters of accuracy and degrees of accuracy, an implementation SHALL:
M = cos(latitude * π / 180) * 40075016.7 / 360.A = meters of accuracy / M.The value of this enumeration may have one of the following values:
Value:
0
The value A is less than or equal to 0.0001 degrees.
Value:
1
The value A is less than or equal to 0.001 degrees.
Value:
2
The value A is less than or equal to 0.01 degrees.
Value:
3
The value A is less than or equal to 0.1 degrees.
This data structure describes an exact point on the earth's surface.
Implementations SHALL take into account the useful number of significant places (e.g. based upon the measurement accuracy) in a coördinate, and SHALL select the smallest variant suitable (i.e. least number of decimal places represented), to provide an encoding of the position in as few bits as possible.
The value of this choice may be one of the following:
This variant is used to represent coördinates down to the 4th decimal place (0.0001 degrees).
This sequence contains the following fields:
This field SHALL be populated with the degrees of longitude, multiplied by 10,000.
This type is constrained in the following way:
The value must be greater than or equal to:
-1800000
The value must be less than or equal to:
1800000
This field SHALL be populated with the degrees of latitude, multiplied by 10,000.
This type is constrained in the following way:
The value must be greater than or equal to:
-900000
The value must be less than or equal to:
900000
This variant is used to represent coördinates down to the 3rd decimal place (0.001 degrees).
This sequence contains the following fields:
This field SHALL be populated with the degrees of longitude, multiplied by 1000.
This type is constrained in the following way:
The value must be greater than or equal to:
-180000
The value must be less than or equal to:
180000
This field SHALL be populated with the degrees of latitude, multiplied by 1000.
This type is constrained in the following way:
The value must be greater than or equal to:
-90000
The value must be less than or equal to:
90000
This variant is used to represent coördinates down to the 2nd decimal place (0.01 degrees).
This sequence contains the following fields:
This field SHALL be populated with the degrees of longitude, multiplied by 100.
This type is constrained in the following way:
The value must be greater than or equal to:
-18000
The value must be less than or equal to:
18000
This field SHALL be populated with the degrees of latitude, multiplied by 100.
This type is constrained in the following way:
The value must be greater than or equal to:
-9000
The value must be less than or equal to:
9000
This variant is used to represent coördinates down to the 1st decimal place (0.1 degrees).
This sequence contains the following fields:
This field SHALL be populated with the degrees of longitude, multiplied by 10.
This type is constrained in the following way:
The value must be greater than or equal to:
-1800
The value must be less than or equal to:
1800
This field SHALL be populated with the degrees of latitude, multiplied by 10.
This type is constrained in the following way:
The value must be greater than or equal to:
-900
The value must be less than or equal to:
900
This data structure is used to represent a timestamp, expressed in UTC. Implementations SHALL convert any local times to UTC before encoding them into this structure.
This sequence contains the following fields:
The year of the timestamp.
This type is constrained in the following way:
The value must be greater than or equal to:
2026
The value must be less than or equal to:
2281
The number of the day in the above year, where the 1st of January is day number 1.
This type is constrained in the following way:
The value must be greater than or equal to:
1
The value must be less than or equal to:
366
The number of minutes into the above day, where 0 minutes is 00:00 and 1439 minutes is 23:59.
This type is constrained in the following way:
The value must be greater than or equal to:
0
The value must be less than or equal to:
1439
This enumeration is used to describe the variety of a shared vehicle. Its values are taken from NeTEx's
PersonalVehicleCategory (CEN/TS 16614-5:2022 § 10.1.4.3.4.2).
The value of this enumeration may have one of the following values:
Value:
0
Scooter - small wheeled low mobile platform.
Value:
1
Bicycle.
Value:
2
Tricycle.
Value:
3
Tandem bicycle.
Value:
4
Moped (Small motorbike).
Value:
5
Motorcycle.
Value:
6
Motorcycle.
Value:
7
Car of any size.
Value:
8
Extremely small vehicle.
Value:
9
Very small vehicle.
Value:
10
Small vehicle.
Value:
11
Compact vehicle.
Value:
12
Large vehicle.
Value:
13
Minivan.
Value:
14
Large people transporter / minibus.
Value:
15
Snowmobile.
Value:
16
Other category.
This enumeration is used to describe the propulsion method of a shared vehicle. Its values are taken from NeTEx's PropulsionType (CEN/TS 16614-5:2022 § 10.1.4.3.2.2).
The value of this enumeration may have one of the following values:
Value:
0
Internal combustion of any sort.
Value:
1
Electric/Combustion Hybrid.
Value:
2
Human powered (pedal, scoot etc).
Value:
3
Human power with electric assistance.
Value:
4
Other power.
This enumeration is used to describe the return constraints of a shared Vehicle. Its values are taken from the General Bikeshare Feed Specification version 3.0.
The value of this enumeration may have one of the following values:
Value:
0
The vehicle can be returned anywhere permitted within the service area.
Value:
1
The vehicle has to be returned to the same station from which it was initially rented.
Value:
2
The vehicle has to be returned to any station within the service area.
Value:
3
The vehicle can be returned to any station, or anywhere else permitted within the service area.
This class defines data element formats for use in extensible data containers used throughout this standard.
Each object of this class identifies a data element format and specifies the ASN.1 type used to represent its contents, the encoding rules used to encode those contents, and the type used to express constraints on its values in certificates.
Data element formats are identified by their id. This permits additional data element formats to be defined
without modifying the structures in which they are carried.
This object class has the following fields:
The data element identifier format is constructed according to one of the following options:
+ (U+002B, PLUS SIGN), concatenated with a 2-character uppercase ISO-3166 country
code, concatenated with a string chosen by the national standards body of that country._ (U+005F, LOW LINE), concatenated with a 4-character ERA Organisation Code or RICS,
concatenated with a string chosen by that company.!I (U+0021, EXCLAMATION MARK, U+0049, Latin Capital Letter I),
concatenated with a string chosen by the issuer. This variant SHALL be construed as equivalent to the
corresponding 2nd variant. It SHALL be used where possible to avoid repetition of the issuer's company code.
It SHALL NOT be used where its meaning could be ambiguous.!C (U+0021, EXCLAMATION MARK, U+0043, Latin Capital Letter C),
concatenated with a string chosen by the carrier. This variant SHALL be construed as equivalent to the
corresponding 2nd variant. It SHALL be used where possible to avoid repetition of the carriers's company
code. It SHALL NOT be used where its meaning could be ambiguous, for example when multiple carriers are involved.!P (U+0021, EXCLAMATION MARK, U+0050, Latin Capital Letter P),
concatenated with a string chosen by the product owner. This variant SHALL be construed as equivalent to the
corresponding 2nd variant. It SHALL be used where possible to avoid repetition of the product owners's
company code. It SHALL NOT be used where its meaning could be ambiguous.* (U+002A, ASTERISK), concatenated with privately chosen string. Note: this variant has no guarantees
of avoiding clashes in assignment, and SHOULD NOT be used unless no other option is available.
If an organisation has a ERA Organisation Code or a RICS, this variant SHALL NOT be used.The 1st and 2nd variant SHOULD be registered before their first use. The 4th, 5th, and 6th variants cannot be registered, as they are equivalent to the corresponding 2nd variant. The 8th variant SHALL be registered before its first use. Registrations SHALL be made with [insert registration authority].
This field accepts any value of the following type:
VisibleStringThis type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
This field must be unique within an object set.
The data structure that describes the contents of this data element.
This field accepts any concrete type.
An object identifier specifying which of the ASN.1 encoding rules used to encode Type into an OCTET STRING
for the placing of this data element into a barcode.
This field accepts any value of the following type:
OBJECT IDENTIFIERA data structure to be used within a certificate to place constraints on the possible values of a data
element of this variety. It SHALL be encoded into an OCTET STRING for inclusion in the certificate as
specified by encoding object identifier. It MAY be the null type, if no constraints ever need to be placed
on the data element.
This field accepts any concrete type.
This Object Identifier has been assigned by ITU-T X.691 to identify the Canonical Aligned Packed Encoding Rules. This SHALL be used within a DATA-ELEMENT object to signify that it is encoded with the CAPER.
This Object Identifier has been assigned by ITU-T X.691 to identify the Canonical Unaligned Packed Encoding Rules. This SHALL be used within a DATA-ELEMENT object to signify that it is encoded with the CUPER.
This Object Identifier SHALL be used within a DATA-ELEMENT object to signify that a data element contains raw bytes.
It is only permitted when the data element is of the OCTET STRING type.
This Object Identifier SHALL be used within a DATA-ELEMENT object to signify that a data element contains no data. It is only permitted when the data element is of the null type.
Generic data container.
This assignment is parameterised, accepting the following parameters:
Set of DATA-ELEMENT objects that are permitted as contents. This set SHOULD be extensible.
This sequence contains the following fields:
This field signifies the criticality of this data element.
If the data format is not recognised, or can't be processed, and it is marked critical, the ticket SHALL be treated as invalid; otherwise, an implementation SHALL ignore extensions not understood.
This field identifies which type of data element is encoded.
Its value is used to identify which type is contained within the value field, and what encoding has been used
for it.
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
This type is constrained in the following way:
The value must come from the &id column of the object set: Parameter ElementSet
This field contains the type identified by the format field, encoded according to the encoding given in the
corresponding DATA-ELEMENT object.
This type is constrained in the following way:
The value must be an encoding of the following type:
ANYThis type is constrained in the following way:
The value must come from the &Type column of the object set:
Parameter
ElementSet
The row is selected by the value of the fields:
format
This assignment is parameterised, accepting the following parameters:
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
64
This type is concretely parameterised with the following:
This assignment is parameterised, accepting the following parameters:
This sequence contains the following fields:
This type is constrained in the following way:
The length of the value must be greater than or equal to:
1
The length of the value must be less than or equal to:
8
This type is constrained in the following way:
The value must come from the &id column of the object set: Parameter ElementSet
This type is constrained in the following way:
The value must be an encoding of the following type:
ANYThis type is constrained in the following way:
The value must come from the &Constraints column of the object set:
Parameter
ElementSet
The row is selected by the value of the fields:
format
A generic container for the conveyance of Digital Signature Scheme signatures, i.e. ECDSA.
This assignment is parameterised, accepting the following parameters:
The length, in bytes, of each of r and s. That is, half the total signature length.
This sequence contains the following fields:
The output r of the DSS signature process.
This type is constrained in the following way:
The length of the value must exactly: Parameter len
The output s of the DSS signature process.
This type is constrained in the following way:
The length of the value must exactly: Parameter len
This assignment is parameterised, accepting the following parameters:
The length, in bytes, required to represent the X coördinate on a curve.
This sequence contains the following fields:
An indicator of the Y coördinate of the elliptic curve point being odd or even.
This field SHALL be FALSE if the first byte of the SEC 1 compressed encoding of this point would be 02h,
and SHALL be TRUE if the first byte of the SEC 1 compressed encoding of this point would be 03h.
The X coördinate of the elliptic curve point.
This type is constrained in the following way:
The length of the value must exactly: Parameter len