5
Buttheoldest,andstillmostcommonscenarioformostcollaborativewritingsupporthas
been“artifactbased”collaboration.Inthisapproachcomputersupportisconceivedofasa
wayofsupportingauthorsincontributingtheirworkintheformofchangestoashared“ar-
tifact”(adocumentorotherworkspace,likeawhiteboard)thatservesasamediumofcom-
munication,aswellasrecordingtheproductofthatcollaboration.Theapplicationitselfis
someformofmulti-usereditoroperatingonthesharedartifact.Whilesomedoubtshave
beenraisedabouteventhismodelofcollaboration(Williams1992),itisthemodelthathas
hadthemostsuccessofallthecollaborationapproachesthathavebeentried.Italsoisthe
approachthatfitsmostnaturallyintoexistingpatternsofcomputerusebyauthors;most
writersalreadyusecomputertoolsforwriting,soitisnaturaltoextendthosewritingtools
tosupportseveralcollaboratingauthors.
Becausethereareavarietyofcollaborativeworkstyles,andconsequentlyavarietyof
conceptsofcollaborativeediting,systemsforcollaborativewritingsupporthavealsobeen
quitedifferent.Untilrecently,almostallhavebeenclassifiablebyafundamentaldistinction
betweentoolstosupportsynchronousversusasynchronousworkactivities.Thisdistinction
isoneoftheprimaryaxesofEllis,GibbsandRein’stime/spacetaxonomyofcollaborative
work(Ellis,Gibbsetal.1991),withitsfundamentaldivisionofcollaborationintosame
time/differenttimecategories.Systemdesignshavegenerallytargetedeitheroneorthe
otherbutnotbothstylesofwork.Systemsupportmodelsandstrategiesforsynchronous
collaborativeeditinghavebeengeneralizedandformalizedbyimplementationintheformof
toolkitssuchasSuite,Groupkit(RosemanandGreenberg1992),Colab(Stefik,Fosteretal.
1987),Rendezvous(Patterson,Hilletal.1990),DisteditandDistview(KnisterandPrakash
1990;PrakashandKim1994),Timewarp(EdwardsandMynat1997),andavarietyofshared
windowsystems.Theseestablishedtoolkits(sometimesexclusively)concentrateononekind
ofcollaboration:synchronouswork.Supportforasynchronousworkhasnotingeneralledto
thecreationoftoolkits,andhasbeenasomewhatlessactiveresearcharea,thoughithas
6
producedexcellentparadigmaticapplications.ThePrepeditor(Neuwirth,Kauferetal.1990;
Neuwirth,Chandhoketal.1992;Neuwirth,Kauferetal.1994)andLotusNotes(Greifand
Sarin1987),bycontrasttothesynchronoustoolkits,haveconcentratedonsupportforasyn-
chronousandoff-linework,oratleastonpropagatingchangesasconvenientratherthan
alwayspropagatingthemimmediately.
Interestingly,themostwidespreadcommercialgroupwaresolutioninactiveuseisLotus
Notes,whichusesarelativelysimple,asynchronous,artifact-baseddatamodelthatmakes
minimalconsistencyguarantees.Andthemostcommonsystemforsharingtextualand
graphicinformationistheWorldWideWeb(WWW),whichhasbeeneffectivelyusedfora
widevarietyofcollaborativepurposes,andwhichprovidesnosystemlevelsupportforsyn-
chronizationorcollaboration,insteadrequiringeachapplicationorusertoimplementany
synchronizationprotocols.Whilethegeneralityandextensibilityofthesesystemsisamong
theirmajorreasonsforsuccess,theirsynchronizationpoliciesdonotseemtohave.
Onepossibleinterpretationofthesuccessofthesesystemsisthatsynchronizationis
completelyunimportant—however,thefrequencywithwhichsynchronizationmechanisms
arecreatedforWWWapplications,andthepresenceofabasicmechanisminNotesshowthat
itisarequirement.Theirsuccessdespitelimitedconsistencyguaranteesshowsthattosup-
portcollaborationitisnotnecessarytousetherobustbutrigidconsistencymechanismsde-
velopedfordatabases,oreventheless-rigidmechanismsusedinsource-codecontrol.It
seemsratherthattheexplicitmanagementrequiredbysuchmechanismsisactuallytoohigh
formanycollaborationapplications.Alternatively,therangeofvariationofsynchronization
policieshaspreventedthecreationofausefulgeneralmechanism,sothattheburdenofim-
plementingpoliciesinnotesandWWWapplicationsisnotaffectedeitherwaybythebuiltin
capabilitiesofthesystems.Palimpsestisanattempttocreateamechanismflexibleenough
toimplementmanypolicies,andthuscapableofbeingreusedinmanyapplicationswith
differingneeds.
Previous Page Next Page