analysis.xml 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <?xml-stylesheet type="text/xsl" href="odmlTerms.xsl" xmlns:odml="http://www.g-node.org/odml"?>
  3. <odML version="1.1">
  4. <repository>http://portal.g-node.org/odml/terminologies/v1.1/terminologies.xml</repository>
  5. <version>1.0</version>
  6. <date>2011-01-21</date>
  7. <!-- ********************************************************* -->
  8. <!-- Analysis section -->
  9. <!-- ********************************************************* -->
  10. <section>
  11. <type>analysis</type>
  12. <name>Analysis</name>
  13. <definition>Sections of the Analysis type can be used to describe analyses.</definition>
  14. <property>
  15. <name>Author</name>
  16. <type>person</type>
  17. <definition>The name of the person who did the analysis, e.g. 'John Doe' or 'Doe, John'</definition>
  18. </property>
  19. <property>
  20. <name>Date</name>
  21. <type>date</type>
  22. <definition>The date of analysis.</definition>
  23. </property>
  24. <property>
  25. <name>Description</name>
  26. <type>text</type>
  27. <definition>A general description of the analysis.</definition>
  28. </property>
  29. <property>
  30. <name>Method</name>
  31. <type>string</type>
  32. <definition>The name of a method used in this analysis. E.g. "power spectrum".</definition>
  33. </property>
  34. <property>
  35. <name>CommandlineCall</name>
  36. <type>string</type>
  37. <definition>The command used to execute the analysis including the command line parameter.</definition>
  38. </property>
  39. <property>
  40. <name>Comment</name>
  41. <type>text</type>
  42. <definition>Specific comments on this analysis.</definition>
  43. </property>
  44. <property>
  45. <name>CodeFile</name>
  46. <type>binary</type>
  47. <definition>
  48. The program code to analyse the data can be transferred using this property.
  49. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  50. code file.
  51. </definition>
  52. </property>
  53. <property>
  54. <name>CodeFileURL</name>
  55. <type>URL</type>
  56. <definition>The URL of the applied piece of program code to actually do the analysis.</definition>
  57. </property>
  58. <property>
  59. <name>CodeRevision</name>
  60. <type>string</type>
  61. <definition>If the analysis code is under version control the revision number can be specified using this
  62. property.
  63. </definition>
  64. </property>
  65. <property>
  66. <name>ConfigFile</name>
  67. <type>binary</type>
  68. <definition>
  69. The configurations used to analyse the data can be transferred using this property.
  70. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  71. configuration file.
  72. </definition>
  73. </property>
  74. <property>
  75. <name>ConfigFileURL</name>
  76. <type>URL</type>
  77. <definition>The URL of the used configuration file used to run the analysis.</definition>
  78. </property>
  79. <property>
  80. <name>DatasetFile</name>
  81. <type>binary</type>
  82. <definition>
  83. The data analysed ion the described way can be transferred using this property.
  84. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of underlying
  85. dataset file.
  86. </definition>
  87. </property>
  88. <property>
  89. <name>DatasetFileURL</name>
  90. <type>URL</type>
  91. <definition>The URL of a analysed datasetFile.</definition>
  92. </property>
  93. <property>
  94. <name>ResultFile</name>
  95. <type>binary</type>
  96. <definition>
  97. The results of this analysis can be transferred using this property.
  98. Using it will blow up the the size of the metadatafile and we recommend to rather define the URL of the results
  99. file.
  100. </definition>
  101. </property>
  102. <property>
  103. <name>ResultFileURL</name>
  104. <type>URL</type>
  105. <definition>The URL of a results file.</definition>
  106. </property>
  107. <property>
  108. <name>ResultFigure</name>
  109. <type>binary</type>
  110. <definition>
  111. A figure showing the results. This property is meant to store the real figure content.
  112. This will blow up the the size of the metadatafile and we recommend to rather define the URL of the figure.
  113. </definition>
  114. </property>
  115. <property>
  116. <name>PaperDOI</name>
  117. <type>text</type>
  118. <definition>If the results of this analysis have been published one can store the doi of the paper.</definition>
  119. </property>
  120. <property>
  121. <name>PaperURL</name>
  122. <type>URL</type>
  123. <definition>If the results of this analysis have been published the URL of the document can be given here
  124. </definition>
  125. </property>
  126. </section>
  127. </odML>