Components
5
Twig Components
29
Render Count
80
ms
Render Time
74.0
MiB
Memory Usage
Components
| Name | Metadata | Render Count | Render Time |
|---|---|---|---|
| ProductCard |
"App\Twig\Components\ProductCard"components/ProductCard.html.twig |
9 | 75.03ms |
| ProductState |
"App\Twig\Components\ProductState"components/ProductState.html.twig |
9 | 2.06ms |
| ProductMostRecent |
"App\Twig\Components\ProductMostRecent"components/ProductMostRecent.html.twig |
9 | 7.84ms |
| PageBanner |
"App\Twig\Components\PageBanner"components/PageBanner.html.twig |
1 | 4.63ms |
| BackButton |
"App\Twig\Components\BackButton"components/BackButton.html.twig |
1 | 0.22ms |
Render calls
| PageBanner | App\Twig\Components\PageBanner | 72.0 MiB | 4.63 ms | |
|---|---|---|---|---|
| Input props | [ "backLabel" => "35.240 : Applications of information technology" "backUrl" => "/taxons/main/ics-2277/35-information-technology-office-machines-5714/35-240-applications-of-information-technology-4986" "paddingClasses" => "p-2 px-lg-5 py-lg-0" "searchPlaceholder" => "sylius.ui.search" "showSearch" => "true" "title" => "35.240.15 : Identification cards and related devices" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\PageBanner {#94263 +supTitle: null +title: "35.240.15 : Identification cards and related devices" +subTitle: null +backUrl: "/taxons/main/ics-2277/35-information-technology-office-machines-5714/35-240-applications-of-information-technology-4986" +backLabel: "35.240 : Applications of information technology" +customClasses: null +backgroundType: null +centered: true +showSearch: true +searchPlaceholder: "sylius.ui.search" +searchValue: null +paddingClasses: "p-2 px-lg-5 py-lg-0" } |
|||
| BackButton | App\Twig\Components\BackButton | 72.0 MiB | 0.22 ms | |
|---|---|---|---|---|
| Input props | [ "url" => "/taxons/main/ics-2277/35-information-technology-office-machines-5714/35-240-applications-of-information-technology-4986" "label" => "35.240 : Applications of information technology" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\BackButton {#94365 +label: "35.240 : Applications of information technology" +url: "/taxons/main/ics-2277/35-information-technology-office-machines-5714/35-240-applications-of-information-technology-4986" } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 13.46 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "white" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#95209 +product: App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.41 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#95301 +product: App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 1.04 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#95395 +product: App\Entity\Product\Product {#94880 #id: 11331 #code: "IEEE00005933" #attributes: Doctrine\ORM\PersistentCollection {#94947 …} #variants: Doctrine\ORM\PersistentCollection {#94945 …} #options: Doctrine\ORM\PersistentCollection {#94941 …} #associations: Doctrine\ORM\PersistentCollection {#94943 …} #createdAt: DateTime @1751039637 {#94879 : 2025-06-27 17:53:57.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754607611 {#94890 : 2025-08-08 01:00:11.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94957 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95294 #locale: "en_US" #translatable: App\Entity\Product\Product {#94880} #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 {#94955 …} #channels: Doctrine\ORM\PersistentCollection {#94949 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94953 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94951 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94963 …} -apiLastModifiedAt: DateTime @1754517600 {#94896 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94899 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1447974000 {#94897 : 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 {#94961 …} -favorites: Doctrine\ORM\PersistentCollection {#94959 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.23 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "secondary-lighter" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#95586 +product: App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "secondary-lighter" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.20 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#95622 +product: App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.85 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#95696 +product: App\Entity\Product\Product {#94934 #id: 11935 #code: "IEEE00006799" #attributes: Doctrine\ORM\PersistentCollection {#94928 …} #variants: Doctrine\ORM\PersistentCollection {#94930 …} #options: Doctrine\ORM\PersistentCollection {#94965 …} #associations: Doctrine\ORM\PersistentCollection {#94932 …} #createdAt: DateTime @1751040086 {#94939 : 2025-06-27 18:01:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#94938 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94905 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95608 #locale: "en_US" #translatable: App\Entity\Product\Product {#94934} #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 "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 {#94922 …} #channels: Doctrine\ORM\PersistentCollection {#94926 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94921 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94924 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94909 …} -apiLastModifiedAt: DateTime @1754517600 {#94937 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1578006000 {#94936 : 2020-01-03 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1508450400 {#94935 : 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 {#94912 …} -favorites: Doctrine\ORM\PersistentCollection {#94907 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 9.02 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "white" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#95818 +product: App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.21 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#95852 +product: App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.87 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#95926 +product: App\Entity\Product\Product {#94972 #id: 12253 #code: "IEEE00007332" #attributes: Doctrine\ORM\PersistentCollection {#94989 …} #variants: Doctrine\ORM\PersistentCollection {#94991 …} #options: Doctrine\ORM\PersistentCollection {#94995 …} #associations: Doctrine\ORM\PersistentCollection {#94993 …} #createdAt: DateTime @1751040312 {#94967 : 2025-06-27 18:05:12.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94968 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#94979 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#95838 #locale: "en_US" #translatable: App\Entity\Product\Product {#94972} #id: 44021 #name: "IEEE 2790:2020" #slug: "ieee-2790-2020-ieee00007332-243906" #description: """ New IEEE Standard - Active.<br />\n A biometric lifeless attack is one of the indispensable issues within biometric authentication. There are three major components in liveness detection systems: lifeless attack presentation, liveness detection, and lifeless attack instruments. The lifeless attack presentation is divided into artifact presentation and human-based presentation. The liveness detection method includes subject-based and scenario-based solutions, as well as other attributes such as decision elements, detection patterns, and implementations. The lifeless attack instrument is specified from aspects such as production elements, production types of artifacts, efficacy, etc. This document establishes terms and definitions in the field of biometric liveness detection and identifies characterizations of lifeless attack and liveness detection methods, with analysis on lifeless attack instruments. In addition, this document specifies the liveness detection process, implementation model, and metrics.<br />\n \t\t\t\t<br />\n This document establishes terms and definitions in the field of biometric liveness detection and identifies characteristics of lifeless attacks and liveness detection methods, with analysis of lifeless attack instruments (LAIs). In addition, this document specifies liveness detection process and metrics. The following is outside of the scope of this document: Standardization of specific liveness detection methods; Detailed information about countermeasures, algorithms, or sensors; Overall system-level security; Security evaluation and vulnerability assessment; Integrated implementation of liveness detection subsystem within general biometric framework<br />\n This document provides a foundation for biometric liveness detection through which lifeless attacks can be specified, detected, and subsequently categorized and analyzed for biometric system performance. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Liveness Detection" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#94981 …} #channels: Doctrine\ORM\PersistentCollection {#94987 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#94983 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#94985 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#94973 …} -apiLastModifiedAt: DateTime @1743289200 {#94969 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1589752800 {#94970 : 2020-05-18 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1587679200 {#94971 : 2020-04-24 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2790" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#94975 …} -favorites: Doctrine\ORM\PersistentCollection {#94977 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.96 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "secondary-lighter" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#96056 +product: App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "secondary-lighter" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.22 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#96094 +product: App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } +appearance: "state-suspended" +labels: [ "Superseded" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.91 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#96168 +product: App\Entity\Product\Product {#95003 #id: 12290 #code: "IEEE00007405" #attributes: Doctrine\ORM\PersistentCollection {#95020 …} #variants: Doctrine\ORM\PersistentCollection {#95022 …} #options: Doctrine\ORM\PersistentCollection {#95026 …} #associations: Doctrine\ORM\PersistentCollection {#95024 …} #createdAt: DateTime @1751040336 {#94997 : 2025-06-27 18:05:36.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#94998 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95010 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96076 #locale: "en_US" #translatable: App\Entity\Product\Product {#95003} #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 {#95012 …} #channels: Doctrine\ORM\PersistentCollection {#95018 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95014 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95016 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95004 …} -apiLastModifiedAt: DateTime @1743289200 {#94999 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1622066400 {#95000 : 2021-05-27 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1561672800 {#95001 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: DateTime @1561672800 {#95002 : 2019-06-28 00:00:00.0 Europe/Paris (+02:00) } -edition: null -coreDocument: "2410" -bookCollection: "" -pageCount: 25 -documents: Doctrine\ORM\PersistentCollection {#95006 …} -favorites: Doctrine\ORM\PersistentCollection {#95008 …} } +label: "Historical" +icon: "historical" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.86 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "white" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#96307 +product: App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.23 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#96341 +product: App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.90 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#96415 +product: App\Entity\Product\Product {#95033 #id: 12463 #code: "IEEE00007746" #attributes: Doctrine\ORM\PersistentCollection {#95050 …} #variants: Doctrine\ORM\PersistentCollection {#95052 …} #options: Doctrine\ORM\PersistentCollection {#95056 …} #associations: Doctrine\ORM\PersistentCollection {#95054 …} #createdAt: DateTime @1751040448 {#95028 : 2025-06-27 18:07:28.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95029 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95040 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96327 #locale: "en_US" #translatable: App\Entity\Product\Product {#95033} #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 {#95042 …} #channels: Doctrine\ORM\PersistentCollection {#95048 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95044 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95046 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95034 …} -apiLastModifiedAt: DateTime @1743289200 {#95030 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1624226400 {#95031 : 2021-06-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1621807200 {#95032 : 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 {#95036 …} -favorites: Doctrine\ORM\PersistentCollection {#95038 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.49 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "secondary-lighter" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#96537 +product: App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "secondary-lighter" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.21 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#96571 +product: App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.90 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#96645 +product: App\Entity\Product\Product {#95063 #id: 12550 #code: "IEEE00010146" #attributes: Doctrine\ORM\PersistentCollection {#95080 …} #variants: Doctrine\ORM\PersistentCollection {#95082 …} #options: Doctrine\ORM\PersistentCollection {#95086 …} #associations: Doctrine\ORM\PersistentCollection {#95084 …} #createdAt: DateTime @1751040506 {#95058 : 2025-06-27 18:08:26.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95059 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95070 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96557 #locale: "en_US" #translatable: App\Entity\Product\Product {#95063} #id: 45209 #name: "IEEE 2859:2023" #slug: "ieee-2859-2023-ieee00010146-244205" #description: """ New IEEE Standard - Active.<br />\n A multi-modal fusion technology framework for the biometric system, which specifies multi-modal fusion architecture, functional requirements, business processes, performance requirements and security requirements is proposed in this standard.<br />\n \t\t\t\t<br />\n This document establishes a technical framework for a biometric multimodal fusion system (BMFS), describes business processes, and specifies the functional requirements, performance requirements, and security requirements of a biometric multi-modal fusion system. This document is applicable for design, development, testing, and application of biometric multi-modal products.<br />\n This document provides a framework and detailed requirements for a biometric multi-modal fusion system through which a secure multi-modal fusion system can be established. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Biometric Multi-modal Fusion" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95072 …} #channels: Doctrine\ORM\PersistentCollection {#95078 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95074 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95076 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95064 …} -apiLastModifiedAt: DateTime @1743289200 {#95060 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1692568800 {#95061 : 2023-08-21 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1690840800 {#95062 : 2023-08-01 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2859" -bookCollection: "" -pageCount: 24 -documents: Doctrine\ORM\PersistentCollection {#95066 …} -favorites: Doctrine\ORM\PersistentCollection {#95068 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.80 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "white" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#96767 +product: App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.24 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#96801 +product: App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.91 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#96875 +product: App\Entity\Product\Product {#95093 #id: 12616 #code: "IEEE00010304" #attributes: Doctrine\ORM\PersistentCollection {#95110 …} #variants: Doctrine\ORM\PersistentCollection {#95112 …} #options: Doctrine\ORM\PersistentCollection {#95116 …} #associations: Doctrine\ORM\PersistentCollection {#95114 …} #createdAt: DateTime @1751040550 {#95088 : 2025-06-27 18:09:10.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1753970953 {#95089 : 2025-07-31 16:09:13.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95100 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#96787 #locale: "en_US" #translatable: App\Entity\Product\Product {#95093} #id: 45473 #name: "IEEE 2884:2023" #slug: "ieee-2884-2023-ieee00010304-244271" #description: """ New IEEE Standard - Active.<br />\n Requirements and testing methods for a facial recognition testing system for end user devices are discussed in this standard. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are also defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements.<br />\n \t\t\t\t<br />\n This standard defines requirements and testing methods for a facial recognition testing system for end user device. System and security requirements, algorithm testing, testing methods, and criteria-level definitions are defined. Key metrics for quantized performance evaluation indexes including false accept rate (FAR), false reject rate (FRR), attack presentation false acceptance (APFAR), and bona fide presentation false rejection rate (BFPFRR) are defined. Criteria levels for testing the performance indexes are specified, including the detailed steps, environment, and minimum requirements. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Facial Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95102 …} #channels: Doctrine\ORM\PersistentCollection {#95108 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95104 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95106 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95094 …} -apiLastModifiedAt: DateTime @1743289200 {#95090 : 2025-03-30 00:00:00.0 Europe/Paris (+01:00) } -lastUpdatedAt: DateTime @1698012000 {#95091 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1694728800 {#95092 : 2023-09-15 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2884" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95096 …} -favorites: Doctrine\ORM\PersistentCollection {#95098 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.11 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "secondary-lighter" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#96997 +product: App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "secondary-lighter" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.19 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#97031 +product: App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.84 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#97105 +product: App\Entity\Product\Product {#95123 #id: 12617 #code: "IEEE00010306" #attributes: Doctrine\ORM\PersistentCollection {#95140 …} #variants: Doctrine\ORM\PersistentCollection {#95142 …} #options: Doctrine\ORM\PersistentCollection {#95146 …} #associations: Doctrine\ORM\PersistentCollection {#95144 …} #createdAt: DateTime @1751040551 {#95118 : 2025-06-27 18:09:11.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608621 {#95119 : 2025-08-08 01:17:01.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95130 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97017 #locale: "en_US" #translatable: App\Entity\Product\Product {#95123} #id: 45477 #name: "IEEE 2891:2023" #slug: "ieee-2891-2023-ieee00010306-244272" #description: """ New IEEE Standard - Active.<br />\n The components of a fingerprint test system for smart devices, such as a mobile phone are specified in this standard. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures and result reporting. Performance metrics which reflect expected device usage are specified, including false accept rate and false reject rate. Multiple testing levels are defined to support a variety of device types.<br />\n \t\t\t\t<br />\n This standard specifies components of a fingerprint test system for smart devices, such as a mobile phone. Test system requirements are specified together with criteria for performance evaluation, testing methods and procedures, and result reporting. Performance metrics that reflect expected device usage are specified, including false accept rates (FARs) and false reject rates (FRRs). Multiple testing levels are defined to support a variety of device types. This document is applicable for performance testing and the application of a fingerprint authentication system.<br />\n This document aims to set the requirements of fingerprint authentication systems on mobile phones and provide detailed test or verification procedures for fingerprint authentication systems. These test or verification requirements are the minimum requirements following the test procedure. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Standard for Performance Evaluation of Biometric Information: Fingerprint Recognition" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95132 …} #channels: Doctrine\ORM\PersistentCollection {#95138 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95134 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95136 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95124 …} -apiLastModifiedAt: DateTime @1754517600 {#95120 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1698012000 {#95121 : 2023-10-23 00:00:00.0 Europe/Paris (+02:00) } -author: "" -publishedAt: DateTime @1695333600 {#95122 : 2023-09-22 00:00:00.0 Europe/Paris (+02:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "2891" -bookCollection: "" -pageCount: 29 -documents: Doctrine\ORM\PersistentCollection {#95126 …} -favorites: Doctrine\ORM\PersistentCollection {#95128 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductCard | App\Twig\Components\ProductCard | 74.0 MiB | 7.09 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } "layout" => "vertical" "showPrice" => true "showStatusBadges" => true "imageFilter" => "product_listing_thumbnail" "additionalClasses" => "h-100 border-0" "hasStretchedLink" => true "backgroundColor" => "white" "hoverType" => "border-black" ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductCard {#97227 +product: App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } +layout: "vertical" +showPrice: true +showStatusBadges: true +additionalClasses: "h-100 border-0" +linkLabel: "" +imageFilter: "product_listing_thumbnail" +hasStretchedLink: true +backgroundColor: "white" +hoverType: "border-black" } |
|||
| ProductState | App\Twig\Components\ProductState | 74.0 MiB | 0.16 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } ] |
|||
| Attributes | [ "showFullLabel" => false ] |
|||
| Component | App\Twig\Components\ProductState {#97261 +product: App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } +appearance: "state-active" +labels: [ "Active" ] -stateAttributeCode: "state" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||
| ProductMostRecent | App\Twig\Components\ProductMostRecent | 74.0 MiB | 0.62 ms | |
|---|---|---|---|---|
| Input props | [ "product" => App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } ] |
|||
| Attributes | [] |
|||
| Component | App\Twig\Components\ProductMostRecent {#97334 +product: App\Entity\Product\Product {#95153 #id: 12943 #code: "IEEE00011023" #attributes: Doctrine\ORM\PersistentCollection {#95170 …} #variants: Doctrine\ORM\PersistentCollection {#95172 …} #options: Doctrine\ORM\PersistentCollection {#95176 …} #associations: Doctrine\ORM\PersistentCollection {#95174 …} #createdAt: DateTime @1751040761 {#95148 : 2025-06-27 18:12:41.0 Europe/Paris (+02:00) } #updatedAt: DateTime @1754608190 {#95149 : 2025-08-08 01:09:50.0 Europe/Paris (+02:00) } #enabled: true #translations: Doctrine\ORM\PersistentCollection {#95160 …} #translationsCache: [ "en_US" => App\Entity\Product\ProductTranslation {#97247 #locale: "en_US" #translatable: App\Entity\Product\Product {#95153} #id: 46781 #name: "IEEE 3188:2024" #slug: "ieee-3188-2024-ieee00011023-244601" #description: """ New IEEE Standard - Active - Draft.<br />\n This standard defines a reference architecture and technical requirements for virtual e-card, which is used for identity verification, mobile payment, and access control.<br />\n \t\t\t\t<br />\n This standard defines a reference architecture for virtual e-card. The standard considers e-cards used for identity verification, mobile payment, and access control. The standard's reference architecture includes the following technical requirements: -Platform capabilities including unified authentication, unified portal access, unified payment, unified Internet of Things (IoT) device integration; -interface requirements; -security requirements.<br />\n This standard helps enterprises to improve collaboration efficiency in the virtual e-card industry chain. It provides unified technical specifications to resolve problems such as weak design ability, long development cycle and serious waste of repeated construction of various application and equipment manufacturers connected to the virtual e-card platform. """ #metaKeywords: null #metaDescription: null #shortDescription: "IEEE Draft Standard for Virtual E-card Platform" -notes: "Active" } ] #currentLocale: "en_US" #currentTranslation: null #fallbackLocale: "en_US" #variantSelectionMethod: "match" #productTaxons: Doctrine\ORM\PersistentCollection {#95162 …} #channels: Doctrine\ORM\PersistentCollection {#95168 …} #mainTaxon: App\Entity\Taxonomy\Taxon {#8840 …} #reviews: Doctrine\ORM\PersistentCollection {#95164 …} #averageRating: 0.0 #images: Doctrine\ORM\PersistentCollection {#95166 …} -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#94964 …} -subscriptionCollections: Doctrine\ORM\PersistentCollection {#95154 …} -apiLastModifiedAt: DateTime @1754517600 {#95150 : 2025-08-07 00:00:00.0 Europe/Paris (+02:00) } -lastUpdatedAt: DateTime @1734303600 {#95151 : 2024-12-16 00:00:00.0 Europe/Paris (+01:00) } -author: "" -publishedAt: DateTime @1732230000 {#95152 : 2024-11-22 00:00:00.0 Europe/Paris (+01:00) } -releasedAt: null -confirmedAt: null -canceledAt: null -edition: null -coreDocument: "3188" -bookCollection: "" -pageCount: 27 -documents: Doctrine\ORM\PersistentCollection {#95156 …} -favorites: Doctrine\ORM\PersistentCollection {#95158 …} } +label: "Most Recent" +icon: "check-xs" -mostRecentAttributeCode: "most_recent" -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …} } |
|||