In SDD we used what is here called the "tagging approach", i.e. for descriptive concepts and characters we use <br><br><Text ref="<a href="http://some.resource.org/123" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
some.resource.org/123</a>"><Content>Free form text</Content></Text><br><br>In SDD, all element/attribute names refer to classes/attributes in UML
or Java, whereas the xml values are corresponding values. Expressing concepts and characters as classes was considered impractical if the aim is generic software (classes are creatable at runtime, but at a price) because the number of characters is often very large.
<br><br>My experience shows that the number of character in identification sets varies between 50 and over 1000. Some studies in manual data integration (in LIAS) convinced me that the number of "integratable" characters is often less than imagined. A similar case study may also be the FRIDA data sets, which limit the number of common characters (common to all plant families) to 200, and from thereon use separate characters for each family.
<br><br>Clearly, when limiting the approach to just "very high level concepts", both class and value approaches are possible. The benefit of the SPM 0.2 approach is that it does enable reasoning (as well as may simplify tapir usage). However, as presented in Bratislava, I am doubtful that this limit holds. In my experience the limit between free form text and categorical data tends be diffuse rather than sharp and my intuition is that the SPM mechanism, being extensible, will be extended.
<br><br>I would like to note that the current TAG strategy is to provide both RDF and xml schema. The schema approach to SPM, however, seems to be more and more undesirable as the number of descriptive concepts grows. <br>
<br>I have a question for TAPIR:<br><br>Does TAPIR find it easier to search elements having specific attribute values than elements having child elements with specific value:<br><br><hasInformation>
<br> <InfoItem category="<span style="text-decoration: underline;">voc.x</span><a href="http://some.resource.org/123" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">.org/DescriptiveConcepts/Size
</a>">
<br> <....>
<br> </InfoItem>
<br><br>I might be useful to know. Although RDF allows this for literals, it seems to require the rdf:resource="" step for categorical data, so this may or may not help.<br><br>----------<br><br>PS: SDD calls the concepts "characters" based on the tradition and character is clearly inappropriate. However, Category to me seems to express nothing other than the type of the value. All contextValue and Value in SPM in version
0.2 refer to categories. Can anyone suggest a better term? What is the opposite of "value"? <br><br>I can think of "Class" (value = instance), or - but perhaps too much limited to descriptions - "Feature" (also in GML). Anything else?
<br><br>Gregor<br><br>-----------------------------------------------------<br>Gregor Hagedorn (<a href="mailto:G.M.Hagedorn@gmail.com">G.M.Hagedorn@gmail.com</a>)<br>Institute for Plant Virology, Microbiology, and Biosafety
<br>Federal Research Center for Agriculture and Forestry (BBA)<br>Königin-Luise-Str. 19 Tel: +49-30-8304-2220<br>14195 Berlin, Germany Fax: +49-30-8304-2203