Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#92877
  +product: App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductType {#93057
  +product: App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#93132
  +product: App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#100085
  +product: App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
]

App\Twig\Components\ProductMostRecent {#100169
  +product: App\Entity\Product\Product {#7311
    #id: 9298
    #code: "IEEE00002017"
    #attributes: Doctrine\ORM\PersistentCollection {#7701 …}
    #variants: Doctrine\ORM\PersistentCollection {#7744 …}
    #options: Doctrine\ORM\PersistentCollection {#7916 …}
    #associations: Doctrine\ORM\PersistentCollection {#7900 …}
    #createdAt: DateTime @1751038147 {#7274
      date: 2025-06-27 17:29:07.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753969444 {#7322
      date: 2025-07-31 15:44:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7922 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7921
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7311}
        #id: 32201
        #name: "IEEE 1327.1:1993"
        #slug: "ieee-1327-1-1993-ieee00002017-240950"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          A C language binding to IEEE Std 1224.1-1993, IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent] is defined. This standard is intended for use by application developers, system implementors, test method writers, and users to support application portability at the source-code level.<br />\n
          \t\t\t\t<br />\n
          This standard defines an ISO/IEC 9989: 1990 {1} C language binding to the language-independent API defined in IEEE Std 1224.1-1993 {3}.1) It is intended to support application portability at the source-code level and to be used by application developers, system implementors, test method writers, and users.<br />\n
          The purpose of this standard is to define a C programming language binding for the X.400-based electronic messaging Application Program Interface (API) that is defined in IEEE Std 1224.1-1993.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400 Based Electronic Messaging C Language Interfaces--Binding for Application Program Interfaces (API)"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7534 …}
    #channels: Doctrine\ORM\PersistentCollection {#7628 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7613 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7645 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7321 …}
    -apiLastModifiedAt: DateTime @1743289200 {#7317
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#7292
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#7318
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#7316
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1327.1"
    -bookCollection: ""
    -pageCount: 71
    -documents: Doctrine\ORM\PersistentCollection {#7465 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7500 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#121679
  +product: App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#121768
  +product: App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
]

App\Twig\Components\ProductMostRecent {#121845
  +product: App\Entity\Product\Product {#121576
    #id: 9209
    #code: "IEEE00001849"
    #attributes: Doctrine\ORM\PersistentCollection {#121559 …}
    #variants: Doctrine\ORM\PersistentCollection {#121557 …}
    #options: Doctrine\ORM\PersistentCollection {#121552 …}
    #associations: Doctrine\ORM\PersistentCollection {#121554 …}
    #createdAt: DateTime @1751038062 {#121549
      date: 2025-06-27 17:27:42.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121584
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121570 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121766
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121576}
        #id: 31845
        #name: "IEEE 1224:1993"
        #slug: "ieee-1224-1993-ieee00001849-240861"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Withdrawn Standard. Withdrawn Date: Mar 06, 2000. No longer endorsed by the IEEE. A general-purpose application program interface (API) for the creation, examination, modification, and deletion of potentially complex Open Systems Interconnection (OSI) information objects is defined in terms that are independent of any particular programming language. The API provides tools for manipulating objects defined using Abstract Syntax Notation One (ASN.1), shielding the application programmer from much of the complexity of ASN.1 It is designed to be used in conjunction with, but is otherwise independent of, application-specific APIs for OSI.<br />\n
          \t\t\t\t<br />\n
          This standard defines a standard interface supporting the manipulation of complex arguments and parameters used by X.400 and Directory Services APIs. The interface supports manipulation of abstract data defined in ASN.1 and is for use in conjunction with, but is otherwise independent of, the X.400 and Directory Services APIs. An application shall be able to link and use multiple implementations of this API. This standard provides a language-independent specification of an interface and environment to support application portability at the source-code level. It is intended to be used by application developers, system implementors, test method writers, and users. This standard describes the external characteristics and facilities that are of importance to applications developers, rather than the internal construction techniques employed to achieve these capabilities. Special emphasis is placed on those functions and facilities that are needed in a wide variety of commercial applications.<br />\n
          This document defines a general-purpose OSI Object Management Application Program Interface (API) for use in conjunction with, but otherwise independent of, other application-speciÞc APIs for Open Systems Interconnection (OSI). Object Management (OM) is the creation, examination, modification, and deletion of potentially complex information objects. It presents to programmers a uniform model, or architecture, of information based upon the concept of groups, or classes, of similar information objects. The OM API provides facilities to manipulate both small objects and those too large to be held in main memory. The information objects to which OM applies are those that arise in OSI, i.e., those that correspond to the types defined by, or by means of, Abstract Syntax Notation One (ASN. 1). The OM API comprises tools for manipulating ASN.1 objects. It shields the programmer from much of the complexity of ASN.1, e.g., its Basic Encoding Rules (BER). This API is designed to work with groups of ASN.1 objects that are called packages. These packages are defined by the application-speciÞc APIs that use this API. The packages contain all the ASN.1 objects necessary to accomplish a specific task. Thus, the API does not work with any arbitrary ASN.1 objects, only those deÞned in packages. The OM API is designed to be implemented by one or more manufacturers working independently. As illustrated in Figure 3-1 below, each manufacturer effectively provides the programmer with the ability to manipulate information objects of particular kinds. This division of implementation responsibility is achieved by means of workspaces (see 4.8). Throughout this document, the term interface denotes the OM API, the term service denotes software that supplies (i.e., implements) the interface, and the term client denotes software that uses the interface. The term service interface denotes the interface realized by the service as a whole, and it is thus a synonym for interface.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--Open Systems Interconnection (OSI) Abstract Data Manipulation--Application Program Interfaces (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121568 …}
    #channels: Doctrine\ORM\PersistentCollection {#121561 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121565 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121563 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121578 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121535
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121583
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @749257200 {#121542
      date: 1993-09-29 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121555
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224"
    -bookCollection: ""
    -pageCount: 94
    -documents: Doctrine\ORM\PersistentCollection {#121574 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121572 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
  "layout" => "vertical"
  "showPrice" => true
  "showStatusBadges" => true
  "additionalClasses" => "product__teaser--with-grey-border"
  "hasStretchedLink" => true
  "hoverType" => "shadow"
  "linkLabel" => "See more"
]

App\Twig\Components\ProductCard {#121920
  +product: App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
  +layout: "vertical"
  +showPrice: true
  +showStatusBadges: true
  +additionalClasses: "product__teaser--with-grey-border"
  +linkLabel: "See more"
  +imageFilter: "product_thumbnail_teaser"
  +hasStretchedLink: true
  +backgroundColor: "white"
  +hoverType: "shadow"
}

[
  "product" => App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
]

[
  "showFullLabel" => false
]

App\Twig\Components\ProductState {#121969
  +product: App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
  +appearance: "state-withdrawn"
  +labels: [
    "Withdrawn"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
]

App\Twig\Components\ProductMostRecent {#122046
  +product: App\Entity\Product\Product {#121543
    #id: 9211
    #code: "IEEE00001851"
    #attributes: Doctrine\ORM\PersistentCollection {#121627 …}
    #variants: Doctrine\ORM\PersistentCollection {#121626 …}
    #options: Doctrine\ORM\PersistentCollection {#121621 …}
    #associations: Doctrine\ORM\PersistentCollection {#121623 …}
    #createdAt: DateTime @1751038064 {#121550
      date: 2025-06-27 17:27:44.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754607004 {#121548
      date: 2025-08-08 00:50:04.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#121624 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#121962
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#121543}
        #id: 31853
        #name: "IEEE 1224.1:1993"
        #slug: "ieee-1224-1-1993-ieee00001851-240863"
        #description: """
          New IEEE Standard - Inactive-Withdrawn.<br />\n
          Application program interfaces (APIs) to X.400-based electronic messaging services are defined in terms that are independent of any particular programming language. A general-purpose API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA, is provided. An X.400 gateway API divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service. This standard, and the language bindings derived from it, are intended to be used in conjunction with IEEE Std 1224-1993, which provides a general-purpose API for the creation, examination, modification, and deletion of OSI information objects.<br />\n
          \t\t\t\t<br />\n
          The purpose of this standard is to provide APIs supporting the development of applications that are users of the message transfer system, and gateways that incorporate or use X.400 mail functionality. This includes gateways between X.400 mail networks and proprietary mail systems. The interface supports access to X.400 services. The standard defines two application program interfaces to X.400-based electronic messaging systems. The interfaces are An X.400 API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UAAn X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a messaging system gateway and an X.400 gateway service This standard provides a language-independent specification.<br />\n
          This standard defines two application program interfaces (APIs) of architectural importance in the construction of message handling systems (MHS). It defines an X.400 Application API that makes the functionality of a message transfer system (MTS) accessible to a message store (MS) or user agent (UA), or the functionality of a simple MS accessible to a UA. It also defines an X.400 Gateway API that divides a message transfer agent (MTA) into two software components, a mail system gateway and an X. 400 gateway service. The two interfaces support Message Access (MA), Message Transfer (MT), and Interpersonal Messaging (IM). MA is the conveyance of information objects between the MTS and one of its users, and thereby among its various users. MT is the conveyance of such objects between the MTAs that make up the MTS. IM is the MA and MT application in which the contents of messages are electronic memos. The interfaces address the operational requirements of these activities; they do not address their system management requirements, for example, those for security. NOTE -- Of the many applications of MA and MT, IM is singled out by this standard only because it is singled out by X.400 itself. (X.400 highlights IM for purely historical reasons.) The use of the interfaces is not limited to IM. Since they permit the contents of messages to be arbitrary binary data, the interfaces are germane to all applications, e.g., electronic data interchange (EDI). Henceforth, the following terms are used consistently as indicated. The terms MA interface and MT interface denote the X.400 Application API and the X.400 Gateway API, respectively. The term interface denotes either interface without distinction, or one interface in particular. If the latter, which interface is meant will be clear from the context. The term service denotes software that implements an interface. A service that implements the MA interface realizes the MTS. A service that implements the MT interface realizes an X.400 gateway service. The term client denotes software that uses an interface. A client that uses the MA interface realizes a UA or an MS. A client that uses the MT interface realizes a mail system gateway. NOTE -- The MA interface does not provide the functionality of the MS Abstract Service of X.400 (its P7 protocol), although it can be viewed as providing a small portion of it. The functionality of P7 is outside the scope of this standard. The message storage and retrieval capabilities of a mail system are among its most important product-differentiating aspects.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE Standard for Information Technology--X.400-Based Electronic Messaging--Application Program Interface (API) [Language Independent]"
        -notes: "Inactive-Withdrawn"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#121609 …}
    #channels: Doctrine\ORM\PersistentCollection {#121632 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7309 …}
    #reviews: Doctrine\ORM\PersistentCollection {#121587 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#121633 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7324 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#121541 …}
    -apiLastModifiedAt: DateTime @1754517600 {#121547
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1578006000 {#121546
      date: 2020-01-03 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @757206000 {#121545
      date: 1993-12-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: DateTime @952297200 {#121544
      date: 2000-03-06 00:00:00.0 Europe/Paris (+01:00)
    }
    -edition: null
    -coreDocument: "1224.1"
    -bookCollection: ""
    -pageCount: 147
    -documents: Doctrine\ORM\PersistentCollection {#121539 …}
    -favorites: Doctrine\ORM\PersistentCollection {#121532 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}