ONVIF:...tTypes(3pm)

✨ NAME ✨

ONVIF::Media::Attributes::expectedContentTypes — bestie, say that three times fast, I dare you 💅

This page lives in the User Contributed Perl Documentation corner of your manual, so pull up a chair, grab a boba, and let's get into it 🧋

---

🦋 DESCRIPTION 🦋

Okay so. This is a Perl data type class — and no, it's not a class about data types in the cool CS-y sense, it's the Perl-side stand-in for one specific XML Schema attribute. Which attribute, you ask? The one literally named expectedContentTypes, and it hangs out in the namespace:

http://www.w3.org/2005/05/xmlmime

That's it. That's the whole vibe. It exists so your Perl code has something to point at when the XML says "hey, here's the content types you should expect." Very demure, very mindful, very XML Schema of it 🎀

---

🌸 METHODS 🌸

new

my $element = ONVIF::Media::Attributes::expectedContentTypes->new($data);

It's giving constructor energy ✨ You call new on the class, hand it some $data, and boom — you've got yourself an element. Main character moment, honestly 👑

And what does that $data need to look like? Glad you asked, bestie, because here's the exact structure you can pass to new():

{ value => $value }

That's the whole shape. One key, value, one value, $value. Lowkey the simplest data structure in the entire ONVIF cinematic universe and I'm obsessed 🫶

---

💖 AUTHOR 💖

Generated by SOAP::WSDL — so, not a human author with a Twitter and opinions, just the machine doing machine things 🤖✨

---

And that's the whole page, no cap! This lil' doc came to you courtesy of perl v5.40.1 and it's dated 2026-02-01 — yes, from the future, don't think about it too hard 🙈 Take care of yourself, hydrate, and go write some well-typed XML, you absolute icon 💅🌈