<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Registries on ADCET</title><link>https://www.adcet.org/en/amc-en/registries/</link><description>Recent content in Registries on ADCET</description><generator>Hugo</generator><language>en-GB</language><atom:link href="https://www.adcet.org/en/amc-en/registries/index.xml" rel="self" type="application/rss+xml"/><item><title>Service areas</title><link>https://www.adcet.org/en/amc-en/registries/services-area/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.adcet.org/en/amc-en/registries/services-area/</guid><description>&lt;p&gt;This register contains the references of the services areas of all AMC applications.&lt;/p&gt;&#10;&lt;p&gt;Each reference must be unique and correspond to a set of keys. To guarantee this uniqueness, each AMC supplier must send an AMC reference request to the ADCET by email at &lt;a href="mailto:amc-register@adcet.org"&gt;amc-register@adcet.org&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;For the common AMC, ServiceScopeID value equals ‘E00’h.&lt;/p&gt;</description></item><item><title>AMC data issuers</title><link>https://www.adcet.org/en/amc-en/registries/amc-data-transmitters/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.adcet.org/en/amc-en/registries/amc-data-transmitters/</guid><description>&lt;h2 id="issuer-categories-and-references"&gt;Issuer categories and references&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Category&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Reference&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Values not allowed&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Territories without NAO&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;0XXX&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;0XFF&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Transport networks and territories with NAO&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;1NNN&lt;/code&gt; (NNN: organising authority number, standard NF P 99-502)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;1XFF&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Card issuers&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;E0XX&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;E0FF&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Integrators&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;E1XX&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;E1FF&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Tests&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;code&gt;FEF0&lt;/code&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;other &lt;code&gt;FXXX&lt;/code&gt; values&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;p&gt;References of the form &lt;code&gt;XXFF&lt;/code&gt; and &lt;code&gt;FFXX&lt;/code&gt; are never assigned.&lt;/p&gt;</description></item><item><title>Common AMC value ranges</title><link>https://www.adcet.org/en/amc-en/registries/common-amc-value-ranges/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.adcet.org/en/amc-en/registries/common-amc-value-ranges/</guid><description>&lt;p&gt;Uniqueness and non-correlation rule: the issuer of the predefined identifiers guarantees that each generated value is used only once for a given sector of activity, and that the identifier must not be able to be predicted from the mere knowledge of one or more other AMC identifiers.&lt;br&gt;&#10;For common AMC values (also recommended for specific AMC), the values generation rule is the following:&lt;br&gt;&#10;ADCET has a whole range of 4-byte values ​​(more than 4 billion possible values) that the issuer can subdivide as it wishes.&lt;/p&gt;</description></item><item><title>Common virtual AMC value ranges</title><link>https://www.adcet.org/en/amc-en/registries/range-of-values-for-common-virtual-amc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.adcet.org/en/amc-en/registries/range-of-values-for-common-virtual-amc/</guid><description>&lt;p&gt;Uniqueness and non-correlation rule: the issuer of the predefined identifiers guarantees that each generated value is used only once for a given sector of activity, and that the identifier must not be able to be predicted from the mere knowledge of one or more other AMC identifiers.&lt;br&gt;&#10;ADCET has a whole range of 4-byte values ​​(more than 4 billion possible values) that the issuer can subdivide as it wishes.&lt;/p&gt;&#10;&lt;p&gt;Value ranges are defined by the first and last value in the range and include all values ​​in the range.&lt;/p&gt;</description></item><item><title>Signatories of the common AMC usage agreement</title><link>https://www.adcet.org/en/amc-en/registries/accredited-organisations/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.adcet.org/en/amc-en/registries/accredited-organisations/</guid><description>&lt;p&gt;The AMC specification is made available to any entity in charge of transmitting or accepting media for multi-service applications, and in particular without this list being exhaustive: local authorities, transport operators, transmitters of portable media can be used in a multi-service context, card and terminal manufacturers, software publishers and service providers.&lt;/p&gt;&#10;&lt;p&gt;In addition to its security principles, the AMC is based on compliance by its partners with a number of management rules described in the application specifications. It is therefore useful that ADCET can ensure compliance with these rules, for the benefit of all.&lt;/p&gt;</description></item></channel></rss>