Inspectable metadata tag is intended to provide information to the compiler that describes how your components are used in an application.
These compile-time directives are never interpreted during run time.
Described by the class definition, these properties are not dynamic.
<type name="X" base="Class" isDynamic="true" isFinal="true" isStatic="true">
<extendsClass type="Class"/>
<extendsClass type="Object"/>
<accessor name="prototype" access="readonly" type="*" declaredBy="Class"/>
<factory type="X">
<extendsClass type="flash.events::EventDispatcher"/>
<extendsClass type="Object"/>
<implementsInterface type="flash.events::IEventDispatcher"/>
<variable name="listOptions" type="Array">
<metadata name="Inspectable">
<arg key="name" value="My List"/>
<arg key="type" value="List"/>
<arg key="defaultValue" value="One"/>
<arg key="enumeration" value="One,Two,Three"/>
</metadata>
</variable>
In addition, application domain and network calls at author time on Flash Pro's artboard can be problematic; although, I've developed a Google Maps component capable of making calls to load maps while authoring.
Although academic, this seems like an inappropriate use of this tag. This implementation is typically for static options of your component.
This could only be accomplished via an automated process that auto-generates the class definitions.
As in, you could call a service that writes the ActionScript class files populated with the enumerable values. Then, have automated builds that push new compiled components for update.
Beyond compiled assembly, there is no way to dynamically update these definitions realtime.