ASTM-E3077 2017

ASTM E3077

Scope

Keywords

eData transfer; material; suppliers

XML Element NameType of TagReq’dOccurrencesField TypeDescription<?xml version=“1.0” encoding=“UTF-8” standalone=“yes” ?>XML DeclarationYes1Declare this is a XML file (hardcode).<ASTMeDataXchange xmlns=“https://staging.astm.org/e55edataxchange.html”>†Section StartYes1The default namespace https://staging.astm.org/e55edataxchange.html† is specific to this guide and prevents collisions with element names in other namespaces.<FileInformation>Section StartYes1Contains information on the XML file, one per XML file. The version attribute shall be set to 1.0 (for example, version=“1.0”) to indicate the version of this guide to which the eData document conforms. <EndUserSystemVersion />FieldNoNumericTo track changes at end user systems. End user will provide the version number to Supplier to populate. This field will remain the same until the end user communicates an update to the Supplier. Version of this field does not affect the FileInformation or the ContentRevision versions.<FilePartyEmail />FieldNoAlphae-mail address for questions related to the file information and format of the XML document.<DataPartyEmail />FieldNoAlphae-mail address for questions related to the eData content.<GenerationDate />FieldYesYYYY-MM-DDDate when the XML file was generated in accordance with ISO 8601extended format.<GenerationTime />FieldYesHH:MM:SSZTime when the XML file was generated (UTC) in accordance with ISO 8601extended format.<ContentRevision />FieldYesNumericUsed to track the information content revision as agreed in a contract between a specific Supplier and an end user.<Signature>Section StartNoThis field is an optional enveloped digital signature. If a digital signature is provided, it must conform to XML Signature Syntax and Processing, in particular the schema xmlsig-core-schema.xsd. In order to ensure broad interoperability, Suppliers must use either the DSA with SHA1 algorithm or the HMAC-SHA1 algorithm. Signers must apply the Enveloped Signature transform and either Canonical XML 1.0 (omits comments) transform or Canonical XML 1.1 (omits comments) transform to the eData document prior to computing the signature. This guide does not indicate how Suppliers should transmit a message authentication code (MAC—like a password, for HMAC-SHA1) or a public key (for DSA) to Customers. Suppliers using the DSA algorithm must include KeyInfo element with at least the DSAKeyValue element specified to facilitate verification by Customers. Only one signature is permitted. Customers shall accept any digital signature conforming to the above requirements.</Signature>Section EndNoEnd Tag.</FileInformation>Section EndYesEnd Tag.<MaterialDataGroup>Section StartYes1Section of material information and data results.<Comments />FieldYesAlphaFor Suppliers to enter comments.<MaterialData>Section StartYesMay occur multiple times within the <MaterialDataGroup> section. Each certificate contains results for one material.Each MaterialDataGroup has a “MaterialDataLotID” attribute, which is referenced by the MaterialData to keep the integrity of the file using Attribute: name=“MaterialDataLotRef”. type=“IDREF”Attribute: name=“MaterialDataLotID” type=“ID”. Each MaterialData has an attribute that references the MaterialDataLotID for this MaterialData.<QualitySignature />FieldNoAlphaTo include name of the Quality sign off.<Manufacturer />FieldYesAlphaName of the manufacturer of this material/sometimes for S-1 supplier, can be distributor name if the manufacturer name is not available.Attribute: name=“Type” type=“string”. Values = Distributor, Manufacturer; default = “Manufacturer”; This Distributor versus Manufacturer attribute is required.Attribute: name=“Level” type=“int”. Manufacturing Level relative to eData receiving (that is, direct supplier = 0, supplier’s component supplier = 1), default to direct supplier. This Attribute is required. Level 0 data is required for every data file.Attribute: name=“Plant” type=“string”. Plant code or name where this material was manufactured. This attribute is optional.<ProductName />FieldYesAlphaProduct Name.<PartNumber />FieldYesAlphaProduct Part/Material Number.<Lot />FieldYesAlphaLot number Attribute: name=“LotDate” type=”“date” format=“YYYY-MM-DD”. This attribute is required.Attribute: name=“ManufactureReceive” type=“string” Values = “MfgDate”, “ReceiveDate” default=“MfgDate” ; This attribute refers to lot received date or lot manufacture date. This attribute is optional.Attribute: name=“ExpDate” type=“date” format=“YYYY-MM-DD”. Supplier’s lot expiration date. This attribute is optional.<Quantity />FieldNoNumericQuantity of the lot in numeric format.<QuantityUOM />FieldNoAlphaUnit of measure for the quantity.<MaterialParameters>Section StartNo11 occurrence per <MaterialData>, contains material data results.<MaterialParameter>Section StartNo*May occur multiple times within the <MaterialData> section.<Name />FieldYesAlphaShort test/assay description name.<Description />FieldNoAlphaLong test/assay description name.<MeasurementAttribute />FieldNoAlphaTest or Attribute of a material or component (for example, pH, purity, outside diameter). Note: May be similar/same as Short Name.<MeasurementVariable />FieldNoAlphaVariable used to differentiate multiple variables measured on the same attribute (for example, minimum, maximum, mean).<UnitOfMeasure />FieldNoAlphaUnit of measure.<Method />FieldNoAlphaMeasurement method used by the supplier.<MeasurementType />FieldNoAlphaMeasurement type (EQ/LT/LTE/GT/GTE). Used in conjunction with the MeasurementValue field<MeasurementValue />FieldNoNumericMeasurement numeric value (numeric values are only accepted).<MeasurementText />FieldNoAlphaMeasured value with symbols as it appears on the CoA or data result, since the “<” symbol may be used in this field Character Data (CDATA) may appear.<MeasurementTestLot />FieldNoAlphaIdentifier for test execution lot, to track information regarding different test lots.<SpecificationNumber />FieldNoAlphaSpecification number related to the material at the end user if available.<Specification />FieldNoAlphaSpecifications as it appears on the CoA (that is, Range or “>” or “<” symbols); if symbol is used in this field CDATA may appear.<SampleLocation />FieldNoAlphaIf more than one measurement of the same type occurs, this field can be used to specify where in the process the measurement occurred.</MaterialParameter>Section EndYesEnd Tag.</MaterialParameters>Section EndYesEnd Tag.</MaterialData>Section EndYesEnd Tag.</MaterialDataGroup>Section EndYesEnd Tag.</ASTMeDataXchange>Section EndYesEnd Tag.† Editorially corrected. ;

ICS Code

ICS Number Code 35.240.63 (IT applications in trade)

DOI: 10.1520/E3077-17E01