From 021c6a6afb392709e06b2e8ace3e74b03da2cab1 Mon Sep 17 00:00:00 2001 From: Pierre Terree Date: Wed, 6 Nov 2024 13:48:05 +0400 Subject: [PATCH] move compliance elements --- content/compliance/_index.md | 9 ++++++++- content/home/hero.md | 8 -------- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/content/compliance/_index.md b/content/compliance/_index.md index d0fe99b..da753d4 100644 --- a/content/compliance/_index.md +++ b/content/compliance/_index.md @@ -2,4 +2,11 @@ title: Terminal Compliance weight: 10 --- -Coming soon \ No newline at end of file + +To ensure the proper working and interoperability of ticketing terminal solutions, [CNA](https://calypsonet.org/) has also defined [rules that shall be followed by terminal solutions](https://calypsonet.org/calypso-for-terminals/#section-how-to-implement-calypso-in-a-ticketing-terminal) for different software layers. From the lowest to the highest level: +- the [Reader Layer Requirements](https://calypsonet.org/reader-layer-requirements-200422/), +- the [Calypso Layer Requirements](https://calypsonet.org/calypso-layer-requirements-200423/), +- and the [Ticketing Layer Requirements](https://calypsonet.org/ticketing-layer-requirements-200430/). + +The layout of the ticketing terminal APIs matches the architecture targeted by the ticketing terminal requirements. +It should therefore be possible in the future to certify the compliance with the terminal requirements for ticketing terminal solutions based on these APIs. \ No newline at end of file diff --git a/content/home/hero.md b/content/home/hero.md index e678ad3..a1aa188 100644 --- a/content/home/hero.md +++ b/content/home/hero.md @@ -31,11 +31,3 @@ First solutions translating these interface definitions into programming languag - [**Card**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-card-api/) and **[Legacy SAM](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-legacysam-api/) API**s to perform secure transactions with Calypso cards or with Calypso security modules such as SAM-S1 or SAM-C1. - [**Symmetric Crypto**](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-symmetric-crypto-api/) and **[Asymmetric Crypto](https://terminal-api.calypsonet.org/specifications/calypso-layer/calypso-asymmetric-crypto-api/) API**s to interface Calypso SAM or Calypso PKI processing libraries. - -

To ensure the proper working and interoperability of ticketing terminal solutions, [CNA](https://calypsonet.org/) has also defined [rules that shall be followed by terminal solutions](https://calypsonet.org/calypso-for-terminals/#section-how-to-implement-calypso-in-a-ticketing-terminal) for different software layers. From the lowest to the highest level: -- the [Reader Layer Requirements](https://calypsonet.org/reader-layer-requirements-200422/), -- the [Calypso Layer Requirements](https://calypsonet.org/calypso-layer-requirements-200423/), -- and the [Ticketing Layer Requirements](https://calypsonet.org/ticketing-layer-requirements-200430/). - -The layout of the ticketing terminal APIs matches the architecture targeted by the ticketing terminal requirements. -It should therefore be possible in the future to certify the compliance with the terminal requirements for ticketing terminal solutions based on these APIs. \ No newline at end of file