Depository DEP
Depository: takes envelopes and bags into a deposit bin.
This specification describes the functionality of the services provided by the Depository (DEP) services under XFS, by defining the service-specific commands that can be issued, using the WFSGetInfo, WFSAsyncGetInfo, WFSExecute and WFSAsyncExecute functions.
Across the editions
Each edition of XFS 3.x has one part per device class. The table lists the editions that have a part for Depository and, for each, how many queries, commands and events the part defines. A dash means the edition has no part for this class.
| Edition | CWA | Date | Queries | Commands | Events |
|---|---|---|---|---|---|
| 2.00 | CWA 13449 | December 1998 | 2 | 5 | 8 |
| 3.00 | CWA 14050 | November 2000 | 2 | 6 | 10 |
| 3.10 | CWA 15748 | July 2008 | 2 | 8 | 13 |
| 3.20 | CWA 16374 | December 2011 | 2 | 8 | 13 |
| 3.30 | CWA 16926 | August 2015 | 2 | 9 | 13 |
| 3.40 | CWA 16926 | February 2020 | 2 | 9 | 13 |
| 3.50 | CWA 16926 | December 2022 | 2 | 9 | 13 |
The class-by-edition matrix shows every class side by side.
The 3.50 document
The part is published as CWA 16926-67. Like every XFS 3.x part it opens with chapters that describe the device and how an application uses it, then lists each query, command and event with its data, and closes with background chapters and the C header.
Before the messages
- European Foreword p. 3
- 1 Introduction p. 7
- 2 Depository Unit p. 8
- 3 References p. 9
The messages
2 queries, 9 commands and 13 events, 24 messages in all, each with its input and output data and its error codes.
Chapter numbers and page numbers are those of the document. CEN publishes the documents free of charge; see Sources.
How to read the numbers
In XFS 3.x an application asks a device about itself with a query (WFS_INF_… – status, capabilities, the forms a printer knows), makes it do something with a command (WFS_CMD_… – print, dispense, read a card), and learns about things that happen on their own from an event (a card taken, a door opened, a threshold reached). The counts above are taken from each document's message tables, so they show how the class grew from edition to edition. A count that does not change does not mean the messages did not: fields are added and meanings refined within a message, and that is not counted here.
Next: The device classes