1.3 References 1.4 Definitions of Terms and Acronyms Include only terms which are specific to the instrument class. Terms of more general interest are defined in When an instrument class specification working group discovers a term of general interest, IVI-5: Glossary. it should submit the term to the glossary working group. Capabilities Groups Layout Each Capability Group section shall contain the subsections: 2.1 Introduction 2.2 <ClassName> Group Names 2.3 Repeated Capability Names If the instrument class does not define any repeated capabilities, section 2.3 shall contain the text “The <ClassName> Class Specification does not define any repeated capabilities.” If it does define one or more repeated capabilities, they shall be listed in section 2.3 and section 2.3 shall contain a sub-section for each different repeated capability describing how the name appears in the Configuration Store. 2.4 Boolean Attribute and Parameter Values 2.5 .NET Namespace General Requirements Layout Each General Requirements section shall contain the subsections: 3.1 Minimum Class Compliance 3.1.1 Disable Function 3.2 Capability Group Compliance Section 3.1 shall include a statement that an IVI specific driver shall comply with the instrument class specification, IVI-3.1, and IVI-3.2. If an instrument class needs to describe additional compliance rules for inherent capabilities beyond the requirements in they shall appear in Sections 3.1.x. A section IVI-3.2: Inherent Capabilities Specification, is added for each inherent capability with additional requirements. Capability Section Layout Each capability group, base and extensions, section shall contain thesubsections contained herein. Overview: An overview of the capability group that describes its purpose and general use. Attributes: (Optional) Defines the attributes that are a part of the capability For each attribute the capability group defines the name of the attribute, the data type, the access (read and write - R/W, or read only - RO), a description,
1.3 References 1.4 Definitions of Terms and Acronyms Include only terms which are specific to the instrument class. Terms of more general interest are defined in IVI-5: Glossary. When an instrument class specification working group discovers a term of general interest, it should submit the term to the glossary working group. Capabilities Groups Layout Each Capability Group section shall contain the subsections: 2.1 Introduction 2.2 <ClassName> Group Names 2.3 Repeated Capability Names If the instrument class does not define any repeated capabilities, section 2.3 shall contain the text “The <ClassName> Class Specification does not define any repeated capabilities.” If it does define one or more repeated capabilities, they shall be listed in section 2.3 and section 2.3 shall contain a sub-section for each different repeated capability describing how the name appears in the Configuration Store. 2.4 Boolean Attribute and Parameter Values 2.5 .NET Namespace General Requirements Layout Each General Requirements section shall contain the subsections: 3.1 Minimum Class Compliance 3.1.1 Disable Function 3.2 Capability Group Compliance Section 3.1 shall include a statement that an IVI specific driver shall comply with the instrument class specification, IVI-3.1, and IVI-3.2. If an instrument class needs to describe additional compliance rules for inherent capabilities beyond the requirements in IVI-3.2: Inherent Capabilities Specification, they shall appear in Sections 3.1.x. A section is added for each inherent capability with additional requirements. Capability Section Layout Each capability group, base and extensions, section shall contain thesubsections contained herein. Overview: An overview of the capability group that describes its purpose and general use. Attributes: (Optional) Defines the attributes that are a part of the capability For each attribute the capability group defines the name of the attribute, the data type, the access (read and write - R/W, or read only - RO), a description,