DIMEXML for Test Method
AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete
AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete
The Office of Structural Material (OSM) of Caltrans has defined an XML schema for each of the material types for the purpose of storing and sharing material test data. An XML schema defines a type of XML format. An XML file is accepted by a system if and only if the XML file can be validated against the schema defined by or supported by the system. For a more descriptive explanation, please visit Wiki: XML Schema. In order to use the batch upload feature to submit data to DIME, the test data has to be written in XML format that can be validated against one of the DIMEXML schemas. These files are referred to as DIMEXML files hereon.
DIMEXML files, or XML files in general, can be created with any text edidtor. However, it is strongly encouraged to have XML file created by software if a data management system is already in place to manage lab test data. Please remember, an XML file must be validated against one of the DIMEXML Schemas before it can be uploaded to DIME.
This page illustrates what are included in an DIMEXML file with a single AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete test result. Please note, however, that each of the DIMEXML schemas allows a sample to include any number of test results from any combination of test methods.
DIME allows users to submit brand new samples or to add new test results to existing samples by uploading DIMEXML files. While these two use cases require two different DIMEXML formats, please be sure to view the correct tab below for the intended purpose.
Below are some links that you may find helpful:- Not registered for DIME? Check this page out to find out how you can register for DIME: Register for DIME.
- Not sure what DIME Project ID is for your project? Look it up on this page: DIME Project ID Lookup.
- DIME also supports submitting data using online forms. Instructions for submitting data using online forms are available Here .
- To see a full list of supported test methods, please visit Test Catalog Page.
- To view or download the complete DIMEXML schemas, visit DIMEXML Schema Page.
- There are many XML validation tools. For a free online tool, try XML Validation Tool.
- DIMEXML empty structures will be available for download for each of the variations for the test method. Check back later.
- Instructions on how to upload DIMEXML files to DIME: Upload DIMEXML Instructions
AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete DIMEXML Structure
- Element by Elment section describes the structure element by element starting from the root with a depth-first approach until all elements are mentioned.
- Treeview section provides an complete overview of DIMEXML in a tree-like structure.
- Tag Definitions section describes each of the tag elments in greater details.
- * indicates required fields
Element by Element
Jump to Treeview | Jump to Tag Definitions
Root Element:
The root element for a new sample in Aggregate DIMEXML format is Aggregate_dimexml, and it requires two child elements, new_sample and tests.
<Aggregate_dimexml> <new_sample></new_sample>*<!-- complex element. See Child Element: <new_sample> below. --> <tests></tests>*<!-- complex element. See Child Element: <tests> below. --> </Aggregate_dimexml>*
Child Element: <new_sample> Jump to tag definitions
new_sample requires two fields and two complext types.
<new_sample> <sample_project_id></sample_project_id>*<!-- DIME Project ID, look it up using the DIME Project ID Lookup page at https://dime.dot.ca.gov/index.php?r=project/projectIDLookup. --> <sample_taken_date></sample_taken_date>*<!-- sample taken date, must be in date format: yyyy-mm-dd --> <sample_meta_data></sample_meta_data>*<!-- complex element, see below --> <material_identification></material_identification>*<!-- complex element, see below --> </new_sample>*
Child Element: <sample_meta_data> Jump to tag definitions
sample_meta_data is for storing sample meta data about the sample.
<sample_meta_data> <sample_received></sample_received>*<!-- Will the laboratory/organization for which you are a member perform testing on this material sample? --> <sample_date_received></sample_date_received><!-- Date that the sample was received by the laboratory/organization performing the testing --> <sample_type_name></sample_type_name>*<!-- Sample type --> <sample_constitutes></sample_constitutes>*<!-- The quantity of what the sample constitutes --> <sample_description></sample_description>*<!-- A brief description of the sample --> <sampler_first_name></sampler_first_name>*<!-- First name of sampler or witnessed by --> <sampler_last_name></sampler_last_name>*<!-- Last name of sampler or witnessed by --> <sampler_title></sampler_title><!-- Title of sampler --> <sampler_telephone></sampler_telephone><!-- Telephone number of sampler --> <sample_taken_from_source></sample_taken_from_source>*<!-- From where was the sample collected --> <sample_source_name></sample_source_name>*<!-- The fabricator/manufacturer/facility name --> <sample_laboratory_id></sample_laboratory_id><!-- Laboratory sample identification --> <linked_sample></linked_sample><!-- Linked DIME Sample ID --> <sample_tl_number></sample_tl_number><!-- Transportation Laboratory (TL) Number --> <lot_number_on_tl></lot_number_on_tl><!-- Inspector Lot Number from the Transportation Laboratory (TL) Form --> <structure_unique_id></structure_unique_id><!-- Structure unique identifier --> <structure_name></structure_name><!-- Structure name --> </sample_meta_data>
Child Element: <material_identification> Jump to tag definitions
material_identification is for sample's material identification information.
<material_identification> <material_source_ident></material_source_ident>*<!-- Source Identification (SMARA or name of Pit) --> <material_product_name></material_product_name><!-- The fabricator's/manufacturer's product name for the sample --> <material_designation></material_designation><!-- The fabricator/manufacturer designation for the sample --> <material_plant_number></material_plant_number><!-- The plant number --> <material_location_description></material_location_description>*<!-- A detailed description of where the material sample was collected --> <material_placement></material_placement><!-- Where the material sample would have been placed if not sampled --> <primary_aggregate_nominal_size></primary_aggregate_nominal_size>*<!-- Primary Aggregate Nominal Size --> <material_concrete_mix_num></material_concrete_mix_num><!-- The concrete mix design number --> <lot_number></lot_number><!-- Lot number --> <sublot_number></sublot_number><!-- Sublot number --> </material_identification>
Child Element:
tests element may contain any number of test results from any combinations of test methods made for this sample. However, in this page, only the AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete test result element is described, and <aashto_t_21_v_05> is the tag elment for indicating that the test result is for AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete.
<tests> <aashto_t_21_v_05> <test_meta_data></test_meta_data>*<!-- complex element, see blow--> <test_results></test_results>*<!-- complex element, see below --> <aashto_t_21_v_05> </tests>
Child Element: <test_meta_data> Jump to tag definitions
<test_meta_data> requires name_tester and date_tested, and allows for the following optional fields, result_compliance_status, result_compliance_status_comments, test_comments.
<test_meta_data> <name_tester></name_tester>*<!-- Tester's full name --> <date_tested></date_tested>*<!-- Date of test --> <test_comments></test_comments><!-- General comments (publicly viewable) (Max 1000 characters) --> <result_compliance_status></result_compliance_status><!-- Test result compliance --> <result_compliance_status_comments></result_compliance_status_comments><!-- Project test result compliance comments (Max 1000 characters) --> </test_meta_data>
Child Element: <test_results> Jump to tag definitions
<test_results> requires <data>
<test_results>
<data></data>*<!-- complex test method variation element, see below -->
</test_results>
Child Element:
<data>
<contains_impurities_AASHTOT21></contains_impurities_AASHTOT21>*<!-- Does the fine aggregate possibly contain injurious organic impurities? -->
</data>
DIMEXML Structure Treeviews
Jump to Element by Element | Jump to Tag Definitions- Aggregate_dimexml
- new_sample*Jump to tag definitions
- dime_project_id*
- sample_taken_date*
- sample_meta_data*Jump to tag definitions
- sample_received*
- sample_date_received
- sample_type_name*
- sample_constitutes*
- sample_description*
- sampler_first_name*
- sampler_last_name*
- sampler_title
- sampler_telephone
- sample_taken_from_source*
- sample_source_name*
- sample_laboratory_id
- linked_sample
- sample_tl_number
- lot_number_on_tl
- structure_unique_id
- structure_name
- material_identification*Jump to tag definitions
- sample_received*
- sample_date_received
- sample_type_name*
- sample_constitutes*
- sample_description*
- sampler_first_name*
- sampler_last_name*
- sampler_title
- sampler_telephone
- sample_taken_from_source*
- sample_source_name*
- sample_laboratory_id
- linked_sample
- sample_tl_number
- lot_number_on_tl
- structure_unique_id
- structure_name
- tests*
- aashto_t_21_v_05*
- test_meta_data*Jump to tag definitions
- name_tester*
- date_tested*
- result_compliance_status
- result_compliance_status_comments
- test_comments
- test_results * (Requires Tags from One of Test Method Variations Below) Jump to tag definitions
- data (DIMEXML template for this variation available soon)
- test_meta_data*Jump to tag definitions
- aashto_t_21_v_05*
- new_sample*Jump to tag definitions
Tag Definitions
Jump to Element by Element | Jump to Treeviewnew_sample
sample_meta_data
material_identification
test_meta_data
Test Method Variation Tables
Variation(combo tag): data
data
Label | Tag | Required? | Base Type | Value Restriction | Attribute "units" Required? | Allowed Units |
---|---|---|---|---|---|---|
Does the fine aggregate possibly contain injurious organic impurities? | contains_impurities_AASHTOT21 | Required | string | enumeration: ,Yes,No | No | N/A |
Element by Element
Jump to Treeview | Jump to Tag Definitions
Root Element:
The root element for an existing sample in Aggregate DIMEXML format is Aggregate_dimexml, and it requires two child elements, existing_sample and tests.
<Aggregate_dimexml> <existing_sample></existing_sample>*<!-- complex element. See Child Element: <existing_sample> below. --> <tests></tests>*<!-- complex element. See Child Element: <tests> below. --> </Aggregate_dimexml>*
Child Element: <existing_sample> Jump to Tag Definitions
existing_sample requires three fields, sample_project_id, sample_taken_date, sample_unique_key
<existing_sample> <sample_project_id></sample_project_id>*<!-- DIME Project ID, look it up using the DIME Project ID Lookup page at https://dime.dot.ca.gov/index.php?r=project/projectIDLookup. --> <sample_taken_date></sample_taken_date>*<!-- sample taken date, must be in date format: yyyy-mm-dd --> <sample_unique_key></sample_unique_key>*<!-- sample unique key, must be a minimum of 8 numerical characters, ie. 0-9 --> </existing_sample>*
Child Element:
tests element may contain any number of test results from any combinations of test methods made for this sample. However, in this page, only the AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete test result element is described, and <aashto_t_21_v_05> is the tag elment for indicating that the test result is for AASHTO T21-5: Standard Method of Test for Organic Impurities in Fine Aggregates for Concrete.
<tests> <aashto_t_21_v_05> <test_meta_data></test_meta_data>*<!-- complex element, see blow--> <test_results></test_results>*<!-- complex element, see below --> <aashto_t_21_v_05> </tests>
Child Element: <test_meta_data> Jump to Tag Definitions
<test_meta_data> requires name_tester and date_tested, and allows for the following optional fields, result_compliance_status, result_compliance_status_comments, test_comments.
<test_meta_data> <name_tester></name_tester>*<!-- Tester's full name --> <date_tested></date_tested>*<!-- Date of test --> <test_comments></test_comments><!-- General comments (publicly viewable) (Max 1000 characters) --> <result_compliance_status></result_compliance_status><!-- Test result compliance --> <result_compliance_status_comments></result_compliance_status_comments><!-- Project test result compliance comments (Max 1000 characters) --> </test_meta_data>
Child Element:
<test_results> requires <data>
<test_results>
<data></data>*<!-- complex test method variation element, see below -->
</test_results>
Child Element:
<data>
<contains_impurities_AASHTOT21></contains_impurities_AASHTOT21>*<!-- Does the fine aggregate possibly contain injurious organic impurities? -->
</data>
DIMEXML Structure Treeviews
Jump to Element by Element | Jump to Tag Definitions- Aggregate_dimexml
- existing_sample*Jump to Tag Definitions
- sample_project_id*
- sample_taken_date*
- sample_unique_key*
- tests*
- aashto_t_21_v_05*
- test_meta_data*Jump to Tag Definitions
- name_tester*
- date_tested*
- result_compliance_status
- result_compliance_status_comments
- test_comments
- test_results * (Requires Tags from One of Test Method Variations Below) Jump to Tag Definitions
- data (DIMEXML template for this variation available soon)
- test_meta_data*Jump to Tag Definitions
- aashto_t_21_v_05*
- existing_sample*Jump to Tag Definitions
Tag Definitions
Jump to Element by Element | Jump to Treeviewexisting_sample
test_meta_data
Test Method Variation Tables
Variation(combo tag): data
data
Label | Tag | Required? | Base Type | Value Restriction | Attribute "units" Required? | Allowed Units |
---|---|---|---|---|---|---|
Does the fine aggregate possibly contain injurious organic impurities? | contains_impurities_AASHTOT21 | Required | string | enumeration: ,Yes,No | No | N/A |