Comments inline.
> > For the benefit of the list, Paul's additions are: > > -Ability to provide comments on pages (must have). > -Ability to export multiple pages to PDF (nice to have) > -Wiki integrated into the OpenSolaris site structure (must have); I > would like to see the Project and Community sites be their own wikis. > -Ability to set up roles and permissions (must have) > > > I've added 'Ability to provide comments on pages' as a conditional > requirement (C19) because not all wiki technologies make the distinction > between commenting and editing (one might not have edit privileges, but > might still be able to comment). So, yes, the ability to make comments > should be an explicit requirement. > > The ability to export pages as PDF is already noted as an optional > requirement (now O21). Most wikis have the ability to create a PDF from a single page. I wanted to add the requirement to create a PDF from multiple wiki pages...a way to create your own PDF "book". This feature is being provided by some wikis, and it's an important feature for the future. > > Integration into the OpenSolaris site structure is, I think, implicit. > The corollary of Project and Community sites being their own wikis I > think is addressed by the conditional requirement for name space > support, if I understand Paul's point correctly. o.k., fair enough. I guess I wanted to make it explicit. ;) > > Roles and permissions are 'must have' requirements, but are addressed by > the E2 essential requirement for pluggable authentication. > http://auth.opensolaris.org references the authentication architecture, > but the E2 requirement does not explain the interaction between the auth > app and the wiki software, that is, that the auth application will have > role information which must be mapped to the wiki software's notion of > roles and hence permissions. I'll remedy that. o.k., thanks. > > > Thanks Paul, and please correct me if I have misinterpreted your > requirements. Thanks much Chris! > > Chris > > > _______________________________________________ website-discuss mailing list [email protected]
