Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93114
  +product: App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93294
  +product: App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93369
  +product: App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106854
  +product: App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
]

App\Twig\Components\ProductMostRecent {#106921
  +product: App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93800
    #id: 12463
    #code: "IEEE00007746"
    #attributes: Doctrine\ORM\PersistentCollection {#93782 …}
    #variants: Doctrine\ORM\PersistentCollection {#93779 …}
    #options: Doctrine\ORM\PersistentCollection {#93775 …}
    #associations: Doctrine\ORM\PersistentCollection {#93777 …}
    #createdAt: DateTime @1751040448 {#93808
      date: 2025-06-27 18:07:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93787
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93793 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93800}
        #id: 44861
        #name: "IEEE 2410:2021"
        #slug: "ieee-2410-2021-ieee00007746-244117"
        #description: """
          Revision Standard - Active.<br />\n
          The Standard for Biometric Privacy (SBP) provides private identity assertion. SBP supersedes the prior IEEE Std 2410(TM)-2019 by including a formal specification for privacy and biometrics such that a conforming SBP system does not incur GDPR, CCPA, BIPA or HIPAA privacy obligations. Homomorphic encryption ensures the biometric payload is always one-way encrypted with no need for key management and provides full privacy by ensuring plaintext biometrics are never received by the SBP server. The SBP implementation includes software running on a client device and on the SPB server. Pluggable components are used to replace legacy functionality to allow rapid integration into existing operating environments. The SBP implementation allows the systems to meet security needs by using the application programming interface, whether the underlying system is a relational database management system or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST ), JavaScript Object Notation (JSON), and Transport Layer Security (TLS) to provide the communication interface. This document describes<br />\n
          the essential methodology to SBP.<br />\n
          \t\t\t\t<br />\n
          The Standard for Biometric Privacy provides a biometric-agnostic security protocol for private authentication, identification, and liveness. The SBP implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS) or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. SBP additionally includes the biometric identification which the industry frequently calls the ‘one to many’ case. In the past, biometric identification was not considered because this requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic security protocol for authentication, identification, and liveness.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Privacy"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93791 …}
    #channels: Doctrine\ORM\PersistentCollection {#93784 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93789 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93786 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93801 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93771
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1624226400 {#93807
      date: 2021-06-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1621807200 {#93806
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#93797 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93795 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113576
  +product: App\Entity\Product\Product {#93800
    #id: 12463
    #code: "IEEE00007746"
    #attributes: Doctrine\ORM\PersistentCollection {#93782 …}
    #variants: Doctrine\ORM\PersistentCollection {#93779 …}
    #options: Doctrine\ORM\PersistentCollection {#93775 …}
    #associations: Doctrine\ORM\PersistentCollection {#93777 …}
    #createdAt: DateTime @1751040448 {#93808
      date: 2025-06-27 18:07:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93787
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93793 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93800}
        #id: 44861
        #name: "IEEE 2410:2021"
        #slug: "ieee-2410-2021-ieee00007746-244117"
        #description: """
          Revision Standard - Active.<br />\n
          The Standard for Biometric Privacy (SBP) provides private identity assertion. SBP supersedes the prior IEEE Std 2410(TM)-2019 by including a formal specification for privacy and biometrics such that a conforming SBP system does not incur GDPR, CCPA, BIPA or HIPAA privacy obligations. Homomorphic encryption ensures the biometric payload is always one-way encrypted with no need for key management and provides full privacy by ensuring plaintext biometrics are never received by the SBP server. The SBP implementation includes software running on a client device and on the SPB server. Pluggable components are used to replace legacy functionality to allow rapid integration into existing operating environments. The SBP implementation allows the systems to meet security needs by using the application programming interface, whether the underlying system is a relational database management system or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST ), JavaScript Object Notation (JSON), and Transport Layer Security (TLS) to provide the communication interface. This document describes<br />\n
          the essential methodology to SBP.<br />\n
          \t\t\t\t<br />\n
          The Standard for Biometric Privacy provides a biometric-agnostic security protocol for private authentication, identification, and liveness. The SBP implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS) or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. SBP additionally includes the biometric identification which the industry frequently calls the ‘one to many’ case. In the past, biometric identification was not considered because this requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic security protocol for authentication, identification, and liveness.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Privacy"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93791 …}
    #channels: Doctrine\ORM\PersistentCollection {#93784 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93789 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93786 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93801 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93771
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1624226400 {#93807
      date: 2021-06-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1621807200 {#93806
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#93797 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93795 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93800
    #id: 12463
    #code: "IEEE00007746"
    #attributes: Doctrine\ORM\PersistentCollection {#93782 …}
    #variants: Doctrine\ORM\PersistentCollection {#93779 …}
    #options: Doctrine\ORM\PersistentCollection {#93775 …}
    #associations: Doctrine\ORM\PersistentCollection {#93777 …}
    #createdAt: DateTime @1751040448 {#93808
      date: 2025-06-27 18:07:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93787
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93793 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93800}
        #id: 44861
        #name: "IEEE 2410:2021"
        #slug: "ieee-2410-2021-ieee00007746-244117"
        #description: """
          Revision Standard - Active.<br />\n
          The Standard for Biometric Privacy (SBP) provides private identity assertion. SBP supersedes the prior IEEE Std 2410(TM)-2019 by including a formal specification for privacy and biometrics such that a conforming SBP system does not incur GDPR, CCPA, BIPA or HIPAA privacy obligations. Homomorphic encryption ensures the biometric payload is always one-way encrypted with no need for key management and provides full privacy by ensuring plaintext biometrics are never received by the SBP server. The SBP implementation includes software running on a client device and on the SPB server. Pluggable components are used to replace legacy functionality to allow rapid integration into existing operating environments. The SBP implementation allows the systems to meet security needs by using the application programming interface, whether the underlying system is a relational database management system or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST ), JavaScript Object Notation (JSON), and Transport Layer Security (TLS) to provide the communication interface. This document describes<br />\n
          the essential methodology to SBP.<br />\n
          \t\t\t\t<br />\n
          The Standard for Biometric Privacy provides a biometric-agnostic security protocol for private authentication, identification, and liveness. The SBP implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS) or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. SBP additionally includes the biometric identification which the industry frequently calls the ‘one to many’ case. In the past, biometric identification was not considered because this requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic security protocol for authentication, identification, and liveness.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Privacy"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93791 …}
    #channels: Doctrine\ORM\PersistentCollection {#93784 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93789 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93786 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93801 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93771
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1624226400 {#93807
      date: 2021-06-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1621807200 {#93806
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#93797 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93795 …}
  }
]

App\Twig\Components\ProductMostRecent {#113643
  +product: App\Entity\Product\Product {#93800
    #id: 12463
    #code: "IEEE00007746"
    #attributes: Doctrine\ORM\PersistentCollection {#93782 …}
    #variants: Doctrine\ORM\PersistentCollection {#93779 …}
    #options: Doctrine\ORM\PersistentCollection {#93775 …}
    #associations: Doctrine\ORM\PersistentCollection {#93777 …}
    #createdAt: DateTime @1751040448 {#93808
      date: 2025-06-27 18:07:28.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93787
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93793 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93800}
        #id: 44861
        #name: "IEEE 2410:2021"
        #slug: "ieee-2410-2021-ieee00007746-244117"
        #description: """
          Revision Standard - Active.<br />\n
          The Standard for Biometric Privacy (SBP) provides private identity assertion. SBP supersedes the prior IEEE Std 2410(TM)-2019 by including a formal specification for privacy and biometrics such that a conforming SBP system does not incur GDPR, CCPA, BIPA or HIPAA privacy obligations. Homomorphic encryption ensures the biometric payload is always one-way encrypted with no need for key management and provides full privacy by ensuring plaintext biometrics are never received by the SBP server. The SBP implementation includes software running on a client device and on the SPB server. Pluggable components are used to replace legacy functionality to allow rapid integration into existing operating environments. The SBP implementation allows the systems to meet security needs by using the application programming interface, whether the underlying system is a relational database management system or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST ), JavaScript Object Notation (JSON), and Transport Layer Security (TLS) to provide the communication interface. This document describes<br />\n
          the essential methodology to SBP.<br />\n
          \t\t\t\t<br />\n
          The Standard for Biometric Privacy provides a biometric-agnostic security protocol for private authentication, identification, and liveness. The SBP implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS) or a search engine. The SBP implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. SBP additionally includes the biometric identification which the industry frequently calls the ‘one to many’ case. In the past, biometric identification was not considered because this requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic security protocol for authentication, identification, and liveness.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Privacy"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93791 …}
    #channels: Doctrine\ORM\PersistentCollection {#93784 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93789 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93786 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93801 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93771
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1624226400 {#93807
      date: 2021-06-21 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1621807200 {#93806
      date: 2021-05-24 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#93797 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93795 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113708
  +product: App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#113735
  +product: App\Entity\Product\Product {#7311
    #id: 12290
    #code: "IEEE00007405"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751040336 {#7274
      date: 2025-06-27 18:05:36.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#7322
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 44169
        #name: "IEEE 2410:2019"
        #slug: "ieee-2410-2019-ieee00007405-243943"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathering, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). An implementation of the BOPS III spec is described, which includes both the software running on the client device as well as the server. Pluggable components are allowed to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. A “point-and-cut” mechanism to add the appropriate security to both development and production systems is offered through the BOPS implementation functionality. Homomorphic encryption and a tremendous simplification of the API are also described.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides three application-programming interface (API) calls to support biometric identification and authentication including liveness. The BOPS implementation allows the systems to meet security needs by using the API. The BOPS implementation need not know whether the underlying system is a machine learning model, a relational database management system (RDBMS), or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          Additionally, BOPS includes the biometric identification that the industry frequently calls the “one-to-many” (1:M) case. In the past, biometric identification was not considered because it requires a lookup against previously stored biometrics and this lookup required indexing and storing the biometric in plain text biometric identification. This specification includes biometric identification by using biometric features vectors as input to the enroll endpoint, biometric feature vectors as input to the predict endpoint, and either video or audio as input to the liveness endpoint.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1622066400 {#7292
      date: 2021-05-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1561672800 {#7318
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @1561672800 {#7316
      date: 2019-06-28 00:00:00.0 Europe/Paris (+02:00)
    }
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 25
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113799
  +product: App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
]

App\Twig\Components\ProductMostRecent {#113826
  +product: App\Entity\Product\Product {#106802
    #id: 11935
    #code: "IEEE00006799"
    #attributes: Doctrine\ORM\PersistentCollection {#106785 …}
    #variants: Doctrine\ORM\PersistentCollection {#106782 …}
    #options: Doctrine\ORM\PersistentCollection {#106778 …}
    #associations: Doctrine\ORM\PersistentCollection {#106780 …}
    #createdAt: DateTime @1751040086 {#106810
      date: 2025-06-27 18:01:26.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106783
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106796 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#106828
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106802}
        #id: 42749
        #name: "IEEE 2410:2017"
        #slug: "ieee-2410-2017-ieee00006799-243587"
        #description: """
          Revision Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device, a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security (TLS) to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components' functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a &quot;point-and-cut&quot; mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106793 …}
    #channels: Doctrine\ORM\PersistentCollection {#106787 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106791 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106789 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106803 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106770
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#106809
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1508450400 {#106808
      date: 2017-10-20 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 88
    -documents: Doctrine\ORM\PersistentCollection {#106800 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106798 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#113503
    #id: 11331
    #code: "IEEE00005933"
    #attributes: Doctrine\ORM\PersistentCollection {#113525 …}
    #variants: Doctrine\ORM\PersistentCollection {#113527 …}
    #options: Doctrine\ORM\PersistentCollection {#113531 …}
    #associations: Doctrine\ORM\PersistentCollection {#113529 …}
    #createdAt: DateTime @1751039637 {#113498
      date: 2025-06-27 17:53:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113501
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113515 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113503}
        #id: 40333
        #name: "IEEE 2410:2015"
        #slug: "ieee-2410-2015-ieee00005933-242983"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device (smartphone or mobile device), a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113517 …}
    #channels: Doctrine\ORM\PersistentCollection {#113523 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113519 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113521 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113508 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113494
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1447974000 {#113509
      date: 2015-11-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#113511 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113513 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#113907
  +product: App\Entity\Product\Product {#113503
    #id: 11331
    #code: "IEEE00005933"
    #attributes: Doctrine\ORM\PersistentCollection {#113525 …}
    #variants: Doctrine\ORM\PersistentCollection {#113527 …}
    #options: Doctrine\ORM\PersistentCollection {#113531 …}
    #associations: Doctrine\ORM\PersistentCollection {#113529 …}
    #createdAt: DateTime @1751039637 {#113498
      date: 2025-06-27 17:53:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113501
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113515 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113503}
        #id: 40333
        #name: "IEEE 2410:2015"
        #slug: "ieee-2410-2015-ieee00005933-242983"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device (smartphone or mobile device), a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113517 …}
    #channels: Doctrine\ORM\PersistentCollection {#113523 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113519 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113521 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113508 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113494
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1447974000 {#113509
      date: 2015-11-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#113511 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113513 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#113503
    #id: 11331
    #code: "IEEE00005933"
    #attributes: Doctrine\ORM\PersistentCollection {#113525 …}
    #variants: Doctrine\ORM\PersistentCollection {#113527 …}
    #options: Doctrine\ORM\PersistentCollection {#113531 …}
    #associations: Doctrine\ORM\PersistentCollection {#113529 …}
    #createdAt: DateTime @1751039637 {#113498
      date: 2025-06-27 17:53:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113501
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113515 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113503}
        #id: 40333
        #name: "IEEE 2410:2015"
        #slug: "ieee-2410-2015-ieee00005933-242983"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device (smartphone or mobile device), a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113517 …}
    #channels: Doctrine\ORM\PersistentCollection {#113523 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113519 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113521 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113508 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113494
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1447974000 {#113509
      date: 2015-11-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#113511 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113513 …}
  }
]

App\Twig\Components\ProductMostRecent {#113959
  +product: App\Entity\Product\Product {#113503
    #id: 11331
    #code: "IEEE00005933"
    #attributes: Doctrine\ORM\PersistentCollection {#113525 …}
    #variants: Doctrine\ORM\PersistentCollection {#113527 …}
    #options: Doctrine\ORM\PersistentCollection {#113531 …}
    #associations: Doctrine\ORM\PersistentCollection {#113529 …}
    #createdAt: DateTime @1751039637 {#113498
      date: 2025-06-27 17:53:57.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607611 {#113501
      date: 2025-08-08 01:00:11.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#113515 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#113892
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#113503}
        #id: 40333
        #name: "IEEE 2410:2015"
        #slug: "ieee-2410-2015-ieee00005933-242983"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          Identity assertion, role gathereing, multilevel access control, assurance, and auditing are provided by the Biometric Open Protocol Standard (BOPS). The BOPS implementation includes software running on a client device (smartphone or mobile device), a trusted BOPS server, and an intrusion detection system. The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into current operating environments in a short period of time. The BOPS implementation provides continuous protection to the resources and assurance of the placement and viability of adjudication and other key features. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface. The BOPS implementation need not know whether the underlying system is a relational database management system or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development. The architecture is language neutral, allowing Representational State Transfer (REST), JavaScript Object Notation (JSON), and Secure Sockets Layer (SSL) or Transport Layer Security to provide the communication interface. The architecture is built on the servlet specification, open SSLs, Java, JSON, REST, and an open persistent store. All tools adhere to open standards, allowing maximum interoperability.<br />\n
          \t\t\t\t<br />\n
          The Biometric Open Protocol Standard (BOPS) provides identity assertion, role gathereing, multilevel access control, assurance, and auditing. The BOPS implementation includes software running on a client device (e.g., smartphone or mobile device), a trusted BOPS Server, and an intrusion detection system (IDS). The BOPS implementation allows pluggable components to replace existing components’ functionality, accepting integration into the current operating environments in a short period of time. The BOPS implementation adheres to the principle of continuous protection in adjudicating access to resources. Accountability is the mechanism that proves a service-level guarantee of security. The BOPS implementation allows the systems to meet security needs by using the application programming interface (API). The BOPS implementation need not know whether the underlying system is a relational database management system (RDBMS) or a search engine. The BOPS implementation functionality offers a “point-and-cut” mechanism to add the appropriate security to the production systems as well as to the systems in development.<br />\n
          This standard provides a biometric-agnostic, multilevel security protocol.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Biometric Open Protocol"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#113517 …}
    #channels: Doctrine\ORM\PersistentCollection {#113523 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#113519 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#113521 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#113508 …}
    -apiLastModifiedAt: DateTime @1754517600 {#113494
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#113491
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1447974000 {#113509
      date: 2015-11-20 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "2410"
    -bookCollection: ""
    -pageCount: 37
    -documents: Doctrine\ORM\PersistentCollection {#113511 …}
    -favorites: Doctrine\ORM\PersistentCollection {#113513 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}