Don; I believe that working copies are designed to do just what you are asking for.  All changes to a vocabulary concept can be traced back to their origin.  In addition, there can be multiple working copies active at any time.  However, working copies of working copies is not something we'd want to get into.  I don't think you would either.

Also, having multiple copies of a production copy only makes sense if you expect the vocabularies to be managed separately.  Otherwise you eventually come across the need to merge the vocabularies and have people manually correct all of the conflicts.  BTW, TopBraid EVN takes a proactive approach to change management.  When selecting a concept in the EVN form, you can choose "Show affected working copies..." to display all of the changes being made to that concept in active working copies.

If you do expect that users can create and manage separate version of the production model, I'd suggest making a copy of the vocabulary.  Merges are no better and no worse by doing so.

But the real advice is to have users create separate working copies from the "gold standard" production copy.  They can then use
"Show affected working copies..." to minimize conflicts when merging.  Unless there is a clear use case that contradicts this, any other approach leads to a chaotic loss of a standard vocabulary.

-- Scott

On 4/6/2013 3:55 AM, Don Jennings wrote:
Hi Bob, Scott,

we want to be able to view the multiple versions of a given vocabulary and use/import the multiple versions in other vocabularies. Basically, we want to treat each version as a separate entity but somehow tag that the versions represent  a time series of the same vocabulary concept. We might  also want to impose restrictions on previous versions of a vocabulary so that users could only create version N+1 by starting with version N.

On Wednesday, April 3, 2013 1:56:23 PM UTC-4, Don Jennings wrote:
We have some in house users looking at EVN, and some initial questions have arisen over the out of the box functionality. Specifically:

1. vocabulary versioning. what mechanisms are used (or available) to tag, store and evolve multiple versions of a given vocabulary? I.e., is there something more than store-it-in-SVN available within the tool? We anticipate having multiple versions of a given vocabulary at any given time actively in use.

2. Is full text search on and across vocabularies supported? E.g., I type in "Dog" and find all vocabulary terms with the word Dog in them or associated with them in comments.

3. Does the auditing functionality support logging of:
  a. who performs an action
  b. when the action is performed
  c. what action was performed
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live,
TopBraid Ensemble, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to