[MOBY-l] Versioning of Moby objects

[Mark Wilkinson]

I don't think we have really considered objects to be anything more than  
"containers", so the idea of versioning an object when the data inside it  
changes has never come up.  Certainly we do version our Object's as  
defined by the ontology (i.e. if the nature of the "container" changes,  
then that Object is re-versioned) but Moby objects really don't pay any  
attention to the data that is passed around inside of them.   If you think  
this is a useful and missing feature, please feel free to submit an RFC :-)

M




On Wed, 02 Apr 2008 07:43:13 -0700, Ola Spjuth <ola.spjuth at farmbio.uu.se>  
wrote:

> Hi,
>
> We in the Bioclipse project (www.bioclipse.net) are working for as much  
> Moby interoperability as possible in our next version. As Bioclipse is a  
> workbench where people can download and edit resources, we had an  
> interesting discussion today how Moby objects (with ID and NAMESPACE)  
> are treated with respect to modifications. Let's say I download a  
> sequence from Genbank, and store it on my local computer. The question  
> was how a modification to this resource should be handled. We considered  
> having some sort of flag for this, or maybe a 'revision' or 'version'  
> parameter, but wanted to hear your view on this matter.
>
> I'd also like to make a humble request that someone elaborated on the  
> use of LSID in Moby, and related this to the REST approach when it comes  
> to services, resources, and versioning of these.
>
> Cheers,
>
>     .../Ola
> _______________________________________________
> moby-l mailing list
> moby-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-l



-- 
--
Mark Wilkinson
iCAPTURE Centre