ASTM G135-95(2019)
(Guide)Standard Guide for Computerized Exchange of Corrosion Data for Metals (Withdrawn 2023)
Standard Guide for Computerized Exchange of Corrosion Data for Metals (Withdrawn 2023)
SIGNIFICANCE AND USE
4.1 This guide establishes a formalism for transferring corrosion test data between computer systems in different laboratories. It will be used by standards developers to specify the format of files containing test results.
4.2 This guide defines a generic approach to structuring data files. It will be used by software developers to create programs which read and write these files.
4.3 Each standard test procedure will define a unique data file derived from this guide. Each time a standard test is performed, the results can be summarized in a data file specific to that test.
4.4 Some experimental information will be global, that is, common to several standards, and will be contained in Guide G107 and other global data dictionaries. Other information will be local, that is, unique to a given standard, and will be defined in that standard.
SCOPE
1.1 This guide covers the techniques used to encode corrosion of metals test results for exchange between computer systems.
1.2 Guidelines are given for creating a data exchange appendix for each ASTM corrosion of metals standard.
1.3 Instructions are given for creating data translation software from the contents of the data exchange appendix.
1.4 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
WITHDRAWN RATIONALE
This guide covered the techniques used to encode corrosion of metals test results for exchange between computer systems.
Formerly under the jurisdiction of Committee G01 on Corrosion of Metals, this guide was withdrawn in December 2023. This standard is being withdrawn without replacement due to its limited use by industry.
General Information
Relations
Buy Standard
Standards Content (Sample)
This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: G135 − 95 (Reapproved 2019)
Standard Guide for
Computerized Exchange of Corrosion Data for Metals
This standard is issued under the fixed designation G135; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope 3.1.2 global data—information shared among several stan-
dards.
1.1 This guide covers the techniques used to encode corro-
sion of metals test results for exchange between computer 3.1.3 local data—information specific to a certain standard.
systems.
3.1.4 semantics—information meaning.
1.2 Guidelines are given for creating a data exchange
3.1.5 syntax—information format.
appendix for each ASTM corrosion of metals standard.
3.1.6 tagged object—a named block of information.
1.3 Instructions are given for creating data translation soft-
3.1.7 translator—a computer routine which writes or reads
ware from the contents of the data exchange appendix.
data files.
1.4 This international standard was developed in accor-
dance with internationally recognized principles on standard-
4. Significance and Use
ization established in the Decision on Principles for the
4.1 This guide establishes a formalism for transferring
Development of International Standards, Guides and Recom-
corrosion test data between computer systems in different
mendations issued by the World Trade Organization Technical
laboratories. It will be used by standards developers to specify
Barriers to Trade (TBT) Committee.
the format of files containing test results.
2. Referenced Documents
4.2 Thisguidedefinesagenericapproachtostructuringdata
files. It will be used by software developers to create programs
2.1 ASTM Standards:
which read and write these files.
G106 Practice for Verification of Algorithm and Equipment
for Electrochemical Impedance Measurements
4.3 Each standard test procedure will define a unique data
G107 Guide for Formats for Collection and Compilation of
file derived from this guide. Each time a standard test is
Corrosion Data for Metals for Computerized Database
performed, the results can be summarized in a data file specific
Input
to that test.
2.2 ANSI Standards:
4.4 Some experimental information will be global, that is,
ANSI/ISO 9899 1990 [1992] Programming Language C
common to several standards, and will be contained in Guide
ANSI X3.4-1986 Coded Character Set 7 Bit ASCII
G107andotherglobaldatadictionaries.Otherinformationwill
be local, that is, unique to a given standard, and will be defined
3. Terminology
in that standard.
3.1 Definitions:
5. Guide for Standards Authors
3.1.1 datatype—a group of rules specifying the format of an
object.
5.1 Local and Global Data:
5.1.1 Some information may be used across several corro-
sion standards, that is, global. Global data is defined in Guide
This guide is under the jurisdiction ofASTM Committee G01 on Corrosion of
G107 and other global standards.
Metals and is the direct responsibility of Subcommittee G01.05 on Laboratory
5.1.2 Some information may be local to a particular corro-
Corrosion Tests.
sion standard. Local data is defined in the standard’s data
Current edition approved Feb. 15, 2019. Published February 2019. Originally
approved in 1995. Last previous edition approved in 2013 as G135 – 95 (2013). exchange appendix.
DOI: 10.1520/G0135-95R19.
2 5.2 Data File:
For referenced ASTM standards, visit the ASTM website, www.astm.org, or
contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
5.2.1 Eachtestwillgenerateasingletestdatafile.Filename
Standards volume information, refer to the standard’s Document Summary page on
formats are not specified.
the ASTM website.
5.2.2 The data file is arranged as a set of named or tagged
Available fromAmerican National Standards Institute (ANSI), 25 W. 43rd St.,
4th Floor, New York, NY 10036, http://www.ansi.org. objects. Each time a standard test is performed a set of objects
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
G135 − 95 (2019)
is obtained. The data file can be thought of as a permanent
repository for this set of objects.
5.2.3 Each tagged object will take two or more lines in the
data file. Lines are strings of ASCII (ANSI X3.4-1986)
characters terminated with a carriage return/linefeed character
FIG. 2 The Elements of a Tagged Object
pair or a single linefeed character.
5.2.4 Lines are further subdivided into tab delimited ASCII
fields that are particularly suitable for manipulation by spread-
5.3.3.1 Each object has a datatype which specifies the
sheet and scientific charting programs. For example, Fig. 1
format of the object’s data.
shows how a section of a data file would show up on printed
5.3.3.2 Global datatypes are defined in a global data ex-
output.
change standard such as Guide G107 and are repeated here for
5.3 Tagged Object: reference, as follows:
5.3.1 Atagged object is a repository for an individual block (a) String (STRING)—Strings contain purely character in-
of information. It may be a simple piece of data, the test date formation. Strings may be further encoded depending on the
for example, or it may be complex, such as a current/voltage/ semantic description of the object.
time curve. A tagged object contains three subordinate areas: (b) Quantity (QUANT)—Quantities represent numeric val-
(1)thetag,(2)thedatatype,and(3)theactualdata.Thetagand ues along with their units. Units may be further encoded
datatype are the first two fields of the first line while the actual depending on the semantic description of the object.
data is contained in subsequent lines. Data lines are always (c) Date (DATE)—Dates are simple day specifiers.
indented one tab space. This is illustrated in Fig. 2. (d) Time (TIME)—Times are simple time of day specifiers.
5.3.2 Tag: (e) Category Set (SET)—Category sets are used to repre-
5.3.2.1 The object’s tag is a simple string that uniquely sent choices. The actual meaning of each value is given in the
identifies it among other objects in a tagged object set. semantic description of the object.
5.3.2.2 When implementing a translator for a given (f) Tabular (TABLE)—Tables are used to hold arrays of
standard, the implementation is free to define other tagged records. The datatype, units, and name of each column is also
object names so long as they don’t clash with those defined in encoded.
the standard. It is suggested that additional names be prefixed 5.3.3.3 Aparticularimplementationofatestisfreetodefine
with some unlikely and unique combination of alphanumeric local datatypes as long as they don’t clash with those defined
characters so that name conflicts do not arise in future versions in global standards. These local datatypes are defined in the
of the standard. For example; NewTest_Apex Potential. standard’s data exchange appendix.
5.3.2.3 Tags are made up of one or more character strings 5.3.3.4 The datatype has a unique identifier made up of a
separated by periods. The first character in each string must be standard number and a name separated by a period; for
alphabetic (including the underscore). Subsequent characters example, G107.SET. Each time an object is recorded in the
may be alphanumeric. data file, the datatype identifier is recorded with the object.
5.3.2.4 Periods should only be used to associate different That identifier specifies to the translator (either computer or
objects together. For example, Matl.Class, Matl.SubClass, human) what data format to use in reading the data from or
Matl.TradeName, are all aspects of Material. In future speci- writing the data to the file.
fications it is suggested that this be done using complex, 5.3.3.5 In cases where the reading translator is unable to
multifield datatypes. find a datatype in its internal table, that object will be marked
5.3.2.5 Periodsshouldnotbeusedtoseparatemultipleword as untranslated. The translator is free to take the appropriate
individual concepts. Instead use capitalization or underscore. action depending on the importance of the object.
For example; ControlMode or Control_Mode. 5.3.3.6 It is important to note that the datatype doesn’t
5.3.2.6 Tags are case insensitive although mixed case is completelyspecifythemeaningofthedata,onlyitsformat.For
suggested for readability. example, a value of one for the tag “Surface.Condition” has a
5.3.3 Datatype: very different meaning than the value of one for the tag
FIG. 1 Data File Sample
G135 − 95 (2019)
(c) Required (Column 3)—This column indicates whether a particular
“Potentiostat.ControlMode” even though they are both of type
object is required or can be safely omitted from the data file.
G107.SET. Those meanings are construed from the tag.
(d) Description (Column 4)—The description column contains free
5.3.4 Data:
form text describing the object. Constraints, defaults, or other specifica-
5.3.4.1 The object’s data is arranged in a format defined by
tions may show up here.
the datatype. Data starts in the second line of the data object.
(e) Datatype (Column 5)—The type gives the datatype of the object.
The data types may be global types defined in Guide G107, or they may
There may be multiple lines and multiple fields associated with
be local to the standard being written.
a data object. Each data line is indented by one tab space to
(f) Category Set/Units/Column Information (Column 6)—This column
distinguish it from the tag/datatype lines.
varies depending on the datatype. If the type is a SET, Column 6 contains
the allowed values and meanings. If the type is a QUANT, Column 6
5.4 Data Exchange Appendix:
contains suggested units. If the type is a TABLE, Column 6 contains units
5.4.1 Standard tests that use this guide will contain a data
or allowed values as required by the datatype of each column.
exchange appendix. This appendix contains the data and
5.4.4 The last required section of the data exchange appen-
format information required to define test data files. For an
dix is a sample data file. This should show a file as actually
example see Appendix X1.
printed although data may be omitted for the sake of space.
5.4.1.1 Thedataexchangeappendixshouldhavethreeparts,
the local datatype definitions section, the object definition
6. Guide for File Translator Programmers
table, and a sample data file.
5.4.2 The local datatype definitions section gives a descrip-
6.1 The following section is intended for programmers who
tionofandformalsyntaxforeachlocaldatatype.Thisgivesthe
are writing data exchange translators. A translator is a portion
rulesoftranslationtoprogrammerswhoarecreatingtranslators
of a program which reads or writes a data file. Production rules
for the standard.
are shown in bold-face Courier font.
5.4.2.1 The rules should be written using the formal lan-
6.1.1 Character Set—ThedataisstoredinanASCIItextfile
guage described in Section 7. The translation rules for several
which can be directly printed using most printers and manipu-
data types are given in Section 6. The QUANT type is
lated using most text editors (see Fig. 4).
reproduced in Fig. 3 as an example:
6.1.2 File—Thedatafileisarrangedasasequenceoftagged
5.4.3 The object definition table is a tabular listing of all the
objects.
objects in the file. For example, consider Table 1. There are
File : = TaggedObject [1 . .*]
four objects in this table: Standard, Date, ControlMode, and
Spectrum. In an actual standard there may be many more.
6.1.3 Tagged Object—Atagged object starts with its tag line
5.4.3.1 Each row of the table defines a data object. These and includes all the information up to the next tag. Any other
objects may be copied from global standards such as Guide
lines associated with the object must be indented one tab
G107 or may be locally defined. An object definition should character. Each line is terminated with a line feed or carriage
not refer to another standard test since a revision of that test
return/line feed pair.
may change the object definition without warning.
TaggedObject : = TagLine DataBlock
5.4.3.2 Column Definitions (as illustrated in Table 1):
6.1.3.1 Tag Line—The first line of a tagged object is called
NOTE 1—Columns 1, 2, and 3 are required for global objects. Columns
the Tag Line. It contains the tag or name of the object and the
1 to 6 are required for local objects.
format specifier.
(a) Reference Number (Column 1)—The reference number is a unique
TagLine : = TagField FormatField {CommentField} NewLine
numberreferringbacktothestandardandparagraphwherethedataobject
is defined. This number is made up of a Standard ID and a paragraph
6.1.3.2 Tag—Atagmuststartwithanalphabeticcharacteror
number separated by a period (.).
underscore ( ___ ). Thereafter numeric characters can be used
(b) Tag/Column Tag (Column 2)—This column contains the data tag. If
as well as alphabetic and underscore. Tags may not contain
the data object is tabular, this column will also contain sub-tags or
headings for each column of the object. spaces. The only other punctuation allowed is a period (.)
FIG. 3 Translation Rules for the Quant Data Object
G135 − 95 (2019)
TABLE 1 Object Definitions
Reference Number/ Category Set/Suggested Units/
Tag/Column Tag Required Description/Column Description Type/Column Type
Column Number Column Information
G107.5.1.4.1 Standard Yes Standard test specification STRING
G107.5.1.4.3 Date Yes date test started DATE
G106.X2.1 ControlMode Yes Circuit configuration SET Allowed Values
1. Potentiostat
2. Galvanostat
3. ZRA
4. V applied/No feedback
5. I applied/No feedback
6. Other
G106.X2.2 Spectrum Yes Corrected frequency spectrum TABLE
Column 1 Frequency Frequency QUANT Hz
Column 2 Signal Applied Signal QUANT V, A
Column 3 ZReal Z real QUANT ohm
Column 4 ZImag Z imaginary QUANT ohm
Column 5 StdDev Standard Deviation QUANT none
FIG. 4 Definition of the Character Set
character.Any character following a period must be alphabetic
FormatField : = {Organization Period} Standard Period Identifier Tab
or underscore. Tags are not case sensitive.
6.1.3.4 Data Lines—Any lines following the tag line up to
TagField : = Tag Tab
the next tag line are data lines associated with the tagged
Tag : = Identifier (Period Identifier) [0 . .*]
object.Aspreviouslystated,datalinesmustbeginwithatabso
Identifier : = AlphabeticChar AlphanumericChar [0 . .*]
that they may be distinguished from tag lines. The data lines
6.1.3.3 Form
...
NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
Designation: G135 − 95 (Reapproved 2019)
Standard Guide for
Computerized Exchange of Corrosion Data for Metals
This standard is issued under the fixed designation G135; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
1. Scope 3.1.2 global data—information shared among several stan-
dards.
1.1 This guide covers the techniques used to encode corro-
sion of metals test results for exchange between computer 3.1.3 local data—information specific to a certain standard.
systems.
3.1.4 semantics—information meaning.
1.2 Guidelines are given for creating a data exchange
3.1.5 syntax—information format.
appendix for each ASTM corrosion of metals standard.
3.1.6 tagged object—a named block of information.
1.3 Instructions are given for creating data translation soft-
3.1.7 translator—a computer routine which writes or reads
ware from the contents of the data exchange appendix.
data files.
1.4 This international standard was developed in accor-
dance with internationally recognized principles on standard-
4. Significance and Use
ization established in the Decision on Principles for the
4.1 This guide establishes a formalism for transferring
Development of International Standards, Guides and Recom-
corrosion test data between computer systems in different
mendations issued by the World Trade Organization Technical
laboratories. It will be used by standards developers to specify
Barriers to Trade (TBT) Committee.
the format of files containing test results.
2. Referenced Documents
4.2 This guide defines a generic approach to structuring data
files. It will be used by software developers to create programs
2.1 ASTM Standards:
which read and write these files.
G106 Practice for Verification of Algorithm and Equipment
for Electrochemical Impedance Measurements
4.3 Each standard test procedure will define a unique data
G107 Guide for Formats for Collection and Compilation of
file derived from this guide. Each time a standard test is
Corrosion Data for Metals for Computerized Database
performed, the results can be summarized in a data file specific
Input
to that test.
2.2 ANSI Standards:
4.4 Some experimental information will be global, that is,
ANSI/ISO 9899 1990 [1992] Programming Language C
common to several standards, and will be contained in Guide
ANSI X3.4-1986 Coded Character Set 7 Bit ASCII
G107 and other global data dictionaries. Other information will
be local, that is, unique to a given standard, and will be defined
3. Terminology
in that standard.
3.1 Definitions:
5. Guide for Standards Authors
3.1.1 datatype—a group of rules specifying the format of an
object.
5.1 Local and Global Data:
5.1.1 Some information may be used across several corro-
sion standards, that is, global. Global data is defined in Guide
This guide is under the jurisdiction of ASTM Committee G01 on Corrosion of G107 and other global standards.
Metals and is the direct responsibility of Subcommittee G01.05 on Laboratory
5.1.2 Some information may be local to a particular corro-
Corrosion Tests.
sion standard. Local data is defined in the standard’s data
Current edition approved Feb. 15, 2019. Published February 2019. Originally
exchange appendix.
approved in 1995. Last previous edition approved in 2013 as G135 – 95 (2013).
DOI: 10.1520/G0135-95R19.
2 5.2 Data File:
For referenced ASTM standards, visit the ASTM website, www.astm.org, or
contact ASTM Customer Service at service@astm.org. For Annual Book of ASTM
5.2.1 Each test will generate a single test data file. File name
Standards volume information, refer to the standard’s Document Summary page on
formats are not specified.
the ASTM website.
3 5.2.2 The data file is arranged as a set of named or tagged
Available from American National Standards Institute (ANSI), 25 W. 43rd St.,
4th Floor, New York, NY 10036, http://www.ansi.org. objects. Each time a standard test is performed a set of objects
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
G135 − 95 (2019)
is obtained. The data file can be thought of as a permanent
repository for this set of objects.
5.2.3 Each tagged object will take two or more lines in the
data file. Lines are strings of ASCII (ANSI X3.4-1986)
characters terminated with a carriage return/linefeed character
FIG. 2 The Elements of a Tagged Object
pair or a single linefeed character.
5.2.4 Lines are further subdivided into tab delimited ASCII
fields that are particularly suitable for manipulation by spread-
5.3.3.1 Each object has a datatype which specifies the
sheet and scientific charting programs. For example, Fig. 1
format of the object’s data.
shows how a section of a data file would show up on printed
5.3.3.2 Global datatypes are defined in a global data ex-
output.
change standard such as Guide G107 and are repeated here for
5.3 Tagged Object: reference, as follows:
5.3.1 A tagged object is a repository for an individual block (a) String (STRING)—Strings contain purely character in-
of information. It may be a simple piece of data, the test date formation. Strings may be further encoded depending on the
for example, or it may be complex, such as a current/voltage/ semantic description of the object.
time curve. A tagged object contains three subordinate areas: (b) Quantity (QUANT)—Quantities represent numeric val-
(1) the tag, (2) the datatype, and (3) the actual data. The tag and ues along with their units. Units may be further encoded
datatype are the first two fields of the first line while the actual depending on the semantic description of the object.
data is contained in subsequent lines. Data lines are always (c) Date (DATE)—Dates are simple day specifiers.
indented one tab space. This is illustrated in Fig. 2. (d) Time (TIME)—Times are simple time of day specifiers.
5.3.2 Tag: (e) Category Set (SET)—Category sets are used to repre-
5.3.2.1 The object’s tag is a simple string that uniquely sent choices. The actual meaning of each value is given in the
identifies it among other objects in a tagged object set. semantic description of the object.
5.3.2.2 When implementing a translator for a given (f) Tabular (TABLE)—Tables are used to hold arrays of
standard, the implementation is free to define other tagged records. The datatype, units, and name of each column is also
object names so long as they don’t clash with those defined in encoded.
the standard. It is suggested that additional names be prefixed 5.3.3.3 A particular implementation of a test is free to define
with some unlikely and unique combination of alphanumeric local datatypes as long as they don’t clash with those defined
characters so that name conflicts do not arise in future versions in global standards. These local datatypes are defined in the
of the standard. For example; NewTest_Apex Potential. standard’s data exchange appendix.
5.3.2.3 Tags are made up of one or more character strings 5.3.3.4 The datatype has a unique identifier made up of a
separated by periods. The first character in each string must be standard number and a name separated by a period; for
alphabetic (including the underscore). Subsequent characters example, G107.SET. Each time an object is recorded in the
may be alphanumeric. data file, the datatype identifier is recorded with the object.
5.3.2.4 Periods should only be used to associate different That identifier specifies to the translator (either computer or
objects together. For example, Matl.Class, Matl.SubClass, human) what data format to use in reading the data from or
Matl.TradeName, are all aspects of Material. In future speci- writing the data to the file.
fications it is suggested that this be done using complex, 5.3.3.5 In cases where the reading translator is unable to
multifield datatypes. find a datatype in its internal table, that object will be marked
5.3.2.5 Periods should not be used to separate multiple word as untranslated. The translator is free to take the appropriate
individual concepts. Instead use capitalization or underscore. action depending on the importance of the object.
For example; ControlMode or Control_Mode. 5.3.3.6 It is important to note that the datatype doesn’t
5.3.2.6 Tags are case insensitive although mixed case is completely specify the meaning of the data, only its format. For
suggested for readability. example, a value of one for the tag “Surface.Condition” has a
5.3.3 Datatype: very different meaning than the value of one for the tag
FIG. 1 Data File Sample
G135 − 95 (2019)
(c) Required (Column 3)—This column indicates whether a particular
“Potentiostat.ControlMode” even though they are both of type
object is required or can be safely omitted from the data file.
G107.SET. Those meanings are construed from the tag.
(d) Description (Column 4)—The description column contains free
5.3.4 Data:
form text describing the object. Constraints, defaults, or other specifica-
5.3.4.1 The object’s data is arranged in a format defined by
tions may show up here.
the datatype. Data starts in the second line of the data object. (e) Datatype (Column 5)—The type gives the datatype of the object.
The data types may be global types defined in Guide G107, or they may
There may be multiple lines and multiple fields associated with
be local to the standard being written.
a data object. Each data line is indented by one tab space to
(f) Category Set/Units/Column Information (Column 6)—This column
distinguish it from the tag/datatype lines.
varies depending on the datatype. If the type is a SET, Column 6 contains
the allowed values and meanings. If the type is a QUANT, Column 6
5.4 Data Exchange Appendix:
contains suggested units. If the type is a TABLE, Column 6 contains units
5.4.1 Standard tests that use this guide will contain a data
or allowed values as required by the datatype of each column.
exchange appendix. This appendix contains the data and
5.4.4 The last required section of the data exchange appen-
format information required to define test data files. For an
dix is a sample data file. This should show a file as actually
example see Appendix X1.
printed although data may be omitted for the sake of space.
5.4.1.1 The data exchange appendix should have three parts,
the local datatype definitions section, the object definition
6. Guide for File Translator Programmers
table, and a sample data file.
5.4.2 The local datatype definitions section gives a descrip-
6.1 The following section is intended for programmers who
tion of and formal syntax for each local datatype. This gives the
are writing data exchange translators. A translator is a portion
rules of translation to programmers who are creating translators
of a program which reads or writes a data file. Production rules
for the standard.
are shown in bold-face Courier font.
5.4.2.1 The rules should be written using the formal lan-
6.1.1 Character Set—The data is stored in an ASCII text file
guage described in Section 7. The translation rules for several
which can be directly printed using most printers and manipu-
data types are given in Section 6. The QUANT type is
lated using most text editors (see Fig. 4).
reproduced in Fig. 3 as an example:
6.1.2 File—The data file is arranged as a sequence of tagged
5.4.3 The object definition table is a tabular listing of all the
objects.
objects in the file. For example, consider Table 1. There are
File : = TaggedObject [1 . .*]
four objects in this table: Standard, Date, ControlMode, and
Spectrum. In an actual standard there may be many more. 6.1.3 Tagged Object—A tagged object starts with its tag line
5.4.3.1 Each row of the table defines a data object. These
and includes all the information up to the next tag. Any other
objects may be copied from global standards such as Guide lines associated with the object must be indented one tab
G107 or may be locally defined. An object definition should
character. Each line is terminated with a line feed or carriage
not refer to another standard test since a revision of that test return/line feed pair.
may change the object definition without warning.
TaggedObject : = TagLine DataBlock
5.4.3.2 Column Definitions (as illustrated in Table 1):
6.1.3.1 Tag Line—The first line of a tagged object is called
NOTE 1—Columns 1, 2, and 3 are required for global objects. Columns
the Tag Line. It contains the tag or name of the object and the
1 to 6 are required for local objects.
format specifier.
(a) Reference Number (Column 1)—The reference number is a unique
TagLine : = TagField FormatField {CommentField} NewLine
number referring back to the standard and paragraph where the data object
is defined. This number is made up of a Standard ID and a paragraph
6.1.3.2 Tag—A tag must start with an alphabetic character or
number separated by a period (.).
underscore ( ___ ). Thereafter numeric characters can be used
(b) Tag/Column Tag (Column 2)—This column contains the data tag. If
as well as alphabetic and underscore. Tags may not contain
the data object is tabular, this column will also contain sub-tags or
headings for each column of the object. spaces. The only other punctuation allowed is a period (.)
FIG. 3 Translation Rules for the Quant Data Object
G135 − 95 (2019)
TABLE 1 Object Definitions
Reference Number/ Category Set/Suggested Units/
Tag/Column Tag Required Description/Column Description Type/Column Type
Column Number Column Information
G107.5.1.4.1 Standard Yes Standard test specification STRING
G107.5.1.4.3 Date Yes date test started DATE
G106.X2.1 ControlMode Yes Circuit configuration SET Allowed Values
1. Potentiostat
2. Galvanostat
3. ZRA
4. V applied/No feedback
5. I applied/No feedback
6. Other
G106.X2.2 Spectrum Yes Corrected frequency spectrum TABLE
Column 1 Frequency Frequency QUANT Hz
Column 2 Signal Applied Signal QUANT V, A
Column 3 ZReal Z real QUANT ohm
Column 4 ZImag Z imaginary QUANT ohm
Column 5 StdDev Standard Deviation QUANT none
FIG. 4 Definition of the Character Set
character. Any character following a period must be alphabetic
FormatField : = {Organization Period} Standard Period Identifier Tab
or underscore. Tags are not case sensitive.
6.1.3.4 Data Lines—Any lines following the tag line up to
TagField : = Tag Tab
the next tag line are data lines associated with the tagged
Tag : = Identifier (Period Identifier) [0 . .*]
object. As previously stated, data lines must begin with a tab so
Identifier : = AlphabeticChar AlphanumericChar [0 . .*]
th
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.