[vos-d] delineation and revision control

[Reed Hedges]

Yes, only some things would be versioned, or have different policies as
Lalo suggests.

Yes, child linking has to be preserved correctly. I think we can
basically take an object's child list as part of its state. When you
make a new version you might change those, or copy them whole from the
original.  In your example, the texture belongs to both I guess, but
really, both objects have links/references to some objects, that it 
just happens to be the same one can be looked over for the most part I
think.

Reed



On Wed, May 09, 2007 at 11:45:50AM +0200, Karsten Otto wrote:
> Well, Lars' suggestion of versioning only "interesting" parts and  
> your suggestion of horizons seem reasonable, but I don't think we  
> have the basis for this in VOS. A vobject usually cannot live as  
> isolated entity, but *requires* a number of relations to child  
> vobjects to make sense; thus any user-percievable "world object" is  
> actually a subgraph of the overall world graph.
> 
> The problem is delineation: It is not clear which subgraphs represent  
> independent "world objects", or if there is even a distinctive  
> decomposition. For example, two objecs may share a texture - which  
> vobject does it "belong" to? If you change one vobject, do you  
> include the texture in the version? Where do you stop following  
> relational links? I don't recall if there is any prohibition in VOS  
> against cycles in the graph - I think there isn't - so matters become  
> even more complicated.
> 
> The only separation I currently see in VOS is the relation between  
> the site vobject and its children, but even here it is not clear  
> which children represent aspects of the site itself, which are  
> scenery, and which are avatars.
> 
> Any suggestions?
> 
> Regards,
> Karsten Otto (kao)
> 
> 
> _______________________________________________
> vos-d mailing list
> vos-d at interreality.org
> http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d