ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
New spreadsheet columns for documenting component deprecation
2
3
“Endorsed cardinality” (column “D”):
4
Used when signaling a cardinality change that would, if implemented in the schemas, cause backwards incompatibility (for example, moving from 0..1 to 1..1 or from 0..n to 0..1). The 2.5 schemas will maintain the old cardinality (column “C”) and users will be alerted that a new cardinality is planned for a future version, and endorsed to maintain compatibility with the cardinality in column “D”.
5
Also used when deprecating an entire BIE. Column “D” shall then have a cardinality of “0”, indicating that the BIE will be removed in a future release.
6
7
“Endorsed cardinality rationale” (column “E”):
8
When an entire BIE is deprecated, this column shall contain information useful for users migrating to alternative functionality, for example reasons for deprecating the BIE, indicating an alternative BIE, etc.
9
10
“Deprecated definition” (column “G”):
11
When updating a BIE definition, this column shall contain the previous definition. To be precise, the old definition shall be copied from column “F” to column “G” to preserve it, and the new definition shall then be written column “F”.
12
13
“Last changed” (column “Y”):
14
To document when a component has been changed from one UBL version to another. Ken will work on a script to populate the column with pre-2.5 changes.
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100