SEMI International Standards
Standards New Activity Report Form (SNARF)
Revised (if Applicable):
Revision to SEMI E125-0414, Specification for Equipment Self Description (EqSD)
Originating Global Technical Committee:
Information & Control
Originating TC Chapter:
Task Force (TF) in which work is to be carried out:
Diagnostic Data Acquisition Task Force NA
Note: If a new task force is needed, also submit a task force organization form (TFOF)
a. Describe the need or problem addressed by this activity.
(Indicate the customer, what benefits they will receive, and if possible, quantify the impact on the return on investment [ROI] if the Document is implemented.)
SimpleEvent and Parameters are directly defined in Node Description, in spite of being referenced in StateMachine, SEMI Object and Exception.
In this proposal, Simple Event and Parameter define a separate web service as like StateMachine, SEMIObject and Exception.
As part of supporting HTTP/2 in the EDA Standards with gRPC and Protocol Buffers, some changes may be required to accommodate new better ways of organizing information.
The first part of the SNARF has been previously approved as part of Document # 6452 - Revision to SEMI E125-0414, Specification for Equipment Self Description (EqSD). It is included as part of this SNARF because the scope of the activity has changed (with the addition of changes to support HTTP/2 integration), and SNARF #6452 will be abolished.
b. Estimate effect on industry.
2: Major effect on an industry sector - identify the relevant sector
Sector or Company Information:
Anyone implementing EDA that upgrades to the next version
c. Estimate technical difficulty of the activity.
II: Some Difficulty - Disagreements on known requirements exist but developing consensus is possible
Describe the technical areas to be covered or addressed by this Document development activity. For Subordinate Standards, list common concepts or criteria that the Subordinate Standard inherits from the Primary Standard, as well as differences from the Primary Standard:
Major and technical changes will be made to E125. The Changes to recognize Complementary Files and Materials will be made. Due to changes in E125, E164 should be changed after completion of this proposal. E164 is out of scope in this proposal.
Revise Node Description, StateMachine, SEMIObj and Exception classes, including:
1. Add operations and Arguments definitions of GetParameters, GetSimpleEvents to E125 specification and WSDL. (Change WSDL File)
2. Change Association Definitions of EquipmentNodeDescription, StateMachine, SEMIObj and Exception’s to E125 specification.
3. Refine Parameter Attribute and Association Definition.
4. Refine SimpleEvent Attribute and Association Definition.
5. Change Attributes for Node Description, StateMachine, SEMIObj, Exception to refer Parameter Classes. (Change XML Schema)
6. Change Attributes for Node Description, SEMIObj to refer SimpleEvent Classes. (Change XML Schema)
7. Add new parameter attributes to support “cached data sample” properties.
In addition, allow changes to support and best leverage HTTP/2 integration with gRPC and Protocol Buffers, and general interface improvement. For example,
a. Introduce unsigned integers
b. Possible removal of parameter types that are not generic
b: Expected result of activity
Major revision to an existing Standard or Safety Guideline
For a new Subordinate Standard, identify the Primary Standard here:
Modification of an existing part of Standard(s) or Safety Guideline(s) including Appendices, Complementary Files, and Supplementary Materials
For Standards, identify the Standard Subtype below:
3. Projected Timetable for Completion:
a: General Milestones
a. Activity Start:
b. 1st Draft by:
c. (Optional) Informational Ballot by:
d. Letter Ballot by:
e. TC Chapter Approval By:
4. Liaisons with other Global Technical Committees/TC Chapters/Subcommittees/TFs:
List SEMI global technical committees, TC Chapters, subcommittees, or task forces in your or other Regions/Locales that should be kept informed regarding the progress of this activity. (Refer to SEMI Standards organization charts and global technical committee charters and scopes as needed.)
List any planned Type I Liaisons with external nonprofit organizations (e.g., SDO) that should receive Draft Documents from Standards staff for feedback during this activity and be notified when the Letter Ballot is issued (refer to Procedure Manual § 7):
will not be issued
Identify the recipient global technical committee(s):
5. Safety Considerations:
The resulting document is expected:
NOT to be a Safety Guideline
to be a Safety Guideline
": When all safety-related information is removed from the Document, the Document is NOT technically sound and complete - Refer to Section 15.1 of the
for special procedures to be followed.
NOT to be a Safety Guideline
": When all safety-related information is removed from the Document, the Document is still technically sound and complete.
6. Intellectual Property Considerations:
For a new Standard or Safety Guideline and for any part to be modified or added in a Revision of published Standards and Safety Guidelines
If "patented technology is intended to be included in the proposed Standard(s) or Safety Guideline(s) " is selected above, then also check one:
For Revision, Reapproval, Reinstatement, or Withdrawal of existing Standard(s) and Safety Guideline(s):
there is previously known material patented technology necessary to use or implement the Standard(s) and Safety Guideline(s)
The body of the Document and any Appendices, Complementary Files, Related Information sections, or Various Materials that may or may not be a part of the Document by reference:
the incorporation of Copyrighted Item will NOT be required
the use of patented technology or the incorporation of Copyrighted Item(s) is NOT required’
: If in the course of developing the Document, it is determined that the use of patented technology or Copyrighted Item(s) is necessary for the Document, the provisions of
§ 16 must be followed.
will incorporate Copyrighted Item’
: A copyright release letter must be obtained from the copyright owner prior to publication.
7. Comments, Special Circumstances:
TC Member Review:
took place between (put dates below) before approval by the GCS, or
Member Review Start Date;
Member Review End Date:
‘TC Member Review’ is required by the
for a period of at least two weeks
before approval of a new, or a major revision of an existing, Standard or Safety Guideline. (Refer to
9. SNARF Approval Dates:
TC Chapter or GCS
Recorded in TC Minutes
10. SNARF Extension Dates:
TC Chapter Extension Granted on
Extension Expires on
Attach Pictures and Files here: