Skip to content

Commit

Permalink
move compliance elements
Browse files Browse the repository at this point in the history
  • Loading branch information
pterr committed Nov 6, 2024
1 parent aacb123 commit 021c6a6
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 9 deletions.
9 changes: 8 additions & 1 deletion content/compliance/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,11 @@
title: Terminal Compliance
weight: 10
---
Coming soon

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.
8 changes: 0 additions & 8 deletions content/home/hero.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.


<br><br>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.

0 comments on commit 021c6a6

Please sign in to comment.