-
Notifications
You must be signed in to change notification settings - Fork 2
/
DiscussionFor1dot1.txt,v
176 lines (148 loc) · 10 KB
/
DiscussionFor1dot1.txt,v
1
2
3
4
5
6
7
8
9
10
11
12
13
14
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
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
head 1.7;
access;
symbols;
locks; strict;
comment @# @;
1.7
date 2009.11.25.03.14.33; author GarryJolleyRogers; state Exp;
branches;
next 1.6;
1.6
date 2009.11.20.02.45.25; author LeeBelbin; state Exp;
branches;
next 1.5;
1.5
date 2008.04.30.12.00.31; author GregorHagedorn; state Exp;
branches;
next 1.4;
1.4
date 2008.04.30.09.08.24; author GregorHagedorn; state Exp;
branches;
next 1.3;
1.3
date 2008.04.28.16.31.55; author GregorHagedorn; state Exp;
branches;
next 1.2;
1.2
date 2007.08.28.10.42.52; author GregorHagedorn; state Exp;
branches;
next 1.1;
1.1
date 2007.03.22.19.47.20; author BobMorris; state Exp;
branches;
next ;
desc
@none
@
1.7
log
@none
@
text
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118873" format="1.1" version="1.7"}%
%META:TOPICPARENT{name="WebHome"}%
---++ Discussion of SDD V 1.1
Necessary changes that are already enacted in the SDD development trunk (of the subversion versioning system):
* Newer releases of Altova XML-Spy claim a problem with the xml:lang attribute directly on the dataset. Since the similar use of xml:lang on Notes, Labels, etc. is unproblematic (there added using an attributeGroup reference), the same method is now used on dataset itself. Consequences: Only technical consequences with validating parsers may be possible, no actual change to syntax of instance files is involved occurred.
* Using SDD for single-access identification keys is less well developed than the other areas and testing continues. Several errors where detected when implementing this for large datasets in the context of the KeytoNature.eu project.
* It was discovered that contrary to initial expectations, some styles of keys do point to specific leads within a couplet, including pointers to subkey or taxon leads. In the original release of SDD 1.1 these where separated from inner nodes (Lead elements) as "Result" elements. To support such keys a described above, the Result element now also requires an optional id attribute to be referable. However, as a result, the distinction between Lead and Result seems no longer warranted. The two functions are therefore combined in a single Lead element type. The type for <nop>StoredKeyLeaf will be removed starting with SDD 1.1 rev. 3.
* In addition, a special attribute "leadspecific" was added on Reticulation elements (pointers to other leads) to flag that a reticulation is specific to the lead, not the couplet.
* Erroneously, the SDD 1.1 version assumes that Identification key statements are short text, whereas in fact they are long text. This required additional changes, in the context of which the Statement element now directly contains the text (rather than Statement/Label) and MediaObject is a sibling of Statement (rather than Statement/MediaObject). The feature that in a "pictorial key" a lead may contain ONLY a media object reference (but no text statement) remains unchanged.
* We believe it is least disruptive to consider this a minor change, expressed in the revision number, since no major data sets for this SDD subtype are known yet. The coded descriptions are not affected by these changes.
* For Natural Language descriptions, the ability to link a text fragment to a "text character" (rather than only categorical/quantitative characters) has been added. The ability to express the language of marked text (through xml:lang attributes) remains unchanged but has been made more explicit in the schema to help schema-generated software tools.@
1.6
log
@none
@
text
@d1 3
a3 3
%META:TOPICINFO{author="LeeBelbin" date="1258685125" format="1.1" reprev="1.6" version="1.6"}%
%META:TOPICPARENT{name="BDI.SDD"}%
---++ Discussion of BDI.SDD V 1.1
d5 1
a5 1
Necessary changes that are already enacted in the BDI.SDD development trunk (of the subversion versioning system):
d9 2
a10 2
* Using BDI.SDD for single-access identification keys is less well developed than the other areas and testing continues. Several errors where detected when implementing this for large datasets in the context of the KeytoNature.eu project.
* It was discovered that contrary to initial expectations, some styles of keys do point to specific leads within a couplet, including pointers to subkey or taxon leads. In the original release of BDI.SDD 1.1 these where separated from inner nodes (Lead elements) as "Result" elements. To support such keys a described above, the Result element now also requires an optional id attribute to be referable. However, as a result, the distinction between Lead and Result seems no longer warranted. The two functions are therefore combined in a single Lead element type. The type for <nop>StoredKeyLeaf will be removed starting with BDI.SDD 1.1 rev. 3.
d12 2
a13 2
* Erroneously, the BDI.SDD 1.1 version assumes that Identification key statements are short text, whereas in fact they are long text. This required additional changes, in the context of which the Statement element now directly contains the text (rather than Statement/Label) and MediaObject is a sibling of Statement (rather than Statement/MediaObject). The feature that in a "pictorial key" a lead may contain ONLY a media object reference (but no text statement) remains unchanged.
* We believe it is least disruptive to consider this a minor change, expressed in the revision number, since no major data sets for this BDI.SDD subtype are known yet. The coded descriptions are not affected by these changes.
d15 1
a15 1
* For Natural Language descriptions, the ability to link a text fragment to a "text character" (rather than only categorical/quantitative characters) has been added. The ability to express the language of marked text (through xml:lang attributes) remains unchanged but has been made more explicit in the schema to help schema-generated software tools.
@
1.5
log
@none
@
text
@d1 3
a3 3
%META:TOPICINFO{author="GregorHagedorn" date="1209556831" format="1.1" reprev="1.5" version="1.5"}%
%META:TOPICPARENT{name="WebHome"}%
---++ Discussion of SDD V 1.1
d5 1
a5 1
Necessary changes that are already enacted in the SDD development trunk (of the subversion versioning system):
d9 2
a10 2
* Using SDD for single-access identification keys is less well developed than the other areas and testing continues. Several errors where detected when implementing this for large datasets in the context of the KeytoNature.eu project.
* It was discovered that contrary to initial expectations, some styles of keys do point to specific leads within a couplet, including pointers to subkey or taxon leads. In the original release of SDD 1.1 these where separated from inner nodes (Lead elements) as "Result" elements. To support such keys a described above, the Result element now also requires an optional id attribute to be referable. However, as a result, the distinction between Lead and Result seems no longer warranted. The two functions are therefore combined in a single Lead element type. The type for <nop>StoredKeyLeaf will be removed starting with SDD 1.1 rev. 3.
d12 2
a13 2
* Erroneously, the SDD 1.1 version assumes that Identification key statements are short text, whereas in fact they are long text. This required additional changes, in the context of which the Statement element now directly contains the text (rather than Statement/Label) and MediaObject is a sibling of Statement (rather than Statement/MediaObject). The feature that in a "pictorial key" a lead may contain ONLY a media object reference (but no text statement) remains unchanged.
* We believe it is least disruptive to consider this a minor change, expressed in the revision number, since no major data sets for this SDD subtype are known yet. The coded descriptions are not affected by these changes.
@
1.4
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1209546504" format="1.1" version="1.4"}%
d12 1
a12 1
* Erroneously, the SDD 1.1 version assumes that Identification key statements are short text, whereas in fact they are long text. This required additional changes, in the context of which the Statement element now directly contains the text.
d15 1
a15 1
* For Natural Language descriptions, the ability to link a text fragment to a "text character" (rather than only categorical/quantitative characters) has been added. The ability to express the language of marked text (through xml:lang attributes) remains unchanged but has been made more explicit in the schema to help schema-generated software tools.@
1.3
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1209400315" format="1.1" reprev="1.3" version="1.3"}%
d9 5
a13 1
* Using SDD for single-access identification keys is less well developed than the other areas and testing continues. In this context it was discovered that contrary to initial expectations, some styles of keys do point to specific leads within a couplet, including subkey or taxon leads. In the original release of SDD 1.1 these where separated from inner nodes (Lead elements) as Result elements. This requires the Result element now also having an optional id attribute to be referable, and a special attribute "leadspecific" on links to show that a reticulation is specific to the lead, not the couplet. However, as a result, the distinction between Lead and Result seems no longer warranted. The two functions are therefore combined in a single Lead element type. The type for <nop>StoredKeyLeaf will be removed starting with SDD 1.1 rev. 3. We believe it is least disruptive to consider this a minor change, since no major data sets for this SDD subtype are known yet.
d15 1
a15 1
* For Natural Language descriptions, the ability to link a text fragment to a "text character" (rather than only categorical/quantitative characters) has been added. The ability to express the language of marked text (through xml:lang attributes) remains unchanged but has been made more explicit in the schema to help schema-generated software tools.
@
1.2
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="GregorHagedorn" date="1188297772" format="1.1" version="1.2"}%
d8 4
@
1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BobMorris" date="1174592840" format="1.1" reprev="1.1" version="1.1"}%
d5 3
@