ONVIF:...ension(3pm)

💖 NAME 💖

ONVIF::Analytics::Types::CapabilitiesExtension — bestie, this is a Perl data type class for the XML Schema defined complexType CapabilitiesExtension, and it lives in the namespace http://www.onvif.org/ver10/schema. That's the whole vibe. It's a 3pm man page, so like, Perl module documentation, and it's here to hold your ONVIF capability data together. Periodt. ✨

---

🌸 DESCRIPTION 🌸

Okay so, no cap: this class is the Perl data type class for the XML Schema defined complexType CapabilitiesExtension from the namespace http://www.onvif.org/ver10/schema.

That's it. That's the assignment. It's giving "faithful little type wrapper" and honestly? Iconic. 💅

🎀 PROPERTIES 🎀

Here's the tea — the following properties may be accessed using get_PROPERTY / set_PROPERTY methods:

• DeviceIO
• Display
• Recording
• Search
• Replay
• Receiver
• AnalyticsDevice
• Extensions

Eight of them. All accounted for. Not one skipped. We don't do that here. 🫶

---

✨ METHODS ✨

💜 new

Constructor, babes. The following data structure may be passed to new():

 { # ONVIF::Analytics::Types::CapabilitiesExtension
   DeviceIO =>  { # ONVIF::Analytics::Types::DeviceIOCapabilities
     XAddr =>  $some_value, # anyURI
     VideoSources =>  $some_value, # int
     VideoOutputs =>  $some_value, # int
     AudioSources =>  $some_value, # int
     AudioOutputs =>  $some_value, # int
     RelayOutputs =>  $some_value, # int
   },
   Display =>  { # ONVIF::Analytics::Types::DisplayCapabilities
     XAddr =>  $some_value, # anyURI
     FixedLayout =>  $some_value, # boolean
   },
   Recording =>  { # ONVIF::Analytics::Types::RecordingCapabilities
     XAddr =>  $some_value, # anyURI
     ReceiverSource =>  $some_value, # boolean
     MediaProfileSource =>  $some_value, # boolean
     DynamicRecordings =>  $some_value, # boolean
     DynamicTracks =>  $some_value, # boolean
     MaxStringLength =>  $some_value, # int
   },
   Search =>  { # ONVIF::Analytics::Types::SearchCapabilities
     XAddr =>  $some_value, # anyURI
     MetadataSearch =>  $some_value, # boolean
   },
   Replay =>  { # ONVIF::Analytics::Types::ReplayCapabilities
     XAddr =>  $some_value, # anyURI
   },
   Receiver =>  { # ONVIF::Analytics::Types::ReceiverCapabilities
     XAddr =>  $some_value, # anyURI
     RTP_Multicast =>  $some_value, # boolean
     RTP_TCP =>  $some_value, # boolean
     RTP_RTSP_TCP =>  $some_value, # boolean
     SupportedReceivers =>  $some_value, # int
     MaximumRTSPURILength =>  $some_value, # int
   },
   AnalyticsDevice =>  { # ONVIF::Analytics::Types::AnalyticsDeviceCapabilities
     XAddr =>  $some_value, # anyURI
     RuleSupport =>  $some_value, # boolean
     Extension =>  { # ONVIF::Analytics::Types::AnalyticsDeviceExtension
     },
   },
   Extensions =>  { # ONVIF::Analytics::Types::CapabilitiesExtension2
   },
 },

Look at that nested structure. It's giving ✨organised chaos✨ — every nested hash gets its own type comment, every leaf gets its schema type (anyURI, int, boolean), and $some_value is just vibes holding the spot. Note that Extensions and the inner Extension are lowkey empty hashes — that's not a bug, that's just how the schema rolls. 🙈

---

👑 AUTHOR 👑

Generated by SOAP::WSDL. Not me, not you, the machine did it. Respect the machine. 💀

---

That's the whole page, bestie! This was ONVIF:...ension(3pm) from the User Contributed Perl Documentation crew, built against perl v5.40.1 and stamped 2026-02-01. Go forth and set your properties, and remember: get_PROPERTY / set_PROPERTY is the only way in. Slay. 💅🎀🦋