ONVIF:...ficate(3pm)

πŸ“¦
version 1.36.37 Β· 5 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– ONVIF::Media::Types::Certificate πŸ’–

okay bestie, welcome to the manual page for ONVIF::Media::Types::Certificate β€” yes the header shows it all squished as ONVIF:...ficate(3pm) but you and me both know what it really is πŸ’… this is a User Contributed Perl Documentation situation, so grab your strawberry drink and let's go πŸ“


✨ NAME ✨

ONVIF::Media::Types::Certificate β€” that's the whole name, no notes, periodt πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

It's a Perl data type class for the XML Schema defined complexType called Certificate, and it lives in the namespace http://www.onvif.org/ver10/schema 🌈

That's it. That's the vibe. It's giving "I exist so XML can be Perl" and honestly? iconic.


πŸŽ€ PROPERTIES πŸŽ€

so here's the tea β€” these properties are all accessible using the get_PROPERTY / set_PROPERTY methods. like, that's the whole access pattern, no cap πŸ”₯

  • CertificateID πŸ’œ
  • Certificate πŸ’œ

🌸 METHODS 🌸

⭐ new ⭐

Constructor, babes 🫢 and the way that it works is you can pass it this exact data structure:

 { # ONVIF::Media::Types::Certificate
   CertificateID =>  $some_value, # token
   Certificate =>  { # ONVIF::Media::Types::BinaryData
     Data =>  $some_value, # base64Binary
   },
 },

look at that nested beauty β€” a CertificateID (a token, cute) and a Certificate which is itself a ONVIF::Media::Types::BinaryData holding a Data value typed as base64Binary πŸ¦‹ she's got layers, she's complex, she's literally the main character.


πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL β€” not me writing it by hand, the machine did that ✨ and it ate, fr fr.


perl v5.40.1 🌸 2026-02-01 🌸 and that's the whole page bestie, mwah, go forth and construct your Certificates responsibly πŸ’–πŸŽ€πŸ’…

πŸ“¦ where this page comes from