Ginnie, Thanks for the feedback. Comments are inline.
On 02/26/10 02:15 PM, Virginia Wray wrote: > Hi Jean - > > Here is some feedback on the doc: > > Section 2. Assumptions and Dependencies > > What about including dependencies on other technologies, like IPS? I'm really not sure where we stop at this type of thing? Then do I list cpio? pkgadd etc? > > > 3.3 Interface Tables > > Under IPSTransfer, set_type is listed twice. Fixed. > > > 3.4.1.3.8 9 - 11 > Is the _args attribute cpio_args? Yes. > > > 3.4.2 IPS Functionality > There is no explanation of the functionality like you have for the > Media functionality. That would make things more explicit. Note taken. I'll make this an outstanding issue to be resolved after it is decided what to even do with this functionality. > > 3.4.2.3.2 > typo - performthe/perform the Fixed. > > > > 3.4.3. SVR4 Functionality > There is no explanation of the functionality like you have for the > Media functionality. That would make things more explicit. Added. > > > 4 Use Case/Diagrams > The first use case implies that the transfer module is engaged, but > it's not clearly called out. > Done. > Second use case: > typo: the esystem / the system > Fixed. > General question: > There is duplicate methods in all of the Classes. Is there a way to > combine that commonality into > a class that the other classes could then be sub-classes of? Yes. You weren't the only one to comment on this. I'll work on having the doc reflect this. Jean
