ONVIF:...lities(3pm)

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

πŸ’– NAME πŸ’–

ONVIF::PTZ::Types::AnalyticsDeviceCapabilities β€” bestie, it's a whole Perl data type class, and she's serving AnalyticsDeviceCapabilities realness ✨

So like, quick vibe check: this manual page lives in the 3pm section (that's the Perl module girlies), and it's filed under User Contributed Perl Documentation. Periodt. πŸŽ€


🌸 DESCRIPTION 🌸

Okay so here's the tea, bestie πŸ«– β€” this is a Perl data type class for the XML Schema defined complexType AnalyticsDeviceCapabilities, and she comes straight out of the namespace http://www.onvif.org/ver10/schema.

That's it, that's the whole vibe. She's a type class. She holds the schema. She does it iconically. πŸ’…

πŸ¦‹ PROPERTIES πŸ¦‹

Not me gatekeeping β€” these are the properties you can access using get_PROPERTY / set_PROPERTY methods, fr fr:

  • XAddr
  • RuleSupport
  • Extension

Three of them. Little trio. Main character energy each one. 😭


✨ METHODS ✨

🧚 new

Constructor, babe. Slay. And here's the data structure you may pass to new() β€” copied exactly, no cap, do not touch:

 { # ONVIF::PTZ::Types::AnalyticsDeviceCapabilities
   XAddr =>  $some_value, # anyURI
   RuleSupport =>  $some_value, # boolean
   Extension =>  { # ONVIF::PTZ::Types::AnalyticsDeviceExtension
   },
 },

Look at her. XAddr is an anyURI, RuleSupport is a boolean, and Extension is a nested ONVIF::PTZ::Types::AnalyticsDeviceExtension hashref that's lowkey just vibing empty in the example. The way that nesting works? Obsessed. πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

Generated by SOAP::WSDL πŸ¦‹

Like, she was generated. Born ready. Didn't even have to try. ✨


and that's the whole page bestie, go forth and instantiate responsibly 🫢

Perl v5.40.1, dated 2026-02-01, and it's the ONVIF:...lities(3pm) page β€” mwah, love u, bye πŸ’–πŸŒˆπŸŽ€

πŸ“¦ where this page comes from