[OpenISO] Software and Documentation for procedures?

[Std Lib0]

On 9/7/07, Norbert Bollow <nb at bollow.ch> wrote:
>
>
> Update:  "Developing a software system of our own" of course does
> not imply starting from scratch and developing yet another CRM
> system.  Rather we should build upon an existing CRM system by
> adding custom modules or whatever to implement the workflow that
> we want.


That's why I thought about peertopatent.org, their software seems to do a
decent job when discussing drafts (I'm using it) and extra features suitable
to openiso could be added accordingly.  But probably a wiki would do pretty
well initially, while the procedures are explored. What about an
openiso.wikidot.com for now (http://www.wikidot.com/features)? Lots of
features, private backups, for free. Noooxml uses it. Great for integration
of communities.

When you say CRM, aren't you probably meaning CMS?

I also would like to suggest having a look at the new commenting system of
the free software foundation
(http://gplv3.fsf.org/wiki/index.php/Comment_system
) called stet. It was used first to handle the comments for the GPLv3. See
for instance it working for the Gnu Affero draft:
http://gplv3.fsf.org/comment/agplv3-draft-2.html
. It looks very intuitive for mass revision, highlighting in a saturation
scale the sections in which there are more disagreement.


The "online editing" would be similar to how you edit a page in a
> wiki, but with the additional constraint that the text should be not
> only suitable for converting to HTML but also suitable for displaying
> in plain text format suitable for quoting in text emails.


This reminds me of a wiki markup called markdown:
http://en.wikipedia.org/wiki/Markdown

"The overriding design goal for Markdown's formatting syntax is to make it
as readable as possible. The idea is that a Markdown-formatted document
should be publishable as-is, as plain text, without looking like it's been
marked up with tags or formatting instructions. While Markdown's syntax has
been influenced by several existing text-to-HTML filters, the single biggest
source of inspiration for Markdown's syntax is the format of plain text
email."

The ability for edit-locks to be restricted to sections of a document
> rather than applying to a document in its entirety would be a big plus.


This is usually not implemented in wikis, though probably there is a cms or
wiki with this feature, or each section has a different page.

In addition, the "online editing" system should understand a document
> numbering/labeling system as proposed here
> http://openiso.org/pipermail/discuss/2007-September/000014.html


good.


> When the official, numbered draft versions are viewed on the
> OpenISO.org website, a list of existing modified draft versions
> should also be displayed, with a summary (provided by whoever
> created the document editing branch) of the changes.


yes, nothing should ever be discarded, just like in wikipedia you have the
complete history of every article.


as for the underlying storage backend, it would be very interesting to use
the idea of git (the revision control of linux, http://git.or.cz/gitwiki/Git):
each revision has a unique cryptographic hash, so that from the knowledge of
this short hash alone, it is possible to obtain the original authentic
document even if the document is stored in an untrusted storage: any undue
modification in any letter of the document would result in a different hash,
so each hash can be seen as a pointer to the authentic document.  this is
very nice feature to have on distributed documents.

[]s,
stdlib0


ps: Any software, however, will have to deal with the entities of the
standardization process. What are the fundamental entities? The following
items seem to be first-class citizens (I really need to read that book):

- process categories
- proceedings (timetable, events etc)
- acceptance rules (voting rules etc)

- application (type, label etc)
- submitter (name, company etc)
- status (under scrutiny, endorsed, etc)

- document, sections
- versions
- dependencies on previous standards

- reviewer (anonymous or name etc)
- groups of reviewers with similar interests
- access control (login, read, write, etc)
- expert reviewer? (name, institution)

- comments+updates on sections

- vote on comments
- reputation system for reviewers, meta-comments (comments on comments)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://OpenISO.org/pipermail/discuss/attachments/20070908/e3821e41/attachment.htm