Of course, your approach of prepending the repository name would probably 
eliminate any future issue in this regard.  Whatever you feel is best...   ;)

On Jan 5, 2012, at 4:49 PM, Greg Von Kuster wrote:

> Yes, this is certainly important, but I think the hope is that proprietary 
> data types will not become so prevalent that name-spacing the extensions is 
> necessary. 
> 
> On Jan 5, 2012, at 4:15 PM, Jim Johnson wrote:
> 
>> 
>> Big Question?    
>> When I started creating all those datatype classes for mothur, I just 
>> labeled the the file_ext as mothur generated them for its output files.  
>> Will we have namespace issues?  
>> Should the file_ext fields include the toolshed name, e.g.   should "otu"   
>> be named "mothur.otu" to avoid conflicts with other downloaded tools from 
>> the toolshed?  
>> Seems like this would be the time to establish rules/practices for such 
>> concerns.
>> 
>> JJ
>> 
>> 
>> 
> 
> 
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> 
> http://lists.bx.psu.edu/

Greg Von Kuster
Galaxy Development Team
g...@bx.psu.edu




___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/

Reply via email to