Great job with the XSDs! I think we should keep it at Apache Taverna under incubator-taverna-language - I know Baclava will be legacy as it's only made in Taverna 2, but Ernesto has shown interest in using it to do a tool for databundle conversion as they have many Baclava files from Taverna 2. That is exactly the kind of engagement we should be encouraging under Apache.
It's also not very different to how scufl2-t2flow can read in Taverna 2 workflows - and with your XSDs the code would be quite clean without legacy libraries popping in. We just need to ensure that tool can't WRITE baclava files.. ;-) Should we also put the XSD at http://taverna.incubator.apache.org/ns/ ? I know baclava is under a dubious namespace like http://org.embl.ebi.escience/baclava/0.1alpha - but http://ns.taverna.org.uk/ is where we have published all the other schemas. (.. although .escience is not a top-level domain, .science is now! http://nic.science/ ) On 30 January 2015 at 16:24, alaninmcr <alanin...@googlemail.com> wrote: > Hello everybody, > > I thought I'd check what is the best place to put the Baclava language code > for reading / writing Baclava based on two xsd's. > > It could go in the incubator site or in github. I am inclined to go for > github. > > Alan -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
