Re: [icom] Versioninig?

["marco pallot" <marc.pallot@esoce.net>]

I'm forwarding my reply (see below) about versioning as it seems it did not 
pass...

Marc Pallot
Centre for Concurrent Enterprise
Nottingham University
Collaborative Work & Infrastructure
ESoCE-NET


----- Original Message ----- 
From: "marc pallot" <marc.pallot@9online.fr>
To: "Patrick Durusau" <patrick@durusau.net>; <icom@lists.oasis-open.org>
Cc: <mpallot@esoce.net>
Sent: Thursday, April 02, 2009 10:55 PM
Subject: Re: [icom] Versioninig?


> Hi Patrick,
>
> Yes, right, versioning might be mandatory for a shared document or other 
> types of content objects...which is not the case for an email...but for 
> the attached file(s).
>
> Within ECOSPACE we have a "notify & upload" Composite Collaborative 
> Service which is sending out an email and automatically uploading a 
> virtually attached document into a shared workspace where versioning can 
> be switched on. It has also the advantage of avoiding to be overflooding 
> email boxes with gigabytes of attache files.....:-)
>
> The direct consequence is that versioning should be part of the model.
>
> I do believe that the collaborative work we have to carry on in the OASIS 
> ICOM wiki page for categorising all needed "entities" and "artefacts" 
> should help to clarify this kind of issues.
>
> Cheers,
> Marc
>
>
> Marc Pallot
> Centre for Concurrent Enterprise
> Nottingham University
> Collaborative Work & Infrastructure
> ESoCE-NET
>
>
> ----- Original Message ----- 
> From: "Patrick Durusau" <patrick@durusau.net>
> To: <icom@lists.oasis-open.org>
> Sent: Thursday, April 02, 2009 9:34 PM
> Subject: [icom] Versioninig?
>
>
>> Greetings!
>>
>> During Eric's presentation (which I am finding very helpful) he mentions 
>> that there is no "versioning" of email.
>>
>> It strikes me as odd that email or any other content, which might be 
>> authored in a collaborative context, cannot be versioned.
>>
>> I suppose if email is thought of as originating outside of the 
>> collaborative model then versioning may not be relevant but I would 
>> hesitate to say that versioning isn't relevant even there.
>>
>> For example, what if I send an email that contains a proposal for 
>> inclusion in ICOM and then after some discussion, I revise my proposal 
>> such that it should be considered both an continuation of the prior email 
>> but also a new proposal. In that case, capturing that my second email is 
>> a subsequent version of the first one may (or may not) be important.
>>
>> I suppose the more general question (which I should read the Beehive 
>> model to see what it says) is what relationships, such as versioning, 
>> that we can model between emails or other content?
>>
>> Hope that everyone is having a great day!
>>
>> Patrick
>>
>> -- 
>> Patrick Durusau
>> patrick@durusau.net
>> Chair, V1 - US TAG to JTC 1/SC 34
>> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
>> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  Follow this link to all your TCs in OASIS at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>
>
>