Overall looks good. Most comments are questions. :-) Section 2.1 indicates that pg_pattern's target may have value of 'this', 'delegate', 'all'...etc and in section 5.1.1, the pg's type also can have value of 'all', 'delegate'. I am not clear on what values are acceptable for pg's target and type.
Can I have instance's specific pg_pattern in the service's template? For example, if I have multiple instances in the service manifest and I like to have instance specific info in the template. Is it correct assumption that the pg name and prop name needs to exist in the defining service/instance manifest? Section 2.6.1. Can I have compound unit such as meter per second? Section 2.8. Can visibility override the existing value or it is just used to describe the current property? Section 2.9. Is there a default for internal_separator? Section 2.10. If I have value="blue" and valueset="red purple". What the acceptable values would be? "blue"? "red purple" or "blue red purple"? Is there any chance that these fields may mutual exclusive? Section 3.1.1. Can you elaborate "Site customizations will behave as if they were defined in the service's main manifest."? Section 3.1.2. Can this more-specific target definitions affect all the instances /services in a more broadly scoped service/golbal? Section 4.3. Should it be "clarify it is of type delegate" instead of restarter? Section 4.4. "wil" should be "will". Section 5.1. Will the scf look the same (1) when we fail in interactive mode, (2) when we don't fail in non-interactive mode? Section 5.2. Should that be "If no manifest file and no FMRI"? Should the current selection be validated if the specified argument is invalid? Section 6.1. Should we specify the responsibility of freeing allocated memory? Section 10.2.1. Can we elaborate "properties are active on"? It will be nice if we can provide an example of "change at next start". Steve
