Liane, These are what I have so far and will let you know if I think of new. - Steve
2.1 DTD extension <prop_pattern> Dose the 'constrains' tag apply to all the values in a property or just individual value? Is it possible to have constrains in the individual <value> </value> block? 2.6.2 What does nt in tm_pg_pattern_nt_<name> mean given that there are _n_ and _t_ already? Are those tm_* repository representation for the new ext template elements or they are internal representation only and not visible to users? I am not very clear about the usage of value_<BASE32 name>_*. Can you elaborate further and give examples? A prop has integer value, what we store for its constraint_name? Integer or ascii representation of integer? Are there interfaces in place to allow user to template/decorate the existing svc/instance? Say I have svc with the current basic template and I like to extend its definitions. smf_template(5) Can the name in prop_pattern take wildcard? Can I apply visibility tag to all the props by using wildcard? Is there any constraint on what characters may be used for internal_separator? Can the extended templates be customized once svc/inst is up and running? Do I need to deliver a new manifest with new ext templates?
