GET https://dev.normadoc.fr/products/ieee-1647-2016-ieee00005607-242777

Response
200 OK
IP
216.73.216.149
Profiled on
Token
f3cee7

Components

4 Twig Components
18 Render Count
16 ms Render Time
208.0 MiB Memory Usage

Components

Name Metadata Render Count Render Time
ProductState 
"App\Twig\Components\ProductState"
components/ProductState.html.twig 		8 1.70ms
ProductMostRecent 
"App\Twig\Components\ProductMostRecent"
components/ProductMostRecent.html.twig 		8 5.71ms
ProductType 
"App\Twig\Components\ProductType"
components/ProductType.html.twig 		1 0.22ms
ProductCard 
"App\Twig\Components\ProductCard"
components/ProductCard.html.twig 		1 9.35ms

Render calls

ProductState App\Twig\Components\ProductState 206.0 MiB 0.31 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#93054
  +product: App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductType App\Twig\Components\ProductType 206.0 MiB 0.22 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductType {#93234
  +product: App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.64 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#93309
  +product: App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.21 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#106804
  +product: App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.80 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#106871
  +product: App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.20 ms
Input props 
[
  "product" => App\Entity\Product\Product {#93750
    #id: 12167
    #code: "IEEE00007193"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040245 {#93758
      date: 2025-06-27 18:04:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93737
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43677
        #name: "IEEE 1647:2019"
        #slug: "ieee-1647-2019-ieee00007193-243820"
        #description: """
          Revision Standard - Active.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs (b) the e language interaction with standard simulation languages (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93721
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1600725600 {#93757
      date: 2020-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1565301600 {#93756
      date: 2019-08-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 622
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113557
  +product: App\Entity\Product\Product {#93750
    #id: 12167
    #code: "IEEE00007193"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040245 {#93758
      date: 2025-06-27 18:04:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93737
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43677
        #name: "IEEE 1647:2019"
        #slug: "ieee-1647-2019-ieee00007193-243820"
        #description: """
          Revision Standard - Active.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs (b) the e language interaction with standard simulation languages (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93721
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1600725600 {#93757
      date: 2020-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1565301600 {#93756
      date: 2019-08-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 622
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.75 ms
Input props 
[
  "product" => App\Entity\Product\Product {#93750
    #id: 12167
    #code: "IEEE00007193"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040245 {#93758
      date: 2025-06-27 18:04:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93737
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43677
        #name: "IEEE 1647:2019"
        #slug: "ieee-1647-2019-ieee00007193-243820"
        #description: """
          Revision Standard - Active.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs (b) the e language interaction with standard simulation languages (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93721
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1600725600 {#93757
      date: 2020-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1565301600 {#93756
      date: 2019-08-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 622
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113624
  +product: App\Entity\Product\Product {#93750
    #id: 12167
    #code: "IEEE00007193"
    #attributes: Doctrine\ORM\PersistentCollection {#93732 …}
    #variants: Doctrine\ORM\PersistentCollection {#93729 …}
    #options: Doctrine\ORM\PersistentCollection {#93725 …}
    #associations: Doctrine\ORM\PersistentCollection {#93727 …}
    #createdAt: DateTime @1751040245 {#93758
      date: 2025-06-27 18:04:05.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#93737
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93743 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93750}
        #id: 43677
        #name: "IEEE 1647:2019"
        #slug: "ieee-1647-2019-ieee00007193-243820"
        #description: """
          Revision Standard - Active.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs (b) the e language interaction with standard simulation languages (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93741 …}
    #channels: Doctrine\ORM\PersistentCollection {#93734 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93739 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93736 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93751 …}
    -apiLastModifiedAt: DateTime @1754517600 {#93721
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1600725600 {#93757
      date: 2020-09-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1565301600 {#93756
      date: 2019-08-09 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 622
    -documents: Doctrine\ORM\PersistentCollection {#93747 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93745 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113689
  +product: App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.62 ms
Input props 
[
  "product" => App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113716
  +product: App\Entity\Product\Product {#7310
    #id: 11125
    #code: "IEEE00005607"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039494 {#7274
      date: 2025-06-27 17:51:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#7322
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39509
        #name: "IEEE 1647:2016"
        #slug: "ieee-1647-2016-ieee00005607-242777"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation-independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1630447200 {#7292
      date: 2021-09-01 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1483657200 {#7318
      date: 2017-01-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 558
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.17 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113780
  +product: App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.65 ms
Input props 
[
  "product" => App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113807
  +product: App\Entity\Product\Product {#106752
    #id: 10507
    #code: "IEEE00004509"
    #attributes: Doctrine\ORM\PersistentCollection {#106735 …}
    #variants: Doctrine\ORM\PersistentCollection {#106732 …}
    #options: Doctrine\ORM\PersistentCollection {#106728 …}
    #associations: Doctrine\ORM\PersistentCollection {#106730 …}
    #createdAt: DateTime @1751039104 {#106760
      date: 2025-06-27 17:45:04.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969918 {#106733
      date: 2025-07-31 15:51:58.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106746 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106778
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106752}
        #id: 37037
        #name: "IEEE 1647:2011"
        #slug: "ieee-1647-2011-ieee00004509-242159"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          This standard defines the e functional verification language. This standard aims to serve as an authoritative source for the definition of (a) syntax and semantics of e language constructs, (b) the e language interaction with standard simulation languages, and (c) e language libraries.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106743 …}
    #channels: Doctrine\ORM\PersistentCollection {#106737 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106741 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106739 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106753 …}
    -apiLastModifiedAt: DateTime @1743289200 {#106720
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1600984800 {#106759
      date: 2020-09-25 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1314309600 {#106758
      date: 2011-08-26 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 495
    -documents: Doctrine\ORM\PersistentCollection {#106750 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106748 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113455
    #id: 10249
    #code: "IEEE00003990"
    #attributes: Doctrine\ORM\PersistentCollection {#113471 …}
    #variants: Doctrine\ORM\PersistentCollection {#113473 …}
    #options: Doctrine\ORM\PersistentCollection {#113477 …}
    #associations: Doctrine\ORM\PersistentCollection {#113475 …}
    #createdAt: DateTime @1751038926 {#113446
      date: 2025-06-27 17:42:06.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113444
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113461 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113877
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113455}
        #id: 36005
        #name: "IEEE 1647:2008"
        #slug: "ieee-1647-2008-ieee00003990-241901"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. This standard aims to serve as an authoritative source for the definition of:<br />\n
          a) syntax and semantics of e language constructs<br />\n
          b) the e language interaction with standard simulation languages<br />\n
          c) e language libraries<br />\n
          This revision extends the standard to cover novel verification-related features.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools. The revision project extends the standard to include novel verification related features. The revision project extends the standard to include novel verification related features.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113463 …}
    #channels: Doctrine\ORM\PersistentCollection {#113469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113465 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113467 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113454 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113447
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113440
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1217714400 {#113437
      date: 2008-08-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 470
    -documents: Doctrine\ORM\PersistentCollection {#113457 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113459 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#113892
  +product: App\Entity\Product\Product {#113455
    #id: 10249
    #code: "IEEE00003990"
    #attributes: Doctrine\ORM\PersistentCollection {#113471 …}
    #variants: Doctrine\ORM\PersistentCollection {#113473 …}
    #options: Doctrine\ORM\PersistentCollection {#113477 …}
    #associations: Doctrine\ORM\PersistentCollection {#113475 …}
    #createdAt: DateTime @1751038926 {#113446
      date: 2025-06-27 17:42:06.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113444
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113461 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113877
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113455}
        #id: 36005
        #name: "IEEE 1647:2008"
        #slug: "ieee-1647-2008-ieee00003990-241901"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. This standard aims to serve as an authoritative source for the definition of:<br />\n
          a) syntax and semantics of e language constructs<br />\n
          b) the e language interaction with standard simulation languages<br />\n
          c) e language libraries<br />\n
          This revision extends the standard to cover novel verification-related features.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools. The revision project extends the standard to include novel verification related features. The revision project extends the standard to include novel verification related features.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113463 …}
    #channels: Doctrine\ORM\PersistentCollection {#113469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113465 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113467 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113454 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113447
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113440
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1217714400 {#113437
      date: 2008-08-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 470
    -documents: Doctrine\ORM\PersistentCollection {#113457 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113459 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.63 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113455
    #id: 10249
    #code: "IEEE00003990"
    #attributes: Doctrine\ORM\PersistentCollection {#113471 …}
    #variants: Doctrine\ORM\PersistentCollection {#113473 …}
    #options: Doctrine\ORM\PersistentCollection {#113477 …}
    #associations: Doctrine\ORM\PersistentCollection {#113475 …}
    #createdAt: DateTime @1751038926 {#113446
      date: 2025-06-27 17:42:06.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113444
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113461 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113877
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113455}
        #id: 36005
        #name: "IEEE 1647:2008"
        #slug: "ieee-1647-2008-ieee00003990-241901"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. This standard aims to serve as an authoritative source for the definition of:<br />\n
          a) syntax and semantics of e language constructs<br />\n
          b) the e language interaction with standard simulation languages<br />\n
          c) e language libraries<br />\n
          This revision extends the standard to cover novel verification-related features.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools. The revision project extends the standard to include novel verification related features. The revision project extends the standard to include novel verification related features.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113463 …}
    #channels: Doctrine\ORM\PersistentCollection {#113469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113465 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113467 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113454 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113447
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113440
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1217714400 {#113437
      date: 2008-08-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 470
    -documents: Doctrine\ORM\PersistentCollection {#113457 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113459 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#113944
  +product: App\Entity\Product\Product {#113455
    #id: 10249
    #code: "IEEE00003990"
    #attributes: Doctrine\ORM\PersistentCollection {#113471 …}
    #variants: Doctrine\ORM\PersistentCollection {#113473 …}
    #options: Doctrine\ORM\PersistentCollection {#113477 …}
    #associations: Doctrine\ORM\PersistentCollection {#113475 …}
    #createdAt: DateTime @1751038926 {#113446
      date: 2025-06-27 17:42:06.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#113444
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113461 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113877
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113455}
        #id: 36005
        #name: "IEEE 1647:2008"
        #slug: "ieee-1647-2008-ieee00003990-241901"
        #description: """
          Revision Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying a hardware or software design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. A definition of the e language syntax and semantics and how tool developers and verification engineers should use them are contained in this standard.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. This standard aims to serve as an authoritative source for the definition of:<br />\n
          a) syntax and semantics of e language constructs<br />\n
          b) the e language interaction with standard simulation languages<br />\n
          c) e language libraries<br />\n
          This revision extends the standard to cover novel verification-related features.<br />\n
          This standard serves the community involved with functional verification of electronic designs using the e language. It provides an implementation independent definition of the e language and facilitates the development of e language based design automation tools. The revision project extends the standard to include novel verification related features. The revision project extends the standard to include novel verification related features.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language e"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113463 …}
    #channels: Doctrine\ORM\PersistentCollection {#113469 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113465 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113467 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113454 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113447
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113440
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1217714400 {#113437
      date: 2008-08-03 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 470
    -documents: Doctrine\ORM\PersistentCollection {#113457 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113459 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductState App\Twig\Components\ProductState 206.0 MiB 0.18 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113484
    #id: 10027
    #code: "IEEE00003473"
    #attributes: Doctrine\ORM\PersistentCollection {#113501 …}
    #variants: Doctrine\ORM\PersistentCollection {#113503 …}
    #options: Doctrine\ORM\PersistentCollection {#113507 …}
    #associations: Doctrine\ORM\PersistentCollection {#113505 …}
    #createdAt: DateTime @1751038757 {#113479
      date: 2025-06-27 17:39:17.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#113480
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113491 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#114010
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113484}
        #id: 35117
        #name: "IEEE 1647:2006"
        #slug: "ieee-1647-2006-ieee00003473-241679"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying an electronic design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. This standard contains a definition of the e language syntax and semantics, and how tool developers and verification engineers should use them.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. The e functional verification language is an application-specific programming language, aimed at automating the task of verifying electronic designs with respect to their specifications. This standard aims to serve as an authoritative source for the definition of the following: a) syntax and semantics of e language constructs b) the e language interaction with standard simulation languages c) e language libraries<br />\n
          Electronic systems are integrated circuits (ICs), boards, or modules combining multiple ICs together, along with optional embedded processors and software components. Electronic systems are built to specifications that anticipate the environment in which such systems are expected to function and define the expected system functionality. Functional verification measures how well a system meets its specification. Even with moderately complex systems this question cannot be answered by inspection. For all modern electronic systems, a sophisticated verification process needs to accompany the design process to ensure compliance with the specification. Many electronic design automation (EDA) tools are used to carry out the functional verification process. The most prominent functional verification method, used to verify virtually all system designs, is called dynamic verification or simulation-based verification . Simulation-based verification makes use of a functional model of the system being designed. The functional model is simulated in the context of a mockup of the anticipated system environment. This mock-up is called the verification environment.<br />\n
          There are many requirements a verification environment needs to fulfill.<br />\n
          — It needs to create input stimulus and feed it into the system being verified.<br />\n
          — It needs to collect the output from the system being verified, as well as the state of selected internal nodes.<br />\n
          — It needs to check the output matches the expectations, based on the functional requirements, the state of the system being verified, and the inputs provided.<br />\n
          — It needs to measure functional coverage : the extent to which functions of the system being verified have been exercised by the verification environment.<br />\n
          — It needs to facilitate error identification, isolation, and debug. For that purpose, test environments contain combinational and temporal assertions, as well as various messaging and logging<br />\n
          capabilities.<br />\n
          — The verification environment needs to be able to mimic all possible variations and configurations the system being verified might face in practice.<br />\n
          — The verification environment needs to be able to throw a wide variety of error conditions at the<br />\n
          system being verified, in order to test error handling and error recovery.<br />\n
          — The verification environment should be easily controllable, to allow steering by the verification<br />\n
          engineers.<br />\n
          The verification environment is a primary component in a simulation-based verification process. The<br />\n
          environment needs to drive the system being verified through enough diverse scenarios to cover a<br />\n
          statistically meaningful portion of the systems state space. Coverage data collected throughout the process should provide the foundation to an informed decision about the production readiness of the system being designed. Sophisticated verification environments are complex software systems, representing a significant investment. Reuse of verification components is a primary way of minimizing this investment. Reusability is typically an artifact of a well thought-out software architecture, but in the case of e , the language itself facilitates reuse through aspect-oriented programming (AOP) constructs and the semantics of generation.<br />\n
          The purpose of the e functional verification language is to facilitate the creation of sophisticated verification environments.<br />\n
          e features many constructs that automate and support common verification environment<br />\n
          tasks. A standard definition of the e language should serve both practicing verification engineers and EDA tool developers. Engineers using e to build verification environments and reusable verification components need to ensure the valuable intellectual property (IP) they create can be interpreted by others. Tool developers need to agree on consistent syntax and semantics to ensure interoperability between tools. These goals are best facilitated by means of an open standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language 'e'"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113493 …}
    #channels: Doctrine\ORM\PersistentCollection {#113499 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113495 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113497 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113485 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113481
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1693346400 {#113482
      date: 2023-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1159480800 {#113483
      date: 2006-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 390
    -documents: Doctrine\ORM\PersistentCollection {#113487 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113489 …}
  }
  "showFullLabel" => "true"
]
Attributes 
[
  "showFullLabel" => "true"
]
Component 
App\Twig\Components\ProductState {#114025
  +product: App\Entity\Product\Product {#113484
    #id: 10027
    #code: "IEEE00003473"
    #attributes: Doctrine\ORM\PersistentCollection {#113501 …}
    #variants: Doctrine\ORM\PersistentCollection {#113503 …}
    #options: Doctrine\ORM\PersistentCollection {#113507 …}
    #associations: Doctrine\ORM\PersistentCollection {#113505 …}
    #createdAt: DateTime @1751038757 {#113479
      date: 2025-06-27 17:39:17.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#113480
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113491 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#114010
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113484}
        #id: 35117
        #name: "IEEE 1647:2006"
        #slug: "ieee-1647-2006-ieee00003473-241679"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying an electronic design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. This standard contains a definition of the e language syntax and semantics, and how tool developers and verification engineers should use them.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. The e functional verification language is an application-specific programming language, aimed at automating the task of verifying electronic designs with respect to their specifications. This standard aims to serve as an authoritative source for the definition of the following: a) syntax and semantics of e language constructs b) the e language interaction with standard simulation languages c) e language libraries<br />\n
          Electronic systems are integrated circuits (ICs), boards, or modules combining multiple ICs together, along with optional embedded processors and software components. Electronic systems are built to specifications that anticipate the environment in which such systems are expected to function and define the expected system functionality. Functional verification measures how well a system meets its specification. Even with moderately complex systems this question cannot be answered by inspection. For all modern electronic systems, a sophisticated verification process needs to accompany the design process to ensure compliance with the specification. Many electronic design automation (EDA) tools are used to carry out the functional verification process. The most prominent functional verification method, used to verify virtually all system designs, is called dynamic verification or simulation-based verification . Simulation-based verification makes use of a functional model of the system being designed. The functional model is simulated in the context of a mockup of the anticipated system environment. This mock-up is called the verification environment.<br />\n
          There are many requirements a verification environment needs to fulfill.<br />\n
          — It needs to create input stimulus and feed it into the system being verified.<br />\n
          — It needs to collect the output from the system being verified, as well as the state of selected internal nodes.<br />\n
          — It needs to check the output matches the expectations, based on the functional requirements, the state of the system being verified, and the inputs provided.<br />\n
          — It needs to measure functional coverage : the extent to which functions of the system being verified have been exercised by the verification environment.<br />\n
          — It needs to facilitate error identification, isolation, and debug. For that purpose, test environments contain combinational and temporal assertions, as well as various messaging and logging<br />\n
          capabilities.<br />\n
          — The verification environment needs to be able to mimic all possible variations and configurations the system being verified might face in practice.<br />\n
          — The verification environment needs to be able to throw a wide variety of error conditions at the<br />\n
          system being verified, in order to test error handling and error recovery.<br />\n
          — The verification environment should be easily controllable, to allow steering by the verification<br />\n
          engineers.<br />\n
          The verification environment is a primary component in a simulation-based verification process. The<br />\n
          environment needs to drive the system being verified through enough diverse scenarios to cover a<br />\n
          statistically meaningful portion of the systems state space. Coverage data collected throughout the process should provide the foundation to an informed decision about the production readiness of the system being designed. Sophisticated verification environments are complex software systems, representing a significant investment. Reuse of verification components is a primary way of minimizing this investment. Reusability is typically an artifact of a well thought-out software architecture, but in the case of e , the language itself facilitates reuse through aspect-oriented programming (AOP) constructs and the semantics of generation.<br />\n
          The purpose of the e functional verification language is to facilitate the creation of sophisticated verification environments.<br />\n
          e features many constructs that automate and support common verification environment<br />\n
          tasks. A standard definition of the e language should serve both practicing verification engineers and EDA tool developers. Engineers using e to build verification environments and reusable verification components need to ensure the valuable intellectual property (IP) they create can be interpreted by others. Tool developers need to agree on consistent syntax and semantics to ensure interoperability between tools. These goals are best facilitated by means of an open standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language 'e'"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113493 …}
    #channels: Doctrine\ORM\PersistentCollection {#113499 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113495 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113497 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113485 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113481
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1693346400 {#113482
      date: 2023-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1159480800 {#113483
      date: 2006-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 390
    -documents: Doctrine\ORM\PersistentCollection {#113487 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113489 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 206.0 MiB 0.61 ms
Input props 
[
  "product" => App\Entity\Product\Product {#113484
    #id: 10027
    #code: "IEEE00003473"
    #attributes: Doctrine\ORM\PersistentCollection {#113501 …}
    #variants: Doctrine\ORM\PersistentCollection {#113503 …}
    #options: Doctrine\ORM\PersistentCollection {#113507 …}
    #associations: Doctrine\ORM\PersistentCollection {#113505 …}
    #createdAt: DateTime @1751038757 {#113479
      date: 2025-06-27 17:39:17.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#113480
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113491 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#114010
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113484}
        #id: 35117
        #name: "IEEE 1647:2006"
        #slug: "ieee-1647-2006-ieee00003473-241679"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying an electronic design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. This standard contains a definition of the e language syntax and semantics, and how tool developers and verification engineers should use them.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. The e functional verification language is an application-specific programming language, aimed at automating the task of verifying electronic designs with respect to their specifications. This standard aims to serve as an authoritative source for the definition of the following: a) syntax and semantics of e language constructs b) the e language interaction with standard simulation languages c) e language libraries<br />\n
          Electronic systems are integrated circuits (ICs), boards, or modules combining multiple ICs together, along with optional embedded processors and software components. Electronic systems are built to specifications that anticipate the environment in which such systems are expected to function and define the expected system functionality. Functional verification measures how well a system meets its specification. Even with moderately complex systems this question cannot be answered by inspection. For all modern electronic systems, a sophisticated verification process needs to accompany the design process to ensure compliance with the specification. Many electronic design automation (EDA) tools are used to carry out the functional verification process. The most prominent functional verification method, used to verify virtually all system designs, is called dynamic verification or simulation-based verification . Simulation-based verification makes use of a functional model of the system being designed. The functional model is simulated in the context of a mockup of the anticipated system environment. This mock-up is called the verification environment.<br />\n
          There are many requirements a verification environment needs to fulfill.<br />\n
          — It needs to create input stimulus and feed it into the system being verified.<br />\n
          — It needs to collect the output from the system being verified, as well as the state of selected internal nodes.<br />\n
          — It needs to check the output matches the expectations, based on the functional requirements, the state of the system being verified, and the inputs provided.<br />\n
          — It needs to measure functional coverage : the extent to which functions of the system being verified have been exercised by the verification environment.<br />\n
          — It needs to facilitate error identification, isolation, and debug. For that purpose, test environments contain combinational and temporal assertions, as well as various messaging and logging<br />\n
          capabilities.<br />\n
          — The verification environment needs to be able to mimic all possible variations and configurations the system being verified might face in practice.<br />\n
          — The verification environment needs to be able to throw a wide variety of error conditions at the<br />\n
          system being verified, in order to test error handling and error recovery.<br />\n
          — The verification environment should be easily controllable, to allow steering by the verification<br />\n
          engineers.<br />\n
          The verification environment is a primary component in a simulation-based verification process. The<br />\n
          environment needs to drive the system being verified through enough diverse scenarios to cover a<br />\n
          statistically meaningful portion of the systems state space. Coverage data collected throughout the process should provide the foundation to an informed decision about the production readiness of the system being designed. Sophisticated verification environments are complex software systems, representing a significant investment. Reuse of verification components is a primary way of minimizing this investment. Reusability is typically an artifact of a well thought-out software architecture, but in the case of e , the language itself facilitates reuse through aspect-oriented programming (AOP) constructs and the semantics of generation.<br />\n
          The purpose of the e functional verification language is to facilitate the creation of sophisticated verification environments.<br />\n
          e features many constructs that automate and support common verification environment<br />\n
          tasks. A standard definition of the e language should serve both practicing verification engineers and EDA tool developers. Engineers using e to build verification environments and reusable verification components need to ensure the valuable intellectual property (IP) they create can be interpreted by others. Tool developers need to agree on consistent syntax and semantics to ensure interoperability between tools. These goals are best facilitated by means of an open standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language 'e'"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113493 …}
    #channels: Doctrine\ORM\PersistentCollection {#113499 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113495 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113497 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113485 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113481
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1693346400 {#113482
      date: 2023-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1159480800 {#113483
      date: 2006-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 390
    -documents: Doctrine\ORM\PersistentCollection {#113487 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113489 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#114077
  +product: App\Entity\Product\Product {#113484
    #id: 10027
    #code: "IEEE00003473"
    #attributes: Doctrine\ORM\PersistentCollection {#113501 …}
    #variants: Doctrine\ORM\PersistentCollection {#113503 …}
    #options: Doctrine\ORM\PersistentCollection {#113507 …}
    #associations: Doctrine\ORM\PersistentCollection {#113505 …}
    #createdAt: DateTime @1751038757 {#113479
      date: 2025-06-27 17:39:17.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#113480
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113491 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#114010
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113484}
        #id: 35117
        #name: "IEEE 1647:2006"
        #slug: "ieee-1647-2006-ieee00003473-241679"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          The e functional verification language is an application-specific programming language, aimed at automating the task of verifying an electronic design with respect to its specification. Verification environments written in e provide a model of the environment in which the design is expected to function, including the kinds of erroneous conditions the design needs to withstand. A typical verification environment is capable of generating user-controlled test inputs with statistically interesting characteristics. Such an environment can check the validity of the design responses. Functional coverage metrics are used to control the verification effort and gauge the quality of the design. e verification environments can be used throughout the design cycle, from a high-level architectural model to a fully realized system. This standard contains a definition of the e language syntax and semantics, and how tool developers and verification engineers should use them.<br />\n
          \t\t\t\t<br />\n
          The scope of this standard is the definition of the e functional verification language. The e functional verification language is an application-specific programming language, aimed at automating the task of verifying electronic designs with respect to their specifications. This standard aims to serve as an authoritative source for the definition of the following: a) syntax and semantics of e language constructs b) the e language interaction with standard simulation languages c) e language libraries<br />\n
          Electronic systems are integrated circuits (ICs), boards, or modules combining multiple ICs together, along with optional embedded processors and software components. Electronic systems are built to specifications that anticipate the environment in which such systems are expected to function and define the expected system functionality. Functional verification measures how well a system meets its specification. Even with moderately complex systems this question cannot be answered by inspection. For all modern electronic systems, a sophisticated verification process needs to accompany the design process to ensure compliance with the specification. Many electronic design automation (EDA) tools are used to carry out the functional verification process. The most prominent functional verification method, used to verify virtually all system designs, is called dynamic verification or simulation-based verification . Simulation-based verification makes use of a functional model of the system being designed. The functional model is simulated in the context of a mockup of the anticipated system environment. This mock-up is called the verification environment.<br />\n
          There are many requirements a verification environment needs to fulfill.<br />\n
          — It needs to create input stimulus and feed it into the system being verified.<br />\n
          — It needs to collect the output from the system being verified, as well as the state of selected internal nodes.<br />\n
          — It needs to check the output matches the expectations, based on the functional requirements, the state of the system being verified, and the inputs provided.<br />\n
          — It needs to measure functional coverage : the extent to which functions of the system being verified have been exercised by the verification environment.<br />\n
          — It needs to facilitate error identification, isolation, and debug. For that purpose, test environments contain combinational and temporal assertions, as well as various messaging and logging<br />\n
          capabilities.<br />\n
          — The verification environment needs to be able to mimic all possible variations and configurations the system being verified might face in practice.<br />\n
          — The verification environment needs to be able to throw a wide variety of error conditions at the<br />\n
          system being verified, in order to test error handling and error recovery.<br />\n
          — The verification environment should be easily controllable, to allow steering by the verification<br />\n
          engineers.<br />\n
          The verification environment is a primary component in a simulation-based verification process. The<br />\n
          environment needs to drive the system being verified through enough diverse scenarios to cover a<br />\n
          statistically meaningful portion of the systems state space. Coverage data collected throughout the process should provide the foundation to an informed decision about the production readiness of the system being designed. Sophisticated verification environments are complex software systems, representing a significant investment. Reuse of verification components is a primary way of minimizing this investment. Reusability is typically an artifact of a well thought-out software architecture, but in the case of e , the language itself facilitates reuse through aspect-oriented programming (AOP) constructs and the semantics of generation.<br />\n
          The purpose of the e functional verification language is to facilitate the creation of sophisticated verification environments.<br />\n
          e features many constructs that automate and support common verification environment<br />\n
          tasks. A standard definition of the e language should serve both practicing verification engineers and EDA tool developers. Engineers using e to build verification environments and reusable verification components need to ensure the valuable intellectual property (IP) they create can be interpreted by others. Tool developers need to agree on consistent syntax and semantics to ensure interoperability between tools. These goals are best facilitated by means of an open standard.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for the Functional Verification Language 'e'"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113493 …}
    #channels: Doctrine\ORM\PersistentCollection {#113499 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113495 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113497 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113485 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113481
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1693346400 {#113482
      date: 2023-08-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1159480800 {#113483
      date: 2006-09-29 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "1647"
    -bookCollection: ""
    -pageCount: 390
    -documents: Doctrine\ORM\PersistentCollection {#113487 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113489 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductCard App\Twig\Components\ProductCard 208.0 MiB 9.35 ms
Input props 
[
  "product" => App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]
Attributes 
[]
Component 
App\Twig\Components\ProductCard {#135693
  +product: App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}
ProductState App\Twig\Components\ProductState 208.0 MiB 0.27 ms
Input props 
[
  "product" => App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
]
Attributes 
[
  "showFullLabel" => false
]
Component 
App\Twig\Components\ProductState {#135729
  +product: App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}
ProductMostRecent App\Twig\Components\ProductMostRecent 208.0 MiB 1.00 ms
Input props 
[
  "product" => App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
]
Attributes 
[]
Component 
App\Twig\Components\ProductMostRecent {#135807
  +product: App\Entity\Product\Product {#135601
    #id: 10912
    #code: "IEEE00005274"
    #attributes: Doctrine\ORM\PersistentCollection {#135625 …}
    #variants: Doctrine\ORM\PersistentCollection {#135623 …}
    #options: Doctrine\ORM\PersistentCollection {#135618 …}
    #associations: Doctrine\ORM\PersistentCollection {#135621 …}
    #createdAt: DateTime @1751039361 {#135614
      date: 2025-06-27 17:49:21.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608190 {#135607
      date: 2025-08-08 01:09:50.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#135636 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#135725
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#135601}
        #id: 38657
        #name: "IEEE/IEC 61691-1-1:2011"
        #slug: "ieee-iec-61691-1-1-2011-ieee00005274-242564"
        #description: """
          Revision Standard - Superseded.<br />\n
          Adoption of IEEE Std 1076-2008. VHSIC Hardware Description Language (VHDL) is defined. VHDL is a formal notation intended for use in all phases of the creation of electronic systems. Because it is both machine readable and human readable, it supports the development, verification, synthesis, and testing of hardware designs; the communication of hardware design data; and the maintenance, modification, and procurement of hardware. Its primary audiences are the implementors of tools supporting the language and the advanced users of the language. (Superseded by IEEE C95.1-2019)<br />\n
          \t\t\t\t
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEC/IEEE International Standard - Behavioural languages - Part 1-1: VHDL Language Reference Manual"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#135634 …}
    #channels: Doctrine\ORM\PersistentCollection {#135627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#135631 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#135629 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#135641 …}
    -apiLastModifiedAt: DateTime @1754517600 {#135600
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#135649
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1305756000 {#135620
      date: 2011-05-19 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "61691-1-1"
    -bookCollection: ""
    -pageCount: 648
    -documents: Doctrine\ORM\PersistentCollection {#135640 …}
    -favorites: Doctrine\ORM\PersistentCollection {#135638 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}