Start development on 386BSD 0.0
[unix-history] / .ref-BSD-4_3_Net_2 / usr / src / contrib / isode / ftam / fadu.py
CommitLineData
53102063
C
1-- fadu.py - FTAM file-access-data-unit definitions
2-- lifted directly from ISO8571-2
3--
4-- Two kinds of changes to the ASN.1
5-- - more commentary-tags for POSY
6-- - Node-Name must be string-valued
7
8-- $Header: /f/osi/ftam/RCS/fadu.py,v 7.1 91/02/22 09:22:26 mrose Interim $
9--
10--
11-- $Log: fadu.py,v $
12-- Revision 7.1 91/02/22 09:22:26 mrose
13-- Interim 6.8
14--
15-- Revision 7.0 89/11/23 21:53:15 mrose
16-- Release 6.0
17--
18
19--
20-- NOTICE
21--
22-- Acquisition, use, and distribution of this module and related
23-- materials are subject to the restrictions of a license agreement.
24-- Consult the Preface in the User's Manual for the full terms of
25-- this agreement.
26--
27--
28
29
30--* ISO8571-FADU *-- FADU DEFINITIONS ::=
31
32%{
33#ifndef lint
34static char *rcsid = "$Header: /f/osi/ftam/RCS/fadu.py,v 7.1 91/02/22 09:22:26 mrose Interim $";
35#endif
36%}
37
38BEGIN
39
40Subtree ::=
41 SEQUENCE {
42 node
43 Node-Descriptor-Data-Element,
44
45 data[0]
46 IMPLICIT DU
47 OPTIONAL,
48 -- present if and only if a DU is connected to the node
49
50 children[1]
51 IMPLICIT Children
52 OPTIONAL
53 -- a leaf node is characterized by having no children
54 }
55
56Children ::=
57 SEQUENCE {
58 enter-subtree
59 Enter-Subtree-Data-Element,
60
61 subtree --* *--
62 SEQUENCE OF
63 Subtree,
64 -- subtrees must appear in their proper order according to
65 -- their proper ordering as children of their parent node
66
67 exit-subtree
68 Exit-Subtree-Data-Element
69 }
70
71DU ::=
72 SEQUENCE OF
73 --* ISO8571-CONTENTS *-- CONT.File-Contents-Data-Element
74
75Node-Descriptor-Data-Element ::=
76 [APPLICATION 0]
77 IMPLICIT SEQUENCE {
78 name
79 Node-Name
80 OPTIONAL,
81 -- present only if the root node of the subtree is a named node
82
83 arc-length[1]
84 IMPLICIT INTEGER
85 DEFAULT 1,
86 -- used to specify the length of the arc to the root node of
87 -- the subtree from its parent node
88
89 data-exists[2]
90 IMPLICIT BOOLEAN
91 DEFAULT TRUE
92 -- data-exists = TRUE indicates that a DU is connected to the
93 -- root node of the subtree
94 }
95
96Node-Name ::=
97--* CHOICE { *--
98--* ftam-coded *-- [0]
99 IMPLICIT GraphicString --* , *--
100 -- when ftam-coded is used, the Node-Name belongs to the same
101 -- abstract syntax as the structuring information. Node-Names
102 -- are then transferred in the presentatino context established
103 -- to support the FTAM FADU abstract syntax. This form of
104 -- Node-Name is only allowed when the content type file
105 -- attribute contains a document type name. To support this
106 -- alternative, at least the G0 character set registered in
107 -- character set register entry 2 shall be supported.
108
109--* user-coded *--
110--* EXTERNAL *--
111 -- the actual types allowed are found in the abstract syntax
112 -- for the files contents, as specified in the contents type
113 -- file attribute for the file
114--* } *--
115
116Enter-Subtree-Data-Element ::=
117 [APPLICATION 1]
118 IMPLICIT NULL
119
120Exit-Subtree-Data-Element ::=
121 [APPLICATION 2]
122 IMPLICIT NULL
123 -- the enter-subtree and exit-subtree data elements are used to bracket
124 -- the list of subtrees, which are children of the preceding node
125
126FADU ::=
127 Subtree
128
129Structuring-Data-Element ::=
130 CHOICE {
131 node-descriptor --* *--
132 Node-Descriptor-Data-Element,
133
134 enter-subtree --* *--
135 Enter-Subtree-Data-Element,
136
137 exit-subtree --* *--
138 Exit-Subtree-Data-Element
139 }
140
141-- Data-Element is defined to be a general data type whose values are
142--
143-- a) a value of the ASN.1 type Structuring-Data-Element in the abstract
144-- syntax "FTAM FADU"; or,
145--
146-- b) a value of the ASN.1 type ISO8571-CONTENTS.File-Contents-Data-Element
147-- in the abstract syntax derived from the contents type file attribute.
148
149END