Is there any documentation that defines the allowed characters for a property name?
If I'm reading the code correctly, the name will only allow alpha, digit, '-' or '_'. Is this accurate? If so, then it is a fairly harsh restriction for my implementation. I'm attempting to use an ANSI approved world wide unique identifier as the property name which can contain, among other characters, ':' and '.'. In my current case, I seem to be getting an invalid argument scf_transaction_property_new error based on a '.' in the property name. For background, I'm using the identifier as the name since the identifier value contains the only necessary information that needs to accompany this property, i.e. it needs no property value. I would prefer not to create an unnecessary abstraction of a name just to be able to populate the property value with the identifier. To explain further, the "properties" in this case is a list of one or more group member entries that only differ in their identifiers. So creating the abstraction would also entail crafting a solution to create another namespace for these group member entries that would need to be based on some character string with an embedded sequence number. From the administrator's point of view, I think this will be confusing based on industry perception of these identifiers. Before I craft a solution that entails creating a name for each entry, is there anything that I might be missing in my above valid property name assumptions? And, with the background explanation I've given, might there be a different approach to accommodating a group and member list model as described above? This message posted from opensolaris.org
