312 lines
11 KiB
Plaintext
312 lines
11 KiB
Plaintext
head 1.11;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.11
|
|
date 2009.11.25.03.14.32; author GarryJolleyRogers; state Exp;
|
|
branches;
|
|
next 1.10;
|
|
|
|
1.10
|
|
date 2009.11.20.02.45.24; author LeeBelbin; state Exp;
|
|
branches;
|
|
next 1.9;
|
|
|
|
1.9
|
|
date 2007.03.06.17.30.00; author TWikiGuest; state Exp;
|
|
branches;
|
|
next 1.8;
|
|
|
|
1.8
|
|
date 2005.01.06.16.43.44; author BobMorris; state Exp;
|
|
branches;
|
|
next 1.7;
|
|
|
|
1.7
|
|
date 2004.09.07.14.31.00; author JacobAsiedu; state Exp;
|
|
branches;
|
|
next 1.6;
|
|
|
|
1.6
|
|
date 2004.05.21.18.15.00; author GregorHagedorn; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2004.05.21.11.43.53; author BobMorris; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2004.05.21.09.00.40; author DonaldHobern; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2004.03.12.20.32.49; author JacobAsiedu; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2003.12.09.23.35.00; author BobMorris; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2003.12.03.00.33.00; author BobMorris; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.11
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118872" format="1.1" version="1.11"}%
|
|
%META:TOPICPARENT{name="BDI.SDD_"}%
|
|
---+!! %TOPIC%
|
|
|
|
* * [[%ATTACHURL%/sdd.zip][sdd.zip]]: BDI.SDD_ reference debugging tool
|
|
|
|
sddDebugRef is a tool by Main.JacobAsiedu to supply meaningful text to the debugref attributes in BDI.SDD_ instance documents. Normally, descriptions and other things in an instance document make references to objects defined in the Terminology section. Since these objects are typically identified by a numeric key, it is desirable to annotate the instance document references with text that helps you figure out what the target of the reference is about, and where it can be found. This XSLT application does that. You can also simply dump your instance document into http://efg.cs.umb.edu:8080/cocoon/SDDdebugref
|
|
|
|
-- Main.BobMorris - 03 Dec 2003
|
|
|
|
|
|
* [[%ATTACHURL%/sdd.zip][sdd.zip]]: $Id: sddRefDebug.xsl,v 1.6 2003/12/06 21:29:19 kas
|
|
|
|
Bug fixes
|
|
|
|
---
|
|
|
|
|
|
Attached is the latest version of the debugref tool that conforms BDI.SDD_ 1.0
|
|
|
|
--Main.JacobAsiedu
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.tar.gz][sddRefDebug.tar.gz]]: LINUX/UNIX users download
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.zip][sddRefDebug.zip]]: Windows users
|
|
|
|
* [[%ATTACHURL%/sddRefDebugDoc.txt][sddRefDebugDoc.txt]]: debugRef tool Help file
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.tar][sddRefDebug.tar]]: Linux/unix users
|
|
|
|
%META:FILEATTACHMENT{name="sdd.zip" attr="h" comment="$Id: sddRefDebug.xsl,v 1.6 2003/12/06 21:29:19 kas" date="1071012810" path="C:\cvsCheckout\sdd.zip" size="3330911" user="BobMorris" version="1.2"}%
|
|
%META:FILEATTACHMENT{name="sddRefDebug.tar.gz" attr="" comment="LINUX/UNIX users download" date="1094567169" path=" sddRefDebug.tar.gz" size="3824443" user="JacobAsiedu" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="sddRefDebug.zip" attr="" comment="Windows users" date="1094567245" path="sddRefDebug.zip" size="3834909" user="JacobAsiedu" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="sddRefDebugDoc.txt" attr="" comment="debugRef tool Help file" date="1094567318" path="sddRefDebugDoc.txt" size="9257" user="JacobAsiedu" version="1.1"}%
|
|
%META:FILEATTACHMENT{name="sddRefDebug.tar" attr="" comment="Linux/unix users" date="1094567396" path="sddRefDebug.tar" size="4853760" user="JacobAsiedu" version="1.1"}%
|
|
%META:TOPICMOVED{by="BobMorris" date="1105029764" from="SDD.ToolsForUseWithSDD" to="SDD.DebugRef"}%
|
|
@
|
|
|
|
|
|
1.10
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
a2 2
|
|
%META:TOPICINFO{author="LeeBelbin" date="1258685124" format="1.1" reprev="1.10" version="1.10"}%
|
|
%META:TOPICPARENT{name="BDI.SDD"}%
|
|
d5 1
|
|
a5 1
|
|
* * [[%ATTACHURL%/sdd.zip][sdd.zip]]: BDI.SDD reference debugging tool
|
|
d7 1
|
|
a7 1
|
|
sddDebugRef is a tool by Main.JacobAsiedu to supply meaningful text to the debugref attributes in BDI.SDD instance documents. Normally, descriptions and other things in an instance document make references to objects defined in the Terminology section. Since these objects are typically identified by a numeric key, it is desirable to annotate the instance document references with text that helps you figure out what the target of the reference is about, and where it can be found. This XSLT application does that. You can also simply dump your instance document into http://efg.cs.umb.edu:8080/cocoon/SDDdebugref
|
|
d19 1
|
|
a19 1
|
|
Attached is the latest version of the debugref tool that conforms BDI.SDD 1.0
|
|
@
|
|
|
|
|
|
1.9
|
|
log
|
|
@Added topic name via script
|
|
@
|
|
text
|
|
@d1 2
|
|
d5 1
|
|
a5 3
|
|
%META:TOPICINFO{author="BobMorris" date="1105029824" format="1.0" version="1.8"}%
|
|
%META:TOPICPARENT{name="WebHome"}%
|
|
* * [[%ATTACHURL%/sdd.zip][sdd.zip]]: SDD reference debugging tool
|
|
d7 1
|
|
a7 1
|
|
sddDebugRef is a tool by Main.JacobAsiedu to supply meaningful text to the debugref attributes in SDD instance documents. Normally, descriptions and other things in an instance document make references to objects defined in the Terminology section. Since these objects are typically identified by a numeric key, it is desirable to annotate the instance document references with text that helps you figure out what the target of the reference is about, and where it can be found. This XSLT application does that. You can also simply dump your instance document into http://efg.cs.umb.edu:8080/cocoon/SDDdebugref
|
|
d10 1
|
|
a10 1
|
|
|
|
d12 1
|
|
a12 1
|
|
* [[%ATTACHURL%/sdd.zip][sdd.zip]]: $Id: sddRefDebug.xsl,v 1.6 2003/12/06 21:29:19 kas
|
|
d14 1
|
|
a14 1
|
|
Bug fixes
|
|
d19 1
|
|
a19 1
|
|
Attached is the latest version of the debugref tool that conforms SDD 1.0
|
|
d23 1
|
|
a23 1
|
|
* [[%ATTACHURL%/sddRefDebug.tar.gz][sddRefDebug.tar.gz]]: LINUX/UNIX users download
|
|
d25 1
|
|
a25 1
|
|
* [[%ATTACHURL%/sddRefDebug.zip][sddRefDebug.zip]]: Windows users
|
|
d27 1
|
|
a27 1
|
|
* [[%ATTACHURL%/sddRefDebugDoc.txt][sddRefDebugDoc.txt]]: debugRef tool Help file
|
|
d29 1
|
|
a29 1
|
|
* [[%ATTACHURL%/sddRefDebug.tar][sddRefDebug.tar]]: Linux/unix users
|
|
@
|
|
|
|
|
|
1.8
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 2
|
|
@
|
|
|
|
|
|
1.7
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="JacobAsiedu" date="1094567460" format="1.0" version="1.7"}%
|
|
d3 26
|
|
a28 31
|
|
* * [[%ATTACHURL%/sdd.zip][sdd.zip]]: SDD reference debugging tool
|
|
|
|
sddDebugRef is a tool by Main.JacobAsiedu to supply meaningful text to the debugref attributes in SDD instance documents. Normally, descriptions and other things in an instance document make references to objects defined in the Terminology section. Since these objects are typically identified by a numeric key, it is desirable to annotate the instance document references with text that helps you figure out what the target of the reference is about, and where it can be found. This XSLT application does that. You can also simply dump your instance document into http://efg.cs.umb.edu:8080/cocoon/SDDdebugref
|
|
|
|
-- Main.BobMorris - 03 Dec 2003
|
|
|
|
|
|
* [[%ATTACHURL%/sdd.zip][sdd.zip]]: $Id: sddRefDebug.xsl,v 1.6 2003/12/06 21:29:19 kas
|
|
|
|
Bug fixes
|
|
|
|
---
|
|
|
|
This is not an existing tool, but something I was discussing with Bryan Heidorn and which I think could very easily be developed to assist us with testing the scalability of the SDD schema and the capabilities of any SDD software we develop.
|
|
|
|
One of the challenges in the SDD schema is the number of Key/KeyRef pairs which need to be handled, along with all of the associated constraint processing. We need to get a better feel for the performance implications of these characteristics. Fortunately it seems likely that these factors are largely independent of the actual meaning of any particular Terminology, Entities or Descriptions elements. We could therefore create a program to generate SDD test documents varying a small number of parameters. The parameters could be something like: <nop>NumberOfCharacters, <nop>NumberOfStatesPerCharacter, <nop>NumberOfClassDescriptions, <nop>NumberOfObjectDescriptions, etc. We could vary the parameters to alter the depth of the class hierarchy and the number of specimens per taxon and the complexity of the terminology (along with whether or not it is imported/included). The actual elements could be little more than "State 1006", "Description 214", etc., although we could vary the balance of <nop>NaturalLanguageDescriptions and <nop>CodedDescriptions. I think this could be a very simple program but could give us a wide variety of different documents against which to test SDD processors.
|
|
|
|
-- Main.DonaldHobern - 21 May 2004
|
|
|
|
Attached is the latest version of the debugref tool that conforms SDD 1.0
|
|
|
|
--Main.JacobAsiedu
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.tar.gz][sddRefDebug.tar.gz]]: LINUX/UNIX users download
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.zip][sddRefDebug.zip]]: Windows users
|
|
|
|
* [[%ATTACHURL%/sddRefDebugDoc.txt][sddRefDebugDoc.txt]]: debugRef tool Help file
|
|
|
|
* [[%ATTACHURL%/sddRefDebug.tar][sddRefDebug.tar]]: Linux/unix users
|
|
|
|
d34 1
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="GregorHagedorn" date="1085163300" format="1.0" version="1.6"}%
|
|
d21 13
|
|
d35 4
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1085139833" format="1.0" version="1.5"}%
|
|
d18 1
|
|
a18 1
|
|
One of the challenges in the SDD schema is the number of Key/KeyRef pairs which need to be handled, along with all of the associated constraint processing. We need to get a better feel for the performance implications of these characteristics. Fortunately it seems likely that these factors are largely independent of the actual meaning of any particular Terminology, Entities or Descriptions elements. We could therefore create a program to generate SDD test documents varying a small number of parameters. The parameters could be something like: NumberOfCharacters, NumberOfStatesPerCharacter, NumberOfClassDescriptions, NumberOfObjectDescriptions, etc. We could vary the parameters to alter the depth of the class hierarchy and the number of specimens per taxon and the complexity of the terminology (along with whether or not it is imported/included). The actual elements could be little more than "State 1006", "Description 214", etc., although we could vary the balance of NaturalLanguageDescriptions and CodedDescriptions. I think this could be a very simple program but could give us a wide variety of different documents against which to test SDD processors.
|
|
d21 1
|
|
a21 1
|
|
%META:FILEATTACHMENT{name="sdd.zip" attr="" comment="$Id: sddRefDebug.xsl,v 1.6 2003/12/06 21:29:19 kas" date="1071012810" path="C:\cvsCheckout\sdd.zip" size="3330911" user="BobMorris" version="1.2"}%
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="DonaldHobern" date="1085130040" format="1.0" version="1.4"}%
|
|
d14 1
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="JacobAsiedu" date="1079123568" format="1.0" version="1.3"}%
|
|
d14 6
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1071012900" format="1.0" version="1.2"}%
|
|
d5 1
|
|
a5 1
|
|
sddDebugRef is a tool by Main.JacobAsiedu to supply meaningful text to the debugref attributes in SDD instance documents. Normally, descriptions and other things in an instance document make references to objects defined in the Terminology section. Since these objects are typically identified by a numeric key, it is desirable to annotate the instance document references with text that helps you figure out what the target of the reference is about, and where it can be found. This XSLT application does that. You can also simply dump your instance document into http://efg.cs.umb.edu:8080/sdd/debugref.
|
|
a8 2
|
|
---
|
|
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1070411580" format="1.0" version="1.1"}%
|
|
d11 6
|
|
a16 1
|
|
%META:FILEATTACHMENT{name="sdd.zip" attr="" comment="SDD reference debugging tool" date="1070411359" path="C:\cvsCheckout\sdd.zip" size="3324800" user="BobMorris" version="1.1"}%
|
|
@
|