SIST EN 61499-2:2006
(Main)Function blocks -- Part 2: Software tools requirements
Function blocks -- Part 2: Software tools requirements
This part of IEC 61499 defines requirements for software tools to support the following systems engineering tasks enumerated in Clause 1 of IEC 61499-1: - the specification of function block types; - the functional specification of resource types and device types; - the specification, analysis, and validation of distributed IPMCSs; - the configuration, implementation, operation, and maintenance of distributed IPMCSs; - the exchange of information among software tools. It is assumed that such software tools may be used in the context of an Engineering Support System (ESS) as described in Clause C.1 of IEC 61499-1. It is beyond the scope of this part of IEC 61499 to specify the entire life cycle of industrialprocess measurement and control systems (IPMCSs), or the entire set of tasks and activities required to support an IPCMS over its life cycle. However, other standards which do specify such tasks and activities may extend or modify the requirements specified in this Part.
Funktionsbausteine für industrielle Leitsysteme -- Teil 2: Anforderungen an Software-Werkzeuge
Blocs fonctionnels -- Partie 2: Spécifications des outils logiciels
the specification of function block types; -the specification, analysis, and validation of distributed IPMCSs; -the exchange of information among software tools.
Funkcijski bloki - 2. del: Zahteve za programska orodja (IEC 61499-2:2005)
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Funkcijski bloki - 2. del: Zahteve za programska orodja (IEC 61499-2:2005)Funktionsbausteine für industrielle Leitsysteme -- Teil 2: Anforderungen an Software-WerkzeugeBlocs fonctionnels -- Partie 2: Spécifications des outils logicielsFunction blocks -- Part 2: Software tools requirements35.240.50Uporabniške rešitve IT v industrijiIT applications in industry35.080Dokumentiranje razvoja programske opreme in sistemov (sistemska dokumentacija)Software development and system documentation25.040.40Merjenje in krmiljenje industrijskih postopkovIndustrial process measurement and controlICS:Ta slovenski standard je istoveten z:EN 61499-2:2005SIST EN 61499-2:2006en01-januar-2006SIST EN 61499-2:2006SLOVENSKI
STANDARD
SIST EN 61499-2:2006
EUROPEAN STANDARD
EN 61499-2 NORME EUROPÉENNE EUROPÄISCHE NORM
August 2005 CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung
Central Secretariat: rue de Stassart 35, B - 1050 Brussels
© 2005 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 61499-2:2005 E
ICS 25.040.40; 35.240.50
English version
Function blocks Part 2: Software tools requirements (IEC 61499-2:2005)
Blocs fonctionnels Partie 2: Spécifications des outils logiciels(CEI 61499-2:2005)
Funktionsbausteine für industrielle Leitsysteme Teil 2: Anforderungen an Software-Werkzeuge (IEC 61499-2:2005)
This European Standard was approved by CENELEC on 2005-06-01. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions.
CENELEC members are the national electrotechnical committees of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
SIST EN 61499-2:2006
EN 61499-2:2005 - 2 - Foreword The text of the International Standard IEC 61499-2:2005, prepared by IEC TC 65, Industrial-process measurement and control, was submitted to the formal vote and was approved by CENELEC as EN 61499-2 on 2005-06-01 without any modification. The following dates were fixed: – latest date by which the EN has to be implemented
at national level by publication of an identical
national standard or by endorsement
(dop) 2006-06-01 – latest date by which the national standards conflicting
with the EN have to be withdrawn
(dow) 2008-06-01 Annex ZA has been added by CENELEC. __________ Endorsement notice The text of the International Standard IEC 61499-2:2005 was approved by CENELEC as a European Standard without any modification. __________ SIST EN 61499-2:2006
- 3 - EN 61499-2:2005
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. NOTE Where an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies. Publication Year Title EN/HD Year IEC 61499-1 - 1) Function blocks Part 1: Architecture
EN 61499-1 2005 2) IEC 61499-4 - 3) Part 4: Rules for compliance profiles
EN 61499-4 - 3)
The normative references given in EN 61499-1 apply to this part of EN 61499.
1) Undated reference. 2) Valid edition at date of issue. 3) To be published. SIST EN 61499-2:2006
SIST EN 61499-2:2006
INTERNATIONAL STANDARD IEC61499-2 First edition2005-01 Function blocks – Part 2: Software tools requirements
IEC 2005
Copyright - all rights reserved No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher. International Electrotechnical Commission,
3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, SwitzerlandTelephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch
Web: www.iec.ch X For price, see current catalogue PRICE CODE
Commission Electrotechnique InternationaleInternational Electrotechnical Commission
SIST EN 61499-2:2006
– 2 – 61499-2 © IEC:2005(E) CONTENTS FOREWORD.3
1 Scope.6 2 Normative references.6 3 Terms and definitions.6 4 Software tool requirements.7 4.1 Information to be provided by the software tool supplier.7 4.2 Exchange of library elements.7 4.3 Information to be provided by the supplier of library elements.7 4.4 Display of declarations.8 4.5 Modification of declarations.8 4.6 Validation of declarations.8 4.7 Implementation of declarations.8 4.8 System operation, testing and maintenance.8
Annex A (normative)
Document Type Definitions (DTDs).9 Annex B (informative)
Graphics model.25 Annex C (informative)
Examples.28
Figure B.1 – Graphics model.25 Figure B.2 – ECC drawing example.27
Table A.1 – Document Type Definition (DTD) elements.9 Table A.2 – DataType DTD.10 Table A.3 – DataType DTD Elements.11 Table A.4 – Library Element DTD.14 Table A.5 – LibraryElement DTD Elements.19
SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 3 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION ____________
FUNCTION BLOCKS –
Part 2: Software tool requirements
FOREWORD 1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is indispensable for the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights. International Standard IEC 61499-2 has been prepared by IEC technical committee 65: Industrial-process measurement and control. This standard cancels and replaces IEC/PAS 61499-2 published in 2001. This first edition constitutes a technical revision. The following major technical changes have occurred between the PAS edition and this edition: a) Syntax for network segments, links and parameters has been added in Annex A for consistency with IEC 61499-1. b) Syntax for parameters instead of constant data connections has been included for consistency with IEC 61499-1. SIST EN 61499-2:2006
– 4 – 61499-2 IEC:2005(E) The text of this standard is based on the following documents: CDV Report on voting 65/339/CDV 65/347/RVC
Full information on the voting for the approval of this standard can be found in the report on voting indicated in the above table. This publication has been drafted in accordance with the ISO/IEC Directives, Part 2. IEC 61499 consists of the following parts, under the general title Function blocks: Part 1: Architecture
Part 2: Software tool requirements
Part 3: Tutorial information Part 4: Rules for compliance profiles
1 The committee has decided that the contents of this publication will remain unchanged until the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in the data related to the specific publication. At this date, the publication will be
• reconfirmed; • withdrawn; • replaced by a revised edition, or • amended. A bilingual version of this standard may be issued at a later date. ——————— 1 Under consideration. SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 5 –
INTRODUCTION The IEC 61499 series consists of four Parts: • Part 1 contains: – general requirements, including an introduction, scope, normative references, definitions, and reference models; – rules for the declaration of function block types, and rules for the behaviour of instances of the types so declared; – rules for the use of function blocks in the configuration of distributed Industrial-Process Measurement and Control Systems (IPMCSs); – rules for the use of function blocks in meeting the communication requirements of distributed IPMCSs; – rules for the use of function blocks in the management of applications, resources and devices in distributed IPMCSs. • Part 2 (this part of IEC 61499) defines requirements for software tools to support the following systems engineering tasks enumerated in Clause 1 of IEC 61499-1: - the specification of function block types; - the functional specification of resource types and device types; - the specification, analysis, and validation of distributed IPMCSs; - the configuration, implementation, operation, and maintenance of distributed IPMCSs; - the exchange of information among software tools. It is assumed that such software tools may be used in the context of an Engineering Support System (ESS) as described in Clause C.1 of IEC 61499-1. • Part 3 has the purpose of increasing the understanding, acceptance, and both generic and domain-specific applicability of IPMCS architectures and software tools meeting the requirements of the other Parts, by providing: - answers to Frequently Asked Questions (FAQs) regarding the IEC 61499 series; - examples of the use of IEC 61499 constructs to solve frequently encountered problems in control and automation engineering. • Part 4 defines rules for the development of compliance profiles which specify the features of IEC 61499-1 and 61499-2 to be implemented in order to promote the following attributes of IEC 61499-based systems, devices and software tools: - interoperability of devices from multiple suppliers; - portability of software between software tools of multiple suppliers; and
- configurability of devices from multiple vendors by software tools of multiple suppliers. SIST EN 61499-2:2006
– 6 – 61499-2 IEC:2005(E) FUNCTION BLOCKS –
Part 2: Software tool requirements
1 Scope
This part of IEC 61499 defines requirements for software tools to support the following systems engineering tasks enumerated in Clause 1 of IEC 61499-1: – the specification of function block types; – the functional specification of resource types and device types; – the specification, analysis, and validation of distributed IPMCSs; – the configuration, implementation, operation, and maintenance of distributed IPMCSs; – the exchange of information among software tools. It is assumed that such software tools may be used in the context of an Engineering Support System (ESS) as described in Clause C.1 of IEC 61499-1. It is beyond the scope of this part of IEC 61499 to specify the entire life cycle of industrial-process measurement and control systems (IPMCSs), or the entire set of tasks and activities required to support an IPCMS over its life cycle. However, other standards which do specify such tasks and activities may extend or modify the requirements specified in this Part. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC 61499-1, Function blocks - Part 1: Architecture
IEC 61499-4, Function Blocks - Part 4: Rules for compliance profiles2
The normative references given in IEC 61499-1 apply to this part of IEC 61499. 3 Terms and definitions For the purposes of this document, the terms and definitions given in IEC 61499-1 as well as the following apply. 3.1
library element collection of declarations applying to a data type, function block type, adapter type, subapplication type, resource type, device type, or system configuration. ——————— 2 To be published. SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 7 –
4 Software tool requirements 4.1 Information to be provided by the software tool supplier This Clause defines the functional requirements of software tools that support the performance of the systems engineering tasks enumerated in Clause 1. The supplier of a software tool shall specify the following information in addition to other information required in this Clause: a) The type or types of library element to which the software tool applies. b) The engineering task or tasks supported by the software tool.
Task descriptions may be taken from the enumeration of engineering tasks given in Clause 1, or may be defined by the supplier. 4.2 Exchange of library elements A software tool shall be capable of exchanging its library elements with other software tools. This exchange shall take the form of data in the format defined in Annex A, written on physical media or exchanged over communication links or networks. 4.3 Information to be provided by the supplier of library elements NOTE The provisions of this subclause are intended to provide the means by which the provider of a library element may achieve protection of intellectual property while still providing sufficient information to permit the effective use of the library element. The provider of a library element may elect to provide an implementation of the library element. EXAMPLE 1 The provider of a function block type library element may provide an implementation of the function block type as: • one or more instances of the function block type in a resource contained in a device of Class 0 or higher as described in IEC 61499-4; • an instantiable implementation of the function block type in a resource contained in a device of Class 1 or higher as described in IEC 61499-4; • a file in an implementation-dependent format suitable for installation in a resource contained in a device of Class 2 as described in IEC 61499-4, for instance using an XML syntax which may be defined in a compliance profile developed according to the rules given in IEC 61499-4. When an implementation of a library element is provided, the provider is not required to provide full details of the implementation. However, the provider shall provide sufficient information to enable the user to fully determine the functionality of the provided library element. EXAMPLE 2 The requirement of the above paragraph would be met by the provider of an instance of a function block type in a resource through the provision, at a minimum, of the following information: • a function block type library element specifying its event and data interfaces as defined in IEC 61499-1, 5.2.1, and its services as defined in IEC 61499-1, 6.1.3; • resource type and device type library elements showing the occurrence and connections of the function block instances. SIST EN 61499-2:2006
– 8 – 61499-2 IEC:2005(E) 4.4 Display of declarations A software tool shall be capable of displaying the declarations of its associated library elements in a form appropriate to the engineering task. This display may utilize the graphical or textual formats defined in IEC 61499-1, or a format defined by the supplier of the software tool. NOTE The declarations of a library element may define its interfaces (event and data inputs and outputs) and internal variables as well as its algorithms and the control of their execution, for example via
an execution control chart (ECC), etc. 4.5 Modification of declarations A software tool shall enable its user to modify the declarations of its associated library elements as appropriate to the engineering task. Such modifications may include adding, deleting or changing the contents of declarations, and may be performed either graphically or textually or both. 4.6 Validation of declarations If required by the associated engineering task, a software tool shall provide facilities for validation of the declarations of its associated library elements. Such facilities may include, but are not limited to: a) Checking the correctness of the syntax of declarations. b) Checking the semantic correctness of declarations, for instance, checking whether all function block instances in an application and its associated subapplications are properly allocated to resources, interconnected within resources, and intercommunicating among resources in a system configuration. c) Simulation and testing of the operation of an instance of a library element type, either by itself or in association with other instances of the same or different types. 4.7 Implementation of declarations If required by the associated engineering task, a software tool shall provide facilities for the implementation of the declarations of its associated library elements. Such facilities may include, but are not limited to: a) The production of executable code ("firmware") for embedding in instances of resource types and device types. b) The creation and interconnection ("downloading") of function block instances in resources and devices, for instance by using the management facilities defined in subclause 3.3 and Annexes F and G of IEC 61499-1. 4.8 System operation, testing and maintenance If required by the associated engineering task, a software tool shall provide facilities for the operation, testing and maintenance of an Industrial Process Measurement and Control System (IPMCS) specified by its associated library elements. Such facilities may include, but are not limited to: a) The facilities described in preceding subclauses of this Clause. b) The information exchange facilities defined in subclause 6.2 and Annex F of IEC 61499-1. SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 9 –
Annex A
(normative)
Document Type Definitions (DTDs)
A.1 General principles This Annex presents Document Type Definitions (DTDs) for the exchange of IEC 61499 library elements between software tools. These DTDs are defined in the syntax defined in the eXtensible Markup Language (XML) specification (see www.w3.org/TR/2000/REC-xml-20001006). The correspondences between the DTD elements given in this Annex, the library elements defined in IEC 61499-1, C.2.2,
and the textual syntax given in IEC 61499-1, Annex B are given in Table A.1. Table A.1 – Document Type Definition (DTD) elements DTD element LibraryElement Textual syntax DataType DataTypeDeclaration data_type_declaration (IEC 61131-3-B.1.3) FBType FBTypeDeclaration fb_type_declaration SubapplicationType SubapplicationTypeDeclaration subapplication_type_ declaration AdapterType AdapterTypeDeclaration adapter_type_declarationResourceType ResourceTypeDeclaration resource_type_ specification DeviceType DeviceTypeDeclaration device_type_specificationSystem SystemConfiguration system_configuration
The first table of each subclause of this Annex contains the DTD for the corresponding library element. The second table of each subclause provides a reference to the textual syntax (if any) plus an explanation for the major elements and attributes in the DTD. Following this, examples are given of the resulting XML files for typical library elements. If there is a conflict between the provisions of this Annex and the provisions of Annex B of IEC 61499-1, the provisions of the latter shall prevail. NOTE 1 The examples given in this Annex provide a representative but not exhaustive sample of the features of the associated DTDs. In particular, these examples are not intended to be used as a test suite for compliance to the provisions of this part of IEC 61499. A.2 DataType DTD An XML document complying with the DTD in Table A.2 represents a DataTypeDeclaration object as described in Clause C.1 of IEC 61499-1. SIST EN 61499-2:2006
– 10 – 61499-2 IEC:2005(E) Table A.2 – DataType DTD
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>
Standard CDATA #IMPLIED
Classification CDATA #IMPLIED
ApplicationDomain CDATA #IMPLIED
Function CDATA #IMPLIED
Type CDATA #IMPLIED
Description CDATA #IMPLIED>
Organization CDATA #REQUIRED
Version CDATA #REQUIRED
Author CDATA #REQUIRED
Date CDATA #REQUIRED
Remarks CDATA #IMPLIED>
Class (UNIVERSAL | APPLICATION | CONTEXT | PRIVATE) #IMPLIED
Number CDATA #REQUIRED>
header CDATA #IMPLIED
classdef CDATA #IMPLIED>
Language (Java | Cpp | C | Other) #REQUIRED
Vendor CDATA #REQUIRED
Product CDATA #REQUIRED
Version CDATA #REQUIRED>
BaseType (BOOL | SINT | INT | DINT | LINT | USINT | UINT | UDINT | ULINT | REAL | LREAL | TIME | DATE | TIME_OF_DAY | TOD | DATE_AND_TIME | DT | STRING | BYTE |WORD | DWORD |LWORD | WSTRING)
#REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
Name CDATA #REQUIRED
Comment CDATA #IMPLIED>
BaseType (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED> SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 11 –
Table A.2 – DataType DTD
LowerLimit CDATA #REQUIRED
UpperLimit CDATA #REQUIRED>
BaseType CDATA #REQUIRED
InitialValues CDATA #IMPLIED
Comment CDATA #IMPLIED>
Comment CDATA #IMPLIED>
Name CDATA #REQUIRED
Type CDATA #REQUIRED
ArraySize CDATA #IMPLIED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
Name CDATA #REQUIRED
Type (SINT|INT|DINT|LINT|USINT|UINT|UDINT|ULINT) #REQUIRED
InitialValue CDATA #IMPLIED
Comment CDATA #IMPLIED>
Explanations of the elements of the DTD given in Table A.2, and (where applicable) references to the formal syntax for their attributes, are given in Table A.3.
Table A.3 – DataType DTD elements Element attributes Textual syntax (IEC 61131-3, Annex B) Explanation DataType
See IEC 61131-3
Name data_type_name
Comment -- A comment as per IEC 61131-3 without (* and *) delimiters Identification
Information for data base retrieval
Standard Primary reference standard in number-part-subclause format
Classification Classification code as defined in reference standard
ApplicationDomain Application domain as defined in reference standard
Function Function of this element as defined in reference standard
Type Element type (e.g., device type) as defined in reference standard
Description Descriptive phrase as defined in reference standard SIST EN 61499-2:2006
– 12 – 61499-2 IEC:2005(E) Table A.3 – DataType DTD elements Element attributes Textual syntax (IEC 61131-3, Annex B) Explanation VersionInfo -- Possibly one of several entries: First entry – Most recent version Second entry – Immediately preceding released version, etc. last entry – First released version
Organization -- The organization supplying this library element
Version digit [digit] '.' digit [digit] [letter] The Version identification for this library element
Author -- The author of this library element
Date date_literal ['-' daytime] The release date of this version
Remarks -- Comments relating to this version ASN1Tag ASN.1 tag per ISO/IEC 8824-1
Class ASN.1 tag class per ISO/IEC 8824-1
Number ASN.1 tag number per ISO/IEC 8824-1 CompilerInfo -- Information for and about compilers used with this class
header -- Header information such as package, imports, etc.
classdef -- The class definition information such as superclass and implemented interfaces.
If none is given, a default abstract superclass is used. Compiler -- Possibly one of several compilers used with this version
Language -- The source language of this compiler
Vendor -- The vendor of this compiler
Product -- The product name of this compiler
Version -- The version of this compiler DirectlyDerivedType See IEC 61131-3, Tables 12 and 14, #1
BaseType elementary_type_name
InitialValue constant
Comment A comment as per IEC 61131-3 without (* and *) delimiters EnumeratedType See IEC 61131-3, Tables 12 and 14, #2
InitialValue enumerated_value
Comment A comment as per IEC 61131-3 without (* and *) delimiters EnumeratedValue See IEC 61131-3, Table 14, #2
Name enumerated_value
Comment A comment as per IEC 61131-3 without (* and *) delimiters SubrangeType -- See IEC 61131-3, Tables 12 and 14, #3
BaseType integer_type_name
InitialValue signed_integer
Comment A comment as per IEC 61131-3 without (* and *) delimiters SIST EN 61499-2:2006
61499-2 IEC:2005(E) – 13 –
Table A.3 – Dat
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.