Sarah,
Thanks for the updated spec. This review only covers section 6, but
there were a few items that I thought worth raising, apologies if they
duplicate others, I didn't compare with other comments. I'll look at
the rest tomorrow.
page 20: Should the image element also include support for image type
(full, user, zone) and properties ("pkg property")?
page 21: I'm still troubled about primary_source and secondary_source in
the software spec. It doesn't seem that the schema allows for multiple
secondary sources, does it? Would it make sense to merely have a list
of source elements and either make primary an attribute or imply it
based on order of appearance? One thing I brought up previously that
doesn't seem resolved is handling repositories that require key & cert
for authentication.
page 26: I think the schema could use comments in each case where the
"options" element appears on the expected format of the options for that
usage.
page 28: I hadn't reviewed the config section before this version, but
I'm wondering whether zones really should be a distinct element, as it
appears to be fairly distinct from the other ones (and likely to grow
more complexity that might not translate well). Thoughts? A second
issue here is what the use case is for a "network" configuration type,
as well as "user"? None of the examples show one.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
