Page History

h1. Contents

This page aims to clarify how to use this wiki. It contains

{toc}




h1. Structure of the wiki


h2. Units

The wiki describes several distinct units in the organization of standards in The Netherlands. Namely,
* Standards
* Application profiles
* Working groups
* Decisions

The *{_}standards{_}* are usually international agreements. The pages concerning the standards provide a short description of the standard and a URL  to the standards own page. These pages will also provide a link to the application profile describing the standard's use.


The core unit of the wiki are the *{_}application profiles{_}*, which describe how a standard is used in The Netherlands within the appropiate context. Each application profile describes a solution to a specific problem. When looking up such an application profile, two levels of detail are present; _Overview_, which describes what the problem is and how this is solved, basically to give an idea of the application profile, and _Expert_, which gives technical details about the application profile and how it works. In each an _abstract_ is present that describes in short what the application profile is about. In essence, the _Expert_ detail level is the official application profile, _Overview_ is a description of this. The wiki pages of the application profile all have the status Draft. For the official agreed upon version, see the PDF file.


The pages concerning the *{_}working groups{_}* describe the working groups that are responsible for maintaining the application profiles. In these pages a description is given of what problem the specific working group tries to solve and what their scope and role is. With these pages, one can also find out who works on specific application profiles and how to contact them.

The last unit are the *{_}decisions{_}*, which describe the decisions made by working groups and the WISH in the last years concerning the use of standards.

h2. Structure

The application profiles are structured in several ways. First, an alphabetical list of all the application profiles is present on \[Application profiles\]. On the \[Categories\] page, all the application profiles are categorized according to their topic. {proposal} On the SURFfields page, the application profiles are ordered with their relevance to the distinct fields SURF is active in and in which these application profiles are used.{proposal}

h1. Who can use the wiki

There are 5 roles associated with this wiki with different possibilities of interaction with the content;
* Visitor
* Moderator
* Working group
* Authority group
* Administrator

The *{_}visitor{_}* is the default role for anyone visiting the wiki. The visitor can review the content on the website and can place _comments_ with questions or proposals.

The *{_}moderator{_}* is a person assigned to be responsible for specific application profile pages. Thus, the role of _moderator_ is relevant to specific pages of application profiles (not the entire wiki). The _moderator_ responds to the comments from the _visitors_, makes the appropriate changes to the application profile pages and communicates this with the responsible authorities. The _moderator_ may propose changes to the _working group_, they have the status of _proposal_.

The *{_}working group{_}* is a group responsible for maintaining the application profiles. They are responsible for the application profiles in the context of its use within the Netherlands. For most application profiles, a working group is created for its maintenance, see the page [working groups] They communicate their decisions with the _moderator_ (see [workflow|#workflow-maintenance] below), these decisions serve as _advices_ for the _authority group_. The _working group_ thus doesn't edit the pages, but communicates that to the _moderator_.

The *{_}authority group{_}* is the group with the authority to make decisions about the application profiles within the Netherlands. They decide whether to follow the advices of the _working group_ or not. The decision of this authority group is incorporated into the application profile, which has the status of standard within the Netherlands. The _authority group_ thus doesn't edit the pages, but communicaties that to the _moderator_.


Last, there is the *{_}administrator{_}* of the wiki. [?SURFfoundation|http://www.surffoundation.nl/] hosts the wiki and maintains it technically. The _administrator_ keeps the wiki clean from spammers and helps with technical problems. The _administrator_ is not responsible for the subject-matter of the wiki, but maintains whether the pages are created according to the guidelines, so that the wiki remains clean and clear. For more info see the ?[standards:Wiki working group] page.




h1. How to use the wiki

Besides reading the wiki and learning about the topics one is interested in, the main advantage a wiki has is the functionality of collaboration. The collaboration this wiki provides is described in three actions:
* Commenting
* Editing
* Exporting to PDF

h2. Commenting

Each page features the possibility to post comments. Especially in the case of the application profiles it might be of interest to ask questions or propose changes to the application profile. There are two distincts ways of placing comments.

When placing comments in the comment section, _everyone_ is allowed to post comments, these comments may then be replied to be the _moderator_ assigned to the specific application profile. The comments are placed at the bottom of the page.

When placing comments inline in the document, only those who are allowed to edit the concerning page can place such comments. This can be especially useful when discussing on-line as a working group, in the situation of developing a new application profile. For such comments, use the following guidelines, in which we follow guidelines from the [?Confluence notation guide|http://wiki.surffoundation.nl/renderer/notationhelp.action?section=advanced]:

First and foremost, for means of keeping communication followable and transparent, close every comment with *\--name author, date* so that everyone knows who made the comment and when.


* In the case of a general informative comment (not for discussion), use the {info\} tags. In the case of a general informative comment, the \--author, date rule may not always be necessary, specifically when the comment isn't part of a discussion but part of the application profile.

{info\} A general informative comment -- Author, date {info\} leads to:

{info} A general informative comment \-\- Author, date {info}

* In the case of a warning when something is wrong or has high priority, use the {warning\} tags.

{warning\} A warning about something wrong or with high priority \-\- Author, date {warning\} leads to:

{warning} A warning about something wrong or with high priority \-\-  Author, date {warning}

* In the case of general comments for means of discussion, use the {note\} tags.

{note\} A comment for means of discussion \-\- Author, date {note\} leads to:

{note} A comment for means of discussion \-\- Author, date {note}

h2. Editing

The application profiles may need changes, the _moderator_ can make changes to the page. There are two stages of changing a profile: when editing a profile, one should annotate these changes to identify their proper status. When a change of an application profile is _proposed_ by a moderator, this moderator should add the {proposal\} tags around this change. When this proposal is agreed upon by the relevant working group, the status should be updated to _advice_ and the tags should be {advice\}. This results in the following identifications of status:

{proposal\} {proposal} Insert proposed change here{proposal} {proposal\}

{advice\} {advice} Insert adviced change here{advice} {advice\}

Only the _moderator_ is allowed to make these changes.


h2. Exporting to PDF

The advice from a working group is then discussed in the WISH, which decides whether the change should be made officially part of the application profile. When this is the case the annotations may be removed and an export is made of the wikipage to PDF. The PDF file is then uploaded and becomes the latest official agreed upon version. The changes are described in the _Document history_ on the wikipage.


h2. Workflow

The above results in the following workflow on maintenance of the application profile pages: !workflowUML.png|align=center!

The workflow for how an application profile is instantiated can be found on [Application Profiles workflow]