This is not a public version. Please do not quote or distribute without author's permission .
Changes in this version:
Rewritten:
The knowledge base to knowkedge place WHAT IS AN ONLINE INTERACTION ENVIRONMENT (OIE)
The section on EDITOR
DESIGNER
Deleted:
Section on OWNER
propose to write a separate bit on that.
Trimmed the COPYRIGHT to its essentials
Added:
ADMINISTRATOR quote from ns
BIBLOGRAPHY one item
Our email addresses in the title.
WHAT IS A ROLE?Key Roles
CYBERSPACE
ROLES IN CYBERSPACE
WHAT IS AN ONLINE INTERACTION ENVIRONMENT (OIE)
PROJECT OWNER
PROJECT MANAGER
DESIGNER
HOST
LIST OWNER
CYBRARIAN
MODERATORADMINISTRATORSpecicialist Roles
MEMBER
ACTIVE PARTICIPANT
POSTER
READER
LURKEREDITOR
AUTHOR
FACILITATOR
COLLABORATION FACILITATOR
INTERACTION FACILITATOR
THERAPEUTIC GUIDE
PRESENTER
TEACHER
LEARNER
MENTORCONCLUSION
REFERENCES
FOOTNOTES
BIBLOGRAPHY
INDEX
CONTRIBUTE TO THIS DOCUMENT
COPYRIGHT
In this paper we identify and describe roles that occur in various online interaction environments (OIEs). Our purpose is to create a resource that will be of use to participants and practitioners in OIEs in talking about and improving their work. We envisage that the relationships between people can be improved and that the work can be more productive if we can see clearly how roles and tasks interact. Complex dilemmas can be resolved quickly and ethically if we understand where responsibilities lie.We believe online interaction works best when *people* do things well, when they have the roles! We advocate the simplest, lowest common denominator technology for most communication. Better mailing lists and email clients are needed and will come, but people can also "upgrade" their *abilities*, there is much to explore and learn about the *human capabilities*. It will be exciting to see major leaps in technology produce new interaction environments, just as interesting is to see the people dimension evolve. Whatever the software, people need adequate roles. The grasp of the roles is developing as fast as the hardware and software, and is crucial in the equation of progress. Getting the *roles* clear will assist those who design software, and that is our hope.
We particularly have the Host of an interaction environment in mind as we write. Host has become the generic term for a person who performs many roles in an OIE. Central to the role is direct contact with the members of the OIE and commitment to the success of the project. Hosting can be seen as an emerging profession in its own right. As Host, one person may enact many roles. They are distinct roles, however, and may be shared among the members of a hosting team.
The terminology used for roles varies among software packages and has evolved differently in different contexts. Drawing from the literature and from case studies, we will identify some generic roles. For each role, we will list the tasks, skills and personality traits that are associated with the role and mention how they relate to other roles. Then we will show how the names and descriptions of roles vary in a range of settings.
We hope that practitioners and students of online group communication will find this document of practical use, and that there will be lively discussion. We are happy to make changes if we see their merit and will acknowledge contributions in future versions of this document.
We acknowledge the influence of J. L. Moreno who developed his terminology in the highly interactive environment of Psychodrama. His definition is that "Role is the functioning form the individual takes in the specific moment he reacts to a specific situation in which other persons or objects are involved." (Moreno, 1977, p. IV) This means that at any time, whatever we are doing, can be described in role terms. Roles defined in this way are not a mask, they are ways of being ourselves.
Roles include thoughts, feeling and action. Think of this broadly as involving our whole way of being, our "weltanschauung", our commitment to particular values. In this paper we will mention the central aspects of the roles that are at their mainspring... for example a Manager is enlivened by his or her desire for orderly execution of the prime directives of the enterprise.
Moreno described three types of roles. We are mostly concerned here with the "social roles" such as Manager, Author, Teacher and so on. To understand the social roles in depth, it will help to understand the two other types in his schema, the "somatic roles" (soma=body) which come to us from the structure and make up of our bodies, such as Walker, Eater, Sleeper, and the "psychodramatic roles" which highlight the psychological aspects of our functioning, for example: Intrepid Explorer, Cunning Fox, Mother Theresa.
We will examine how people constructively involve themselves in cyberspace. First, however let us clarify what we mean by "cyberspace".
We could think of the networked computer as a tool which helps us to communicate, however the tool has so radically altered our experience that we have new words to describe it. Cyberspace, a term coined in the 1980s, describes a distinct new environment. To look at the roles we enact in online communication it is helpful to explore the nature of this environment and how we are present in it.
In cyberspace, everything, including the body, is represented in another form. In cyberspace we interact with representations and abstractions that people have created. Face-to-face experience is lost in the case of text based communication and altered in the case of video, or graphical avatars. If the digital representation is recorded, we can experience it any time, this asynchronous communication leads to our experience of online time as a distinct flow separate from chronological time.
Face to face (breath-on-air as bandwith) has its own structural constraints, those of our bodies have a form matched to the space time environment; we are subject to gravity, we require light to see, we can hear certain frequencies. We propose an abstracted view of the body as a structure which both permits and constrains the functioning of an individual in a particular environment which has specific persistent characteristics.
Online communication is mediated via hardware and software. However we go beyond thinking of access to files, we go "into" a place and software has environmental qualities "platforms", "workspaces", "levels", "groups" and "communities". Obviously we do not enter into cyberspace *physically*, to "go" there, we associate ourselves with certain units of software, we have a software representation; an email address, which can then be given attributes, such as a user name, and passwords that will enable it to go into certain "places" and perform certain actions.
Avatars are entities sent to earth by gods to act in the physical realm. In cyberspace we are represented by our avatar. At its most fundamental level, our avatar is the email address which represents us. The email address can then accumulate attributes, such as access to files. We associate with this cybersoma and experience being alive in a world alongside the physical world; cyberspace.
Moreno described three aspects of a role; thoughts, feelings and action. We have added a fourth aspect; the cybersomatic.
Some roles are hard-wired into the software. An example is list owner, which then has a strong cybersomatic aspect. The software of most mailing lists *demands* that there be a person in such a role. Even if we do not use this name overtly, but use the word Administrator and Host, list owner is present as a purely cybersomatic aspect of the role.
Moderator is a social role, we know what a moderator is in ordinary (North American) usage, in the online world it has a cybersomatic aspect in that one designated as the Moderator receives all communication before it is approved for distribution. Some online communities have various levels of membership with each level adding cybersomatic powers. There are experiments to hard wire democracy into online groups. <Footnote 1> This aspect of the computer environment is used extensively in MUDs, MOOS and adventure games where new powers are added as each level is completed. It is important to understand the cybersomatic role structure in a particular environment.
It avoids confusion if a person is not called a Moderator or Wizard unless they have the cybersomatic preconditions, i.e. if the software is set to give them those abilities. It is important for software designers to name roles, when they embed them in the software, in a way that meshes well with the social role. For example an administrator is different from a manager.
WHAT IS AN ONLINE INTERACTION ENVIRONMENT
(OIE)
An Online Interaction Environment, OIE, supports the social interaction among group members. At the same time it accumulats a record of the shared knowledge of the group.
We use the somewhat cumbersome term, OIE, because it is generic enough to embrace many forms of discourse such as Virtual Communities and Collaborative Virtual Environments using different platforms such as mailing lists, and groupware technologies such as Lotus Notes and MS Exchange.
We describe the characteristics of several OIEs and distinguish them from other environments. We have categorised the environments by their *purpose*. We are thinking of the purpose from the perspective of the participants or end users of the OIEs. Owners may have additional aims in mind, such as increasing a company's profile or making sales, the owners purpose is not the primary consideration, as similar environments could be run by owners who have different motivation.
The roles people take on in each type of environment will vary and so it is important that we distinguish a variety of OIEs here. It is also useful as Hosts in one environment may not realise how much they have in common with people in another environment. For example in Learning Environments it is easy to forget that the role of Teacher is not totally different from the Host in a Virtual Community.
Collaborative Virtual Environment (CVE)
collaboration on a specific task, usually the
production of a document
Virtual Community (VC)
discussion
Virtual Work Space
integrated with other media -
especially face to face & phone learning,
knowledge base development, support, group building
Community of Practice
share ideas, challenges, develop shared
thinking, develop knowledge base, support,
develop relationships, innovation, monitoring
quality and ethics
Knowledge Place
An online environment for sharing specific and
quite structured knowledge. Examples include
organisational standards and procedures or
how to use a software system. As well as building
a knowledge repository, the purpose often includes
working together to revise and develop new knowledge.
Online Learning Environment (OLE)
teaching, learning, integrated with other media or
not, content or skills or conceptual focus
Ownership is in disarray. There was a time when slaves were owned. In some cultures people can own land. We can now own not only machines and wires but the bits that flow through them. It has been said that property is theft, and also that information is free, yet the term Owner has a long history in cyberspace, List owner, owner of software, author etc. One use we advocate is Project Owner, in the literal sense of the word as the one who pays for it all. No where is it really free to create an online interaction environment, even using free software on the net such as eGroups or Communityware, there is effort used in creating the environment as a whole. Someone has to name it, write the welcome file and charters etc and promote it. Thus in a specific project it could be that the owner is the person who designs the environment, has the pass word needed that could delete the whole endeavour. However the Project Owner may well pay someone to do all those tasks. For example: A company decides to create a Mailing List for its sales staff - A Community of Practice in our typology. The existence of the list ultimately depends on the person who pays and allocates work to the sales people. It is well to remember who the real owner is, as that person or group must have their goals and aims for the interaction met for the process to continue. An example of the power of the Project's Owner was evident when the discussion forums in Netcenter were simply discontinued by the owner <Footnote 2>. They do not have all the power however, as the communities shifted to sites using Communityware.Owning the project involves its own ethical considerations. The owners of Geocities tried to claim rights to the content put there by users. <Footnote 3> Far from owning the content the project owner has the ethically needs to consider and respects the participants ownership of the content.
Skills: Entrepreneur Tasks: Staff employment and liaison, pay staff, allocate resources, evaluate viability Ethical Considerations: Honour participants contributions.
Community Manager is sometimes used for what we have in mind here. The word community may be used for sites that consist of several asynchronous forums, web pages, chat rooms etc., however in many contexts "community", while necessary may not be the prime focus, for example in a Support Centre. The person who makes sure it is a goer, we are calling the Project Manager.The Project's Owner, while having the ultimate say over the endeavour, may have little to do with its creation or day to day functioning.
Figallo HWC Page xi
"The relationship between the user and the site as a whole must be monitored by one key person -- the Community Manager -- who takes on the responsibility of keeping that relationship a good one."
Monitoring is a key word here, we add: organizing, supervising, managing, responsibility, liaison, training, encouragement, evaluation, good will. We could add also that in time limited projects, termination is also an area that needs attention.
Once a project is going well, and the members are participating, the host is hosting and the system is running well, there may be little for the Project Manager to do, however to maintain that positive process requires active attention and involvement. The others in the project, both at its inception and those involved in an ongoing basis will work best when they feel well supported, trained and trusted.
Note that the Project Manager often reports directly to the Project owner (perhaps the CEO or Director). While they may, sometimes be done by the same person, the environment *design* involves another role. The Project Manager may have some influence on the design, the role here is to *implement* a plan and a design.
Software designers at Cooper http://www.cooper.com/philosophy.html made this comment on design:
When we say design, we don't mean dolling up some dog of a product with cuter-than-a-bug icons. "Putting lipstick on a pig," as one of our favorite clients put it. Goal-Directed design goes much deeper than just making things look cool and is applicable to virtually any category of interactive product.The design of an interactive environment has many layers. The choice of operating system and the choice of medium, such as Internet or Intranet, or Usenet, or the World Wide Web involve design decisions, even if they are thought of as programming. In this paper, we are primarily thinking about the person who uses *existing* software, and is not involved in designing the software itself. The designer of an OIE is like the architect. The person, employed by the Project Owner, to come up with the plans that suit all concerned.
Cyberspace is created by representation. Hence things *are* what we call them. A Lounge is a particular type of interaction environment, and if we call a mailing list Staff Lounge, then that will largely determine the interaction that occurs there. Choosing the right name for the spaces is part of the Designer's job.
There is more to it than naming. If we have a place called Staff Lounge, then it must be open to people designated as Staff, and closed to non staff. Building that into the plans is part of the Designer's job.
All this sounds simple enough, remember that such a place has to work well for the Project Owner and the people who use it, as well as the Host of the Lounge. Liaison with these people is integral to design.
The Designer is a person who creates a structure, that meets the criteria of the owner and is possible given existing affordable materials and useable by those who are to use it.
My introduction to Hosts was in Compuserve Forums circa 1991.
There they
were not called Hosts, but ??. They had special
signs around
their sig, id, thus: ::Jim::
The next awareness of the online role was Sysop of a BBS. Then
List
Owner. Not until I read Howard Rheingold's "The Virtual
Community"
did the term Host clearly come to consciousness. That
was at some point
reinforced by John Coat's now classic text:
Cyberspace Innkeeping: Building
Online Community.
http://www.sfgate.com/~tex/inkeeping
A shorter and precise summary of the role is Howard Rheingold's:
The Art of Hosting Good Conversation Online.
http://www.rheingold.com/texts/artonlinehost.html
Figallo HWC Page xi
"I expand the definition of the host to encompass the entire
staff of
a Web site. Hosting is not just one person's job, it is
the mission of the
entire company that provides the Web site. It
includes the means that the
site uses to pay for its existence...
Hosting involves every element of the
Web site's operation, from
design to customer service to marketing."
We are thinking of Host like that, if there is only one person
who is
doing it all, lets call him or her the Host, if there are
specialisms in the
group, then at the centre of the discussions
and liaisons it is good to have
the Host of the forums.
These ideas about the Host and Hosting are very useful and come
from years
of online experience and how it can work well.
In this document we reccommend the three above as having defined
the role,
not only for communities, but for that aspect of all
online groups, even if
community is far from their minds.
While we advocate the more generic use, there is also the
very
specific focussed role. Notice that the role has lost its
close
links with the cybersomatic, it is quire distinct from List
Owner
and Sysop. We prefer Administrator for those roles. The
Host
must of course liaise closely and know what is possible...
for
example can a person be put on review, is the system secure, etc.
It is also distinct from the Project Manager, who has a
broader
perspective, and to whom the host is ultimately answerable.
The
Project manage thus has to know a thing or two about hosting to
do
that job.
Separate too from the specialists such as *facilitator*, teacher,
speaker,
therapist etc.
~~~
the central focus for the Host role is the wellness
of
the group as a whole...
Much like a doctor has an ethical duty to protect life
so the
Host is ethically bound to perform that task... and yes it
does
mean some severe surgery at times... never on a whim!
Though
that accusation may all too readily be there, and being ready
for
that, and preempting it will come naturally (after much training
:) to
a Host.
~~~
LIST
OWNER
<<< stuff to edit from:
http://www.lsoft.com/manuals/1.8d/owner/owner.html#6.2
6.2. The role of the list owner as moderator
By default, the list owner becomes a moderator of sorts, even if the list in question is neither edited nor officially moderated. This means that, as a list owner, you must be prepared to maintain order if it becomes necessary. At the same time, you must moderate yourself so that you do not alienate users and cause your list and/or host institution to suffer as a result. Thankfully, mailing lists have generally enjoyed relative peace and quiet over the years in comparison to newsgroups, but mailing lists have unique problems of their own.
Lists dedicated to controversial subjects are more likely to become arenas for "flame wars" between subscribers with hard-held and differing opinions than those dedicated to the discussion of popular software packages, but this does not mean that the latter are immune any more than it means that the former are constantly plagued by flames. The example set by you as list owner and as a participating subscriber to the list is perhaps the most important factor in whether or not your list becomes a site known for strife and controversy. In other words, if you appear not to care about whether or not discussion is on topic and/or civilized, no one else will, either. Yet if you become a policeman -- the other end of the spectrum -- no one will want to subscribe or participate for fear of your wrath. Either way, your list is unlikely to last very long.
The middle ground is, as in most things, the place to be when administering a list. Some call this "firm but fair," letting things go pretty much as they will but stepping in with a wry or gently chiding remark from time to time when exchanges get heated. And they will! Software discussion lists are particularly bad about this when new subscribers ask "frequently-asked questions" (FAQs) and veteran subscribers respond in exasperated fashion with "RTFM!" (Read The Fine Manual) and similar nasty retorts. Good list owner practice at this point is likely to be a good-natured reminder from you that flames belong in private mail, pointing out that new subscribers have no way of knowing that the particular questions they ask have been asked (and answered!) n random times before, and possibly adding a link to the list's archives (if they are available on the web) or instruction on how to use the SEARCH command to look for answers before asking.
Finally, if your mailing list has an international audience, you must be careful to account for language problems and cultural differences. You will need to decide which languages are allowed or not allowed on the list; this should be mentioned shortly in the list abstract or welcome message. Unless the list is specific to one country or is explicitly for discussion in a specific language, the official language will probably be English. As your list grows, some subscribers may object to this decision, arguing that people who have trouble expressing themselves in English should be allowed to use their own language, with the understanding that many people will be unable to understand what they are saying. As the list owner, it will be your call. Usually, the best compromise is to start a separate list for discussions in the new language. However, you must be careful in wording your decision. In multi-lingual cultures, it is usually considered a courtesy to use the other person's language. It is certainly considered rude for people to demand that everyone else should speak their language. Thus, if your native language is English, you will be in a delicate position. To avoid a flame war, you will want to make sure that your decision does not come out as a unilateral demand. Politely suggesting a separate list, and tolerating an occasional non-English posting when the poster genuinely cannot speak English, is often the best course of action.
Another possible source of flame wars is unintended rudeness. It is easy to forget that non native speakers are making an effort every time they post something to the list. People will make mistakes, sometimes appearing rude when they did not mean to, simply because they used the wrong word. Another cause of apparent rudeness is cultural difference. Things which are perfectly normal in one culture can be insulting in another. For instance, ad hominem attacks are perfectly acceptable in some countries. Conversely, referring to other people by their first name ("As Peter said in his last message, ...") can be downright insulting in some cultures, where anything short of the full title is at best condescending. But, of course, in other countries the use of the full title is considered sarcastic... There is no middle ground here, because there are too many conflicting cultures and too many languages. The only way to successful cross-cultural communication is through the tolerance of other people's cultural habits, in return for their tolerance of yours.
6.3. The role of the list owner as editor
Edited lists are generally used for the purpose of "full moderation" or for refereed electronic journals or the like, for which random postings from subscribers and/or non-subscribers may not be welcome for general distribution. This places the list owner and any editors in the position of being full-time monitors of what is and is not allowed to go through to the list.
A word of warning to potential list editors: Rules on the Internet are not set in stone. Some people will insist on their right to post without what they will term "censorship" by the list editor. Some will become upset to the point of threatening to report you to your local computing center administrators for abridging their freedom of speech, or (in the U.S.) even threatening to sue your institution and you personally for an abridgment of their First Amendment rights. It is therefore vitally important to you that you keep a "paper trail" of such complaints in the event that threats become reality and you are asked about them. This common practice in the business world should be common practice in list ownership as well.
Freedom of speech and copyright issues on the Internet have
not yet been tested in the courts as of this writing. These are both areas in
which list editors and list owners in general must tread carefully. Always
document any problems you may have in these areas. >>>
MODERATOR
<<< From
http://www.lsoft.com/manuals/1.8d/owner/owner.html
2.13.4. Moderated lists
A moderated list is similar to an edited list, but for LISTSERV's purposes it refers to a list that uses the Moderator= list header keyword to "load-share" posting approvals among several editors. It is set up similarly to an edited list, as follows:
* Send=
Editor,Confirm
* Editor=
someuser@somehost.com
* Moderator=
someuser@somehost.com,anotheruser@anotherhost.com
* Moderator= yetanotheruser@his.host.com
This list will "load-share" the approval process between the three moderators, who will each receive one-third of the postings for approval. Note that a primary editor should still be defined.
If it is desired to have one editor handle more than a single share of the approvals, you simply define the editor more than once in Moderator=. For instance,
We don't hear a lot about editors in online groups. Perhaps we should. We are not thinking of editorial control here, but editors akin to editors in the publishing industry, people who assist in the production of documents.
"Editor" may be associated with someone who has editorial control however this style of control is not usually termed "editor" in the realm of online groups. In online groups the person who "edits" posts is usually called the Moderator, this is the usage we advocate and this is covered in the section on moderator. There is a small aberration to note here, Listserve (tm) mailing lists use the word editor as the equivalent to moderator in some circumstances. See http://www.lsoft.com/manuals/1.8d/owner/owner.html 2.13.3. Edited lists.
We are advocating that in online groups the term Editor be used only when people are working collaboratively on a document. That person must gather the work together in a readable form. An Editor assists the author (s) in the production of the work. This may include gathering material together, pointing out inconsistencies, looking at the overall style of the language, posting the work to date, version control, keeping the project on schedule.
A "CVE Design" wil include a protocol for collaboration - this says things like how many Authors must approve contributions before the Editor can put it into the next version and the procedure for decisions about releasing a version to the public etc. Walter Logeman has an online group to develop a collaboration protocol and CVE design. See http://www.egroups.com/group/collab_project/info.html
AUTHOR
An author is not necessarily the main writer... look at this definition:
author \Au"thor\ ([add]"th[~e]r), n. [OE. authour, autour, OF. autor, F. auteur, fr. L. auctor, sometimes, but erroneously, written autor or author, fr. augere to increase, to produce. See Auction, n.] 1. The beginner, former, or first mover of anything; hence, the efficient cause of a thing; a creator; an originator. Source: Webster's Revised Unabridged Dictionary
"He reads another message simply because of the return address.
From: root@pallas.eruditorium.org
On a UNIX machine, "root" is the name of the
most godlike of all users, the one
who can read, erase, or edit any file, who
can run any program, who can sign up
new users and terminate existing
ones. So receiving a message from someone who
has the account name
"root" is like getting a letter from someone who has the
title
"President" or "General" on his letterhead. Randy's
been root on a few
different systems, some of which are worth tens of
millions of dollars and
professional courtesy demands that he at least reads
this message.
CRYPTONOMICON page 244
root is not god. The *administrator* is subject to the decisions of the Host.
CONCLUSION
FOOTNOTES
An Article in the NY Times: Improving Dialogue on the Internet By DENISE CARUSO
http://www.nytimes.com/library/tech/99/07/biztech/articles/05digi.html
Talks about:
"Civic Exchange: Strong Democracy in Cyberspace, a project based in part on the theories he [Benjamin Barber] developed in his book on participatory democracy, "Strong Democracy."
The article mentions the following:
"Unchangeable, though, is a rule imposed by the
software itself: The group must elect its own moderator. Barber says this single
feature alone may solve the dilemma of online anarchy vs. democracy -- if not
for the Internet writ large, at least for those seeking meaningful
dialogue."
ROLES IN CYBERSPACE
From Salon:
"But last Wednesday, with no warning, the forums were abruptly turned off, the hosts let go, and the community members left to wonder what, exactly, happened to their home. The demise of the community is a byproduct of the AOL takeover of Netscape, but that doesn't help the community members whose online hangout has been suddenly shuttered.
"There's a lot of annoyed users out there. This is not a responsible way for a corporation to run online communities," says Elizabeth Lewis, who until last week was one of the Netcenter community hosts. "Those of us who are in community building for the long haul are concerned about how Netscape did this. It's not so much that they shut the community down -- although I don't think they gave the forums enough of a go -- but it's how they did it."
http://www.ireland.com/newspaper/computimes/1999/0712/comp6.htm
Monday, July 12, 1999
Irish Times
Computimes
MONITOR
Yahoo surrenders to its homesteaders
''Yahoo has once again revised the terms of use for its GeoCities Web community after members protested that proposed copyright clauses released late last month robbed users of control over the content of their own websites. The row started when Geocities members became alarmed by language in an agreement which gave Yahoo "the royalty-free, perpetual, irrevocable. . . license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, perform and display" their content.
''In a clear attempt to mollify users, the new terms
state (our italics): "Yahoo does not claim ownership of the content you
place on your Yahoo GeoCities site. By submitting content to Yahoo for inclusion
on your Yahoo GeoCities site, you grant Yahoo the world-wide, royalty-free and
non-exclusive license to reproduce, modify, adapt and publish the content. . .
for as long as you continue to be a Yahoo GeoCities homesteader."
PROJECT OWNER
Top
REFERENCES
BIBLOGRAPHY
http://jan.ucc.nau.edu/~mpc3/moderators.html
Resources for Moderators and Facilitators of Online
Discussion
mauri collins and Zane L. Berge
Berge Collins
Associates
Comprehensive list of resources.
INDEX
Copyright (C) 1999. Groupsense and Psybernet PO BOX
13543 Christchurch New Zealand
Verbatim copying and distribution of this entire article is permitted for non commercial use in any medium, provided this notice is preserved.
The best way to contribute to future versions of this
document is to join the Roles Online Mailing List, see the description for
details.
____________________________________________________________
Version History
Version 0.07
19990902
This is not a public version. Please do not quote or distribute without author's permission.
Changes in this version:
Rewritten:Sequence of Contents (not reflected in the order of the sections as yet.)Major rewrite of PROJECT MANAGER as posted to the list on Saturday, 7 August 1999
Deleted:
Added:
Whole chunk on OWNER, which now includes Project owner... left old section there for now.
Minor changes in wording in par 2INTRODUCTION. Also in par 1 &2 in WHAT IS A ROLE?
Note about Public document above.
Minor stylistic Changes to the HTML formatting, notably more use of <blockquote>, more to be done.
A new section at the end: CONTRIBUTE TO THIS DOCUMENT
To the first par in WHAT IS A ROLE? also modfied the last par there -- posted these changes to the list and may revise them soon.
Deleted:
Second to last par in 0.05 WHAT
IS A ROLE? was redundant as we put it in the Intro.
Added:
An
additional paragraph to the INTRODUCTION
(second par)
Footnote 1 in ROLES
IN CYBERSPACE
Section at the end on COPYRIGHT
Rough
draft for AUTHOR
A
whole new chunk in EDITOR...
still some there to be deleted etc. From email: Mon, 05 Jul 1999 11:01:30
GMT
Version 0.05
25 June 1999
Changes in this version:
Rewritten:
ROLES IN CYBERSPACE (from Walter Logeman post on 7
June, with some minor changes)
DESIGNER (from Walter Logeman post on
7 June, with some changes)
Moved:
ROLES IN CYBERSPACE to
follow the section on Cyberspace
A paragraph on roles
from
ROLES IN CYBERSPACE to ROLES
Version 0.04
7 June 1999
Changes in this
version:
Rewritten:
WHAT IS A ROLE?
(Status:
Proposal)
Added:
CYBERSPACE (Status:
Proposal)
Version 0.03
29 May 1999
Put the version on the web in in HTML
<http://www.psybernet.co.nz/roles/roles003.htm>
Added:
CONTENTS (with links)