tissue microarray ( tma ) is a high throughput technology that allows hundreds of tissue samples to be placed in a recipient paraffin histology block .
tissue microarray blocks ( tmas ) enable rapid molecular analysis of tissue to provide new diagnostic and prognostic biomarkers as well as potential therapeutic targets in disease .
each tissue core may be from a different source block , and the recipient tma block can be sectioned to provide thin sections that are subsequently mounted onto glass slides for testing and analysis . as a result ,
whole tissue cross - sections that expend the tissue block are not required to be used by a single research study .
the importance of using the xml standard to encode pathology data has been described previously .
the tissue microarray data exchange specification ( tma des ) is an xml specification for encoding tma experiment data in a machine readable format that is also human readable .
the tma des data format has been used by a variety of systems , and allows any persons or system using it to share their tma data .
tma des defines common data elements ( cdes ) that form a basic vocabulary for describing tma data , and have commonly agreed upon syntax and semantics .
this enables tma des data to be exported from computer applications such as xperanto - tma and tamee and shared among researchers .
an extract from a modified version of a tma des file included with the paper that described the tma des dtd is shown in figure 1 .
the xml in this extract defines cde names in pairs of tags ( e.g.  < creator> 
</creator >  ) , and values for those cdes are contained within those tags ( e.g. " joe bloggs " ) .
the cdes in figure 1 represent the header of a tma des file , which contains information such as a title assigned to the tma and the creator of the tma .
cde can contain other cdes , with information such as a description of the tma , or the source of the tma , but only the  title  and  creator  cdes are shown in figure 1 . extract from a modified tma des xml file while tma des data is encoded in xml , the rules defining the syntax and structure of tma des data are described in a  document type definition 
dtd definition for the tma element another standard called iso 11179 is used to describe the semantics of tma des cdes .
an example of an iso 11179 description of the  tma  cde is shown in figure 3 .
this entry specifies the registration authority that has defined the cde , the language defining the cde , whether the cde is required in a tma des document , the datatype of the cde ( e.g. is it textual , numeric , empty ) , the number of times it can occur in a tma des document , and a definition field that describes the semantic meaning of the cde .
iso 11179 description of the tma des  tma  cde the multiple formats used for encoding data by tma des require separate applications for verifying syntactical and structural correctness , and for processing the data they contain , as illustrated in figure 4 .
for example , an xml parser ( a program used to verify that an xml document is compliant with the rules of the xml syntax , and to extract information from xml documents ) could be used to validate and process tma des xml data , but it would not recognize a dtd file as a valid document , nor would it be able to extract information from a dtd file .
the use of multiple encoding formats , instead of a single encoding format , adds to the burden of developing applications that read and write tma des data .
in addition , there exist alternative xml - based formats for describing data which in some respects are superior to those used by tma des , and there are convincing arguments for adopting their use in place of those currently used by tma des . a notable effort to define a schema for tma data
this paper defines an owl schema containing concepts specific to tma experiments , and illustrates the benefits of using owl to describe tma data .
a limitation of xml is that there must be some agreement on the semantic meanings of cdes before they are useful for sharing data .
owl , on the other hand , is a format that can use cdes defined in existing ontologies .
the tma owl schema illustrates how existing owl ontologies are used by the authors when producing tma data .
however , this owl schema does not contain all the concepts that tma des does .
it also does not address the issues with tma des that arise due to the lack of an encoding format for the existing tma des iso11179 definitions .
in addition , while owl allows data to be described , it does not provide mechanisms for defining the syntax / structure of data , or valid ranges of values for data .
tma des data requires separate parsers for xml , dtd , and iso 11179 documents we propose using xml to encode all tma des data .
two xml based standards , xml schema and the resource description framework ( rdf ) can be used in place of dtds and iso 11179 respectively .
for example , the tma des cdes in figure 5 represent the date a block was created , a textual description of the block , and the number of cores in the block
. cdes from tma des xml data these data are of different types ( date , textual and numeric respectively ) . unlike dtds , xml schemas enable data to be checked for invalid values by allowing datatypes to be specified for cdes .
for example , a program may require that the value of the block_number - of - cores cde in figure 5 be numeric ( e.g. " 26 " as above ) , not textual ( e.g.  twenty six  ) .
xml schemas are also more flexible than dtds when specifying valid ranges of values for cdes . for example
, the following constraints on values could be imposed on cdes using xml schema : 
 block_core - size must be a real number with one decimal placeblock_number - of - cores must be an integer between 0 and 100 inclusivecore_gender must be a single character with the value
fblock_identifier must be composed of two characters , followed by 2 single digit integers , then a hyphen , then 3 single digit integers ( e.g.  ta00 - 050  ,  bd10 - 450  ) . 
  block_core - size must be a real number with one decimal place block_number - of - cores must be an integer between 0 and 100 inclusive core_gender must be a single character with the value  m  or  f 
block_identifier must be composed of two characters , followed by 2 single digit integers , then a hyphen , then 3 single digit integers ( e.g.  ta00 - 050  ,  bd10 - 450  ) .
the tma des specification defines valid ranges of values for cdes in the definition attribute of entries in an iso 11179 file .
for example , the definition attribute for the core_organism cde is : organism name at species level for organism whose tissue is represented in the donor block , comment : uri for taxonomy.dat is ftp://ftp.ebi.ac.uk/pub/databases/taxonomy/taxonomy.dat the correct entry for human tissue is  9606 human 
tma des does not provide a commonly accepted mechanism for enabling parsers to automatically check that the values of cdes comply with their iso 11179 definitions .
these definitions serve as guidelines for producers of data , rather than a mechanism for automatically checking that data is formatted correctly .
in contrast , xml parsers can verify that the value of cdes satisfy constraints that are expressed in xml schema documents .
rdf is commonly encoded in xml , whereas iso 11179 does not specify how metadata should be encoded . there may be inconsistencies in how parsers interpret iso 11179 data .
for example , a parser may identify cde names as a string of characters , followed by a colon , and terminated with a carriage return .
this parser would identify three cdes in the sample text below (  maximum occurrence  ,  definition ,  and  characters  ) whereas in actual fact only  maximum occurrence  and  definition  are valid cdes .
definition : this is the slide identifier issued by the distributor ; it is a character string that permits the following characters :  [ 0 - 9][a - z][a - z].- _ :  another example of a potential problem occurs in the iso 11179 definition of the tma des 
this definition is shown below : this line contains definitions for two attributes of the cde (  datatype  and  maximum occurrence  ) .
each attribute for all other cdes defined in this document are on their own line , therefore we can assume that this is a typographical error and the line should be split in two , with separate lines defining the  datatype  and  maximum occurrence  attributes . while it may appear obvious that this definition contains two attributes of a cde , it is not obvious to machines ( that process this data ) .
for example , a parser we wrote to convert iso 11179 data to rdf determined that the datatype of the block_protocol cde was  character string maximum occurrence : unlimited  .
unlike iso 11179 , rdf is part of the stack of protocols that compose the  semantic web .
 berman emphasizes the importance of xml providing logic and meaning to data , allowing it to be part of the  semantic web .
 the use of rdf to encode tma des metadata could potentially enable applications to process tma des data with greater autonomy .
we have implemented an xml schema that describes the syntax and structure of tma des .
we have also produced an rdf file that provides the same semantic definitions that are specified in the tma des iso 11179 file .
for example , the tma des cdes in figure 5 represent the date a block was created , a textual description of the block , and the number of cores in the block
. cdes from tma des xml data these data are of different types ( date , textual and numeric respectively ) . unlike dtds , xml schemas enable data to be checked for invalid values by allowing datatypes to be specified for cdes .
for example , a program may require that the value of the block_number - of - cores cde in figure 5 be numeric ( e.g. " 26 " as above ) , not textual ( e.g.  twenty six  ) .
xml schemas are also more flexible than dtds when specifying valid ranges of values for cdes . for example
, the following constraints on values could be imposed on cdes using xml schema : 
 block_core - size must be a real number with one decimal placeblock_number - of - cores must be an integer between 0 and 100 inclusivecore_gender must be a single character with the value  m  or 
fblock_identifier must be composed of two characters , followed by 2 single digit integers , then a hyphen , then 3 single digit integers ( e.g.  ta00 - 050  ,  bd10 - 450  ) . 
  block_core - size must be a real number with one decimal place block_number - of - cores must be an integer between 0 and 100 inclusive core_gender must be a single character with the value  m  or
block_identifier must be composed of two characters , followed by 2 single digit integers , then a hyphen , then 3 single digit integers ( e.g.  ta00 - 050  ,  bd10 - 450  ) .
the tma des specification defines valid ranges of values for cdes in the definition attribute of entries in an iso 11179 file .
for example , the definition attribute for the core_organism cde is : organism name at species level for organism whose tissue is represented in the donor block , comment : uri for taxonomy.dat is ftp://ftp.ebi.ac.uk/pub/databases/taxonomy/taxonomy.dat the correct entry for human tissue is  9606 human 
tma des does not provide a commonly accepted mechanism for enabling parsers to automatically check that the values of cdes comply with their iso 11179 definitions .
these definitions serve as guidelines for producers of data , rather than a mechanism for automatically checking that data is formatted correctly .
in contrast , xml parsers can verify that the value of cdes satisfy constraints that are expressed in xml schema documents .
rdf is commonly encoded in xml , whereas iso 11179 does not specify how metadata should be encoded . there may be inconsistencies in how parsers interpret iso 11179 data .
for example , a parser may identify cde names as a string of characters , followed by a colon , and terminated with a carriage return .
this parser would identify three cdes in the sample text below (  maximum occurrence 
,  definition ,  and  characters  ) whereas in actual fact only  maximum occurrence  and  definition  are valid cdes .
definition : this is the slide identifier issued by the distributor ; it is a character string that permits the following characters :  [ 0 - 9][a - z][a - z].- _ :  another example of a potential problem occurs in the iso 11179 definition of the tma des 
this line contains definitions for two attributes of the cde (  datatype  and  maximum occurrence  ) .
each attribute for all other cdes defined in this document are on their own line , therefore we can assume that this is a typographical error and the line should be split in two , with separate lines defining the  datatype  and  maximum occurrence  attributes . while it may appear obvious that this definition contains two attributes of a cde , it is not obvious to machines ( that process this data ) .
for example , a parser we wrote to convert iso 11179 data to rdf determined that the datatype of the block_protocol cde was  character string maximum occurrence : unlimited  . unlike iso 11179 ,
rdf is part of the stack of protocols that compose the  semantic web . 
berman emphasizes the importance of xml providing logic and meaning to data , allowing it to be part of the  semantic web .
 the use of rdf to encode tma des metadata could potentially enable applications to process tma des data with greater autonomy .
we have implemented an xml schema that describes the syntax and structure of tma des .
we have also produced an rdf file that provides the same semantic definitions that are specified in the tma des iso 11179 file .
there were two main tasks in creating an xml schema for tma des : 
 the structure and syntax rules specified in the tma des dtd are replicated in an xml schema.the datatypes and constraints on values for cdes defined in the tma des iso 11179 file are defined in this xml schema . 
 
the structure and syntax rules specified in the tma des dtd are replicated in an xml schema .
the datatypes and constraints on values for cdes defined in the tma des iso 11179 file are defined in this xml schema . in order to create an xml schema version of the tma des dtd ,
an online tool was used to convert the tma des dtd into an xml schema .
core_histo - repository ,  from the resulting xml schema is shown in figure 6 .
xml schema definition of a tma des cde the xml schema extract , figure 6 , specifies the same information as the definition for the core_histo - repository cde in the tma des dtd . the xml schema document produced by the dtd to xml schema converter ( supplementary file 1 ) contains definitions for all the tma des cdes . after replicating the tma des syntax and structure rules in an xml schema document , the tma des iso 11179 file was consulted in order to determine the datatypes that the tma des xml schema document should specify for cdes .
the following is a list of the cde datatypes used in the iso 11179 file : 
 character stringdate ( yyyy - mm - dd)integerreal numberreal numberscharacter string representing taxonomy.dat identifier number followed by an allowable taxonomy.dat name for the identifier numberdecimal numberdecimal number ranging from 0 to 100empty 
  character string representing taxonomy.dat identifier number followed by an allowable taxonomy.dat name for the identifier number decimal number ranging from 0 to 100 some of these datatypes are mapped to their xml schema equivalents [ table 1 ] .
mapping iso 11179 datatypes to equivalent xml schema datatypes other datatypes contained restrictions on their values that were also defined in our xml schema ( e.g.  decimal number ranging from 0 to 100  ) .
we modified the cde definitions in the xml schema file so that they had the appropriate datatypes .
decimal  type cdes in the iso 11179 file were defined as being of type " xs : float " in the xml schema .
the tma des xml schema was also modified where appropriate so that it specified constraints on the values of cdes that were specified in the tma des iso 11179 file .
figure 7 shows an xml schema extract that specifies a constraint on the value of the  core_organism  cde .
this cde definition uses a regular expression to specify that values for this cde must consist of a sequence of digits , followed by any number of alphanumeric characters (  < xs : pattern value="[0 - 9]*.*"/ >  ) .
xml schema allows other constraints such as valid ranges of numeric values and particular values for textual data to be specified .
iso11179tordf  that parsed the tma des iso 11179 file and created an rdf version of this file . this program is a bash script written on a computer running a unix operating system ( supplementary file 2 ) .
some alterations had to be made to the tma des iso 11179 file in order to ensure that all attributes were described in a consistent fashion .
if the data contained in this file were encoded in xml , it would not have been necessary to manually alter the file so that the program could parse it , illustrating the advantage of our approach of encoding this data using xml .
these alterations included : 
 removing html links at the beginning of the document which linked to the individual cdes.removing carriage returns from property values.ensure that there was only one property definition per line ( e.g. in the entry for the  block_protocol 
cde , split the line  datatype : character stringmaximum occurrence : unlimited  into two lines ,  datatype : character string  and  maximum occurrence : unlimited  ) . 
 
removing html links at the beginning of the document which linked to the individual cdes . removing carriage returns from property values .
ensure that there was only one property definition per line ( e.g. in the entry for the  block_protocol  cde , split the line  datatype : character stringmaximum occurrence : unlimited  into two lines ,  datatype : character string  and  maximum occurrence : unlimited  ) .
the program was run from the command prompt on a machine running unix as shown below : iso11179tordf tmades_cdes.txt > > tmades_cdes.rdf the program takes the name of a file containing iso 11179 definitions as input ( in this case ,  tmades_cdes.txt  ) .
this output could be redirected to a file , as in the example above , using the 
> >  operator followed by the name of a file (  tmades_cdes.rdf  ) .
figure 8 shows an extract from the rdf file generated in this manner which describes the  histo  cde .
rdf description of the  histo  cde the rdf generated by iso 11179 to rdf contains some redundant information .
the  obligation  ,  datatype  and  maximumoccurrence  cdes contain data that is also specified in the tma des xml schema document . for the sake of completeness ,
however , we have included them in our rdf file ( supplementary file 3 ) .
there were two main tasks in creating an xml schema for tma des : 
 the structure and syntax rules specified in the tma des dtd are replicated in an xml schema.the datatypes and constraints on values for cdes defined in the tma des iso 11179 file are defined in this xml schema . 
 
the structure and syntax rules specified in the tma des dtd are replicated in an xml schema .
the datatypes and constraints on values for cdes defined in the tma des iso 11179 file are defined in this xml schema . in order to create an xml schema version of the tma des dtd ,
an online tool was used to convert the tma des dtd into an xml schema .
core_histo - repository ,  from the resulting xml schema is shown in figure 6 .
xml schema definition of a tma des cde the xml schema extract , figure 6 , specifies the same information as the definition for the core_histo - repository cde in the tma des dtd . the xml schema document produced by the dtd to xml schema converter ( supplementary file 1 ) contains definitions for all the tma des cdes . after replicating the tma des syntax and structure rules in an xml schema document , the tma des iso 11179 file was consulted in order to determine the datatypes that the tma des xml schema document should specify for cdes .
the following is a list of the cde datatypes used in the iso 11179 file : 
 character stringdate ( yyyy - mm - dd)integerreal numberreal numberscharacter string representing taxonomy.dat identifier number followed by an allowable taxonomy.dat name for the identifier numberdecimal numberdecimal number ranging from 0 to 100empty 
  character string representing taxonomy.dat identifier number followed by an allowable taxonomy.dat name for the identifier number decimal number ranging from 0 to 100 some of these datatypes are mapped to their xml schema equivalents [ table 1 ] .
mapping iso 11179 datatypes to equivalent xml schema datatypes other datatypes contained restrictions on their values that were also defined in our xml schema ( e.g.  decimal number ranging from 0 to 100  ) .
we modified the cde definitions in the xml schema file so that they had the appropriate datatypes .
decimal  type cdes in the iso 11179 file were defined as being of type " xs : float " in the xml schema .
the tma des xml schema was also modified where appropriate so that it specified constraints on the values of cdes that were specified in the tma des iso 11179 file .
figure 7 shows an xml schema extract that specifies a constraint on the value of the  core_organism  cde .
this cde definition uses a regular expression to specify that values for this cde must consist of a sequence of digits , followed by any number of alphanumeric characters (  < xs : pattern value="[0 - 9]*.*"/ >  ) .
xml schema allows other constraints such as valid ranges of numeric values and particular values for textual data to be specified .
iso11179tordf  that parsed the tma des iso 11179 file and created an rdf version of this file . this program is a bash script written on a computer running a unix operating system ( supplementary file 2 ) .
some alterations had to be made to the tma des iso 11179 file in order to ensure that all attributes were described in a consistent fashion .
if the data contained in this file were encoded in xml , it would not have been necessary to manually alter the file so that the program could parse it , illustrating the advantage of our approach of encoding this data using xml .
these alterations included : 
 removing html links at the beginning of the document which linked to the individual cdes.removing carriage returns from property values.ensure that there was only one property definition per line ( e.g. in the entry for the  block_protocol 
cde , split the line  datatype : character stringmaximum occurrence : unlimited  into two lines ,  datatype : character string  and  maximum occurrence : unlimited  ) . 
 
removing html links at the beginning of the document which linked to the individual cdes . removing carriage returns from property values .
ensure that there was only one property definition per line ( e.g. in the entry for the  block_protocol  cde , split the line  datatype : character stringmaximum occurrence : unlimited  into two lines ,  datatype : character string  and  maximum occurrence : unlimited  ) .
the program was run from the command prompt on a machine running unix as shown below : iso11179tordf tmades_cdes.txt > >
tmades_cdes.rdf the program takes the name of a file containing iso 11179 definitions as input ( in this case ,  tmades_cdes.txt  ) .
this output could be redirected to a file , as in the example above , using the 
> >  operator followed by the name of a file (  tmades_cdes.rdf  ) .
figure 8 shows an extract from the rdf file generated in this manner which describes the  histo  cde .
rdf description of the  histo  cde the rdf generated by iso 11179 to rdf contains some redundant information .
the  obligation  ,  datatype  and  maximumoccurrence  cdes contain data that is also specified in the tma des xml schema document . for the sake of completeness ,
however , we have included them in our rdf file ( supplementary file 3 ) .
we performed an experiment where our tma des xml schema document was used to confirm that existing tma des data were well formed and valid .
the ta00-050.xml file representing tma des data was successfully tested for conformance to the syntax and rules in this xml schema document using an online xml schema validator .
we also deliberately introduced errors into the ta00 - 050 xml file , and attempted to validate it with both the xml schema validator and an xml dtd validator in order to compare their error checking capabilities .
table 2 shows the errors that were introduced , along with the messages generated by the two validators .
while the first three errors were detected by both the xml schema and the dtd validator , the last two errors were only detected when validation took place against the xml schema document .
errors introduced into tma des xml data , and error messages returned by xml schema and dtd parsers when the xml was validated against them when an rdf parser processes an rdf file , it should be able to extract the object or concept which is being described , the attribute names of that object / concept , and the values of these attributes ( this combination of data is known as a  triple  ) .
statements such as the following can thus be created by rdf parsers : 
 the cd : version of the histo object is  version 1.0the cd : registrationauthority of the histo object is 
association for pathology informaticsthe cd : language of the histo object is  en  
  the cd : version of the histo object is  version 1.0  the cd : registrationauthority of the histo object is 
association for pathology informatics  the cd : language of the histo object is  en  after executing iso11179tordf , an rdf file with definitions for the 80 tma des cdes was created .
examples of the triples generated by this service are shown in table 3 , and the complete output from the w3c rdf parser is in supplementary file 3 .
we performed an experiment where our tma des xml schema document was used to confirm that existing tma des data were well formed and valid .
the ta00-050.xml file representing tma des data was successfully tested for conformance to the syntax and rules in this xml schema document using an online xml schema validator .
we also deliberately introduced errors into the ta00 - 050 xml file , and attempted to validate it with both the xml schema validator and an xml dtd validator in order to compare their error checking capabilities .
table 2 shows the errors that were introduced , along with the messages generated by the two validators .
while the first three errors were detected by both the xml schema and the dtd validator , the last two errors were only detected when validation took place against the xml schema document .
errors introduced into tma des xml data , and error messages returned by xml schema and dtd parsers when the xml was validated against them
when an rdf parser processes an rdf file , it should be able to extract the object or concept which is being described , the attribute names of that object / concept , and the values of these attributes ( this combination of data is known as a  triple  ) .
statements such as the following can thus be created by rdf parsers : 
 the cd : version of the histo object is 
association for pathology informaticsthe cd : language of the histo object is  en  
  the cd : version of the histo object is  version 1.0  the cd : registrationauthority of the histo object is 
the cd : language of the histo object is  en  after executing iso11179tordf , an rdf file with definitions for the 80 tma des cdes was created .
examples of the triples generated by this service are shown in table 3 , and the complete output from the w3c rdf parser is in supplementary file 3 .
the introduction of the tma des has greatly facilitated the recording , storage , and sharing of tma data .
one current problem however is that three formats are used for encoding tma des data ( xml , dtd and iso 11179 ) .
we have shown that all tma des data could be encoded using xml , which simplifies processing .
xml schema allows datatypes and valid values to be specified for cdes , which enables a wider range of error checking to be performed using xml schemas than could be performed using dtds .
we produced an xml schema version of the tma des dtd , and used this to validate the ta00 - 050 .
xml file that was included as a supplementary file in the study on the tma des dtd published by nohle et al . and demonstrated the superior error checking capabilities of our schema to the existing tma des dtd .
the development of new tools which validate tma des data using xml schemas is an opportunity for future work .
we created a program which converted data in the tma des iso 11179 file to an rdf xml format .
the output from this program was successfully parsed by the w3c rdf validation service , with no human assistance required .
in contrast , the iso 11179 file required manual pre - processing in order that it could be parsed correctly by our program , illustrating the benefits of encoding tma des metadata in xml .
rdf is also part of the stack of protocols that compose the  semantic web ,  which envisions applications using metadata to make decisions about how data is processed without human guidance .
an avenue for future investigation is the development of  software agents  that can aggregate rdf descriptions of tma des data from multiple sources , and  reason  and perform operations on that data in an autonomous fashion . we have encoded the syntax and semantic rules for tma des in a single language , xml , and have illustrated how a wider range of error checking can be performed on tma des data using xml schemas instead of dtds , and how the use of rdf encoded in xml for defining semantic rules for tma des cdes allows these rules to be interpreted by applications , allowing semantic data to be easily shared .
pathologists could benefit from these advantages by using tma des processing applications which use xml schemas and rdf .
 background : the tissue microarray data exchange specification ( tma des ) is an xml specification for encoding tma experiment data . while tma des data is encoded in xml , the files that describe its syntax , structure , and semantics are not . the dtd format is used to describe the syntax and structure of tma des , and the iso 11179 format is used to define the semantics of tma des . 
 however , xml schema can be used in place of dtds , and another xml encoded format , rdf , can be used in place of iso 11179 . encoding all tma des data and metadata in xml would simplify the development and usage of programs which validate and parse tma des data . 
 xml schema has advantages over dtds such as support for data types , and a more powerful means of specifying constraints on data values . 
 an advantage of rdf encoded in xml over iso 11179 is that xml defines rules for encoding data , whereas iso 11179 does not.materials and methods : we created an xml schema version of the tma des dtd . 
 we wrote a program that converted iso 11179 definitions to rdf encoded in xml , and used it to convert the tma des iso 11179 definitions to rdf.results:we validated a sample tma des xml file that was supplied with the publication that originally specified tma des using our xml schema . 
 we successfully validated the rdf produced by our iso 11179 converter with the w3c rdf validation service.conclusions:all tma des data could be encoded using xml , which simplifies its processing . 
 xml schema allows datatypes and valid value ranges to be specified for cdes , which enables a wider range of error checking to be performed using xml schemas than could be performed using dtds . 
BACKGROUND
Advantages of XML Schema over DTDs
Advantages of RDF Schema over ISO 11179
Maximum Occurrence: Unlimited
Datatype: Character string maximum occurrence: Unlimited
MATERIALS AND METHODS
Creating an XML Schema version of the TMA DES DTD
Creating an RDF version of the TMA DES ISO 11179 file
RESULTS
Validating TMA DES data with our TMA DES XML schema
Parsing RDF data generated from TMA DES ISO 11179 data
CONCLUSIONS