@@ -228,22 +228,22 @@ Here is the start of the relevant section from PS 3.5:
228
228
229
229
7.8.1 PRIVATE DATA ELEMENT TAGS
230
230
231
- It is possible that multiple implementors may define Private Elements with the
231
+ It is possible that multiple implementers may define Private Elements with the
232
232
same (odd) group number. To avoid conflicts, Private Elements shall be
233
233
assigned Private Data Element Tags according to the following rules.
234
234
235
235
a) Private Creator Data Elements numbered (gggg,0010-00FF) (gggg is odd) shall
236
236
be used to reserve a block of Elements with Group Number gggg for use by an
237
- individual implementor . The implementor shall insert an identification code
237
+ individual implementer . The implementer shall insert an identification code
238
238
in the first unused (unassigned) Element in this series to reserve a block of
239
239
Private Elements. The VR of the private identification code shall be LO (Long
240
240
String) and the VM shall be equal to 1.
241
241
242
242
b) Private Creator Data Element (gggg,0010), is a Type 1 Data Element that
243
- identifies the implementor reserving element (gggg,1000-10FF), Private Creator
244
- Data Element (gggg,0011) identifies the implementor reserving elements
243
+ identifies the implementer reserving element (gggg,1000-10FF), Private Creator
244
+ Data Element (gggg,0011) identifies the implementer reserving elements
245
245
(gggg,1100-11FF), and so on, until Private Creator Data Element (gggg,00FF)
246
- identifies the implementor reserving elements (gggg,FF00- FFFF).
246
+ identifies the implementer reserving elements (gggg,FF00- FFFF).
247
247
248
248
c) Encoders of Private Data Elements shall be able to dynamically assign
249
249
private data to any available (unreserved) block(s) within the Private group,
0 commit comments