I have copied over the pages as suggested except:
http://dev.mygrid.org.uk/wiki/display/developer/SCUFL2+API
as it is significantly different to:
https://github.com/apache/incubator-taverna-language

I have not yet update any examples as suggested here.

I have added an extra "scufl2" menu list which shows up whenever a scufl2 page 
is selected.

Next steps;

Mark mygrid pages deprecated

Do the download page.

copy/ moved some of the stuff from 
https://github.com/apache/incubator-taverna-language to the api page 

Update examples.

Please: If anyone would like to make any changes please reply to this first so 
we don't get conflicts/ duplicate work.

Christian


________________________________________
From: Stian Soiland-Reyes [[email protected]]
Sent: Friday, March 06, 2015 12:22 PM
To: [email protected]
Subject: Re: Scufl 2 Pages for website

On 3 March 2015 at 15:07, Christian Brenninkmeijer
<[email protected]> wrote:
> Looking at the mygrid pages I suggest coping the following pages:
> http://dev.mygrid.org.uk/wiki/display/developer/SCUFL2

OK

> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2-DataLink
> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2-Processors
> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2-Workflow

Outdated

If you feel like updating them - simply copy the relevant filepaths and XML from
.././incubator-taverna-language/taverna-scufl2-examples/examples/helloanyone.wfbundle


> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2-Profile
Empty


> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2+URIs

Fine (But not all of those are handled by guess.taverna.org.uk yet)

> http://dev.mygrid.org.uk/wiki/display/developer/SCUFL2+use+cases

Drop it.


> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2-WorkflowBundle

Generally fine - but some outdated examples.


> http://dev.mygrid.org.uk/wiki/display/developer/Taverna+Workflow+Bundle

Fine

> http://dev.mygrid.org.uk/wiki/display/developer/Taverna+URI+templates

This is the proposal that lead to
http://dev.mygrid.org.uk/wiki/display/developer/Scufl2+URIs
.. but as it contains the explanations perhaps some its content should
go into Scufl2+URIs

See also http://ns.taverna.org.uk/ which explains the namespaces



> I suggest not folling these pages as the are marked as old or incomplete.
> Do we need stubs for any of these or do  I just remove the links?
> http://dev.mygrid.org.uk/wiki/display/developer/SCUFL2+API

No, this is very much up to date and needs to move over.


> http://dev.mygrid.org.uk/wiki/display/developer/Scufl2+Ontology

Out of date - but placeholder needed as

http://ns.taverna.org.uk/2010/scufl2#http://ns.taverna.org.uk/2010/scufl2#

goes there.


> http://dev.mygrid.org.uk/wiki/display/developer/SCUFL2+language
> http://dev.mygrid.org.uk/wiki/pages/viewpage.action?pageId=5211689
> http://dev.mygrid.org.uk/wiki/display/developer/2011-02+Scufl2+status
> http://dev.mygrid.org.uk/wiki/display/developer/2011-02+Data+bundle
Outdated




>
> I was also not going to copy the proposal pages across:
> http://dev.mygrid.org.uk/wiki/display/developer/2013-06-12+Configuration+as+JSON
> http://dev.mygrid.org.uk/wiki/display/developer/2010-05+Semantification
> http://dev.mygrid.org.uk/wiki/display/TAVOSGI/2013-02+Data+bundle+requirements

Agreed.


> There is a lot of use of
>  "http://ns.taverna.org.uk/2010/workflows"; expecialy in minted URIs
> 1. Is this still correct?

Yes - see

"ns.taverna.org.uk and apache.org"
at
http://taverna.incubator.apache.org/ns/

We will transfer DNS of *.taverna.org.uk to Apache.


> 2. As that points to http://taverna.incubator.apache.org/ns/2010/workflows
> we should put a holding page there.

I think it should be without the plural - e.g.

http://guess.taverna.org.uk/ does not support /2010/workflow/ yet -
but it should not be hard as it would look pretty much the same as

http://guess.taverna.org.uk/workflowBundle/2f0e94ef-b5c4-455d-aeab-1e9611f46b8b/workflow/HelloWorld/processor/hello/out/output1


--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/0000-0001-9842-9718

Reply via email to