Net::RDAP::Values(3)
πΈ NAME πΈ
Net::RDAP::Values β it's a Perl module (section 3, from the User Contributed Perl Documentation collection, bestie) that gives you an interface to the RDAP values registry. That's it, that's the whole vibe. π
β¨ DESCRIPTION β¨
okay so picture this: the RDAP JSON Values Registry got defined way back in RFC 7483, and what it does is list out all the permitted values for certain RDAP object properties. And this class? This class is literally just an interface to that registry. That's its whole job. Main character behavior, honestly. π
But here's the iconic plot twist π β the registry is only available in CSV and XML formats. No JSON, no nothing. So this module has to pull in XML::LibXML just to access the registry data that it retrieves from the IANA web server. The irony is not lost on anyone. It's giving "using a sledgehammer to open a snack wrapper" and honestly? We respect it. π
π METHODS π
check() β
Net::RDAP::Values->check($value, $type);
Net::RDAP::Values->check('add period', RDAP_TYPE_STATUS);
Net::RDAP::Values->check('registration', RDAP_TYPE_EVENT_ACTION);
so check() is your vibe check, literally β it lets you figure out if a given value is actually present in the registry. π΅οΈββοΈ You also have to tell it what type the value is, using one of the RDAP_TYPE_* constants. No type, no answer, that's the deal.
If the value is registered in the registry, this method hands you back a true value. If it's not? You get undef. That's it. Simple. Devastating. π«Ά
values() π
@values = Net::RDAP::Values->values($type);
@values = Net::RDAP::Values->values(RDAP_TYPE_ROLE);
values() returns a whole list of the permitted values for whatever value type you hand it. Very "here's the guest list, you're not on it" energy. π
β οΈ heads up bestie β if you specify an invalid type, an exception is raised. So like, double-check your type before you come for this function, ok? π
types() ποΈ
@types = Net::RDAP::Values->types;
types() gives you a list of all the possible RDAP value types. It's the full roster. The complete cast list. Every single one. β¨
description() π¬
$description = Net::RDAP::Values->description($value, $type);
$description = Net::RDAP::Values->description('registration', RDAP_TYPE_EVENT_ACTION);
use Net::RDAP::EPPStatusMap;
$description = Net::RDAP::Values->description(epp2rdap('serverHold'), RDAP_TYPE_STATUS);
description() returns a textual description β in English β of the value that's sitting in the registry. And it's actually suitable for displaying to a user, which is so nice of it. No cryptic codes, no gibberish, just words a human can read. iconic π
π EXPORTED CONSTANTS π
Net::RDAP::Values exports the following constants, and every single one of them corresponds to a permitted type of RDAP value. Collect them all, bestie π:
RDAP_TYPE_NOTICE_OR_REMARK_TYPERDAP_TYPE_STATUSRDAP_TYPE_ROLERDAP_TYPE_EVENT_ACTIONRDAP_TYPE_DOMAIN_VARIANT_RELATIONRDAP_REDACTED_NAME
π COPYRIGHT π
Copyright 2018-2023 CentralNic Ltd, 2024-2026 Gavin Brown. For licensing information, please see the LICENSE file in the Net::RDAP distribution. π«Ά
and that's the whole page, bestie!! πΈ this was Net::RDAP::Values(3) from the User Contributed Perl Documentation, brought to you by perl v5.42.2 on 2026-06-17. go forth and validate your values responsibly π β¨π¦π
π¦ where this page comes from
- fedora 44: perl-Net-RDAP 0.43-1.fc44 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms