ONVIF:...lities(3pm)

🌸 NAME 🌸

ONVIF::Device::Types::IOCapabilities — and yes bestie, this is a 3pm page, so it's User Contributed Perl Documentation energy all the way 💅

---

✨ DESCRIPTION ✨

okay so. this is a Perl data type class — that's the whole job, that's the whole vibe 🫶

it exists for the XML Schema complexType called IOCapabilities, and it lives in the namespace http://www.onvif.org/ver10/schema. that's it, that's the girl. she's a data type class and she's serving 💖

---

🎀 PROPERTIES 🎀

the following properties can be reached using get_PROPERTY / set_PROPERTY methods — yes, that exact naming, PROPERTY gets swapped for the real one, iykyk 😌

• InputConnectors
• RelayOutputs
• Extension

those three, in that order, no notes 🔥

---

💜 METHODS 💜

🦋 new 🦋

Constructor bestie!! 🌈 the following data structure may be passed to new():

 { # ONVIF::Device::Types::IOCapabilities
   InputConnectors =>  $some_value, # int
   RelayOutputs =>  $some_value, # int
   Extension =>  { # ONVIF::Device::Types::IOCapabilitiesExtension
     Auxiliary =>  $some_value, # boolean
     AuxiliaryCommands => $some_value, # AuxiliaryData
     Extension =>  { # ONVIF::Device::Types::IOCapabilitiesExtension2
     },
   },
 },

look at her. nested Extension inside Extension — it's giving main character energy, it's giving layers, it's giving 🧚✨

quick vibe check: InputConnectors and RelayOutputs are int, Auxiliary is boolean, AuxiliaryCommands is AuxiliaryData, and that innermost Extension (ONVIF::Device::Types::IOCapabilitiesExtension2) is just… vibes. empty. iconic honestly 💀

---

👑 AUTHOR 👑

Generated by SOAP::WSDL — not me, not you, the machine did it and honestly? ate 🍓

---

and that's the whole page bestie, no cap, every option, every property, every nested curly brace accounted for 💅✨

this was perl v5.40.1, dated 2026-02-01, from the ONVIF:...lities(3pm) page — love that for us, mwah 🫶💖