RE: Taverna Server documentation

[Gale Naylor]

Happy New Year @Ian and @Stian and all! Things are going well. Keep
thinking I'll have time to do more than lurk, but not so far. :)

Looks like things are going well for you, too!

Cheers!

Gale

On Jan 18, 2018 6:22 AM, "Ian Dunlop"  wrote:

> Hello,
>
> Styling seems to have gone a bit crazy on the install guide “Configuration
> Property List” part, lot’s of bold headers. (http://taverna.staging.
> apache.org/documentation/server/3.1/install)
> In http://taverna.staging.apache.org/documentation/server/3.1/usage some
> of the code blocks haven’t rendered correctly, you can still see the ```xml
> markup in some places.
> Also why is the workflow state not rendered as a Taverna workflow (BTW
> that’s a joke )
>
> Overall, good job.
> @Gale Happy New Year. Great to hear from you. Hope things are going well
> for you.
>
> Cheers,
>
> Ian
>
> Sent from Mail for Windows 10
>
> From: Stian Soiland-Reyes
> Sent: 18 January 2018 12:41
> To: dev@taverna.incubator.apache.org
> Subject: Re: Taverna Server documentation
>
> I think we can say the distinction is if the documentation is
> code-related (stays in git aka GitHub) or user-related (stays on our
> website).  With Taverna Server it's a bit tighter together.. all the
> API examples could change from one release to another and easily be
> outdated.
>
> Agree on that the headers and code sections looks better in GtHub
> rendering.
>
> It could be that we can make some tweaks to our website CSS to make it
> more similar?
> I think we are using Bootstrap and a couple of custom overrides in
> https://github.com/apache/incubator-taverna-site/tree/trunk/content/css
>
> On 5 January 2018 at 15:50, Gale Naylor 
> wrote:
> > Happy New Year, all!
> >
> > I was only able to take a quick look on my phone. But the docs look
> pretty
> > good!
> >
> > Stian, what would be the advantage of the docs being on the Apache site
> vs
> > GitHub? I do like the headers and code sections better in GitHub.
> > Personally, the Apache CMS headings seem large and h1/h2 are fairly
> > similar. Also, I like the gray code rendering. But not a big deal.
> >
> > Cheers!
> >
> > Gale
> >
> > On Thu, Jan 4, 2018, 7:18 AM Stian Soiland-Reyes 
> wrote:
> >
> >> I updated
> >> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
> >> to include some table of content - it's still very long and could
> >> probably be split into multiple pages.
> >>
> >> As I fixed some things in its example XML I think it would be cumbersome
> >> to also maintain a OpenOffice version, so I removed those.
> >>
> >> Would this documentation live in GitHub as it is now, or as
> >> separate pages under
> >> https://taverna.incubator.apache.org/documentation/server/ ?
> >>
> >> I had a quick go:
> >>
> >> http://taverna.staging.apache.org/documentation/server/3.1/
> >> http://taverna.staging.apache.org/documentation/server/3.1/install
> >> http://taverna.staging.apache.org/documentation/server/3.1/usage
> >>
> >> Stylistically I think those look quite nice.. your views?
> >>
> >> (Compare with GitHub rendering
> >> https://github.com/apache/incubator-taverna-server/blob/
> master/README.md
> >> https://github.com/apache/incubator-taverna-server/blob/
> master/install.md
> >> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
> >> )
> >>
> >> Note as I just copied from GitHub, that there are a couple of MarkDown
> >> differences that makes the /usage examples look broken or perhaps too
> red.
> >>
> >>
> >>
> >> On Wed, 6 Dec 2017 11:12:04 +, Stian Soiland-Reyes <
> st...@apache.org>
> >> wrote:
> >> > I had a look at the documentation included in the Taverna Server git
> >> > repository https://github.com/apache/incubator-taverna-server
> >> >
> >> > Both install and usage are quite extensive, and describes both how to
> >> > install it and how the services are invoked.
> >> >
> >> > For some reason these where in the repository as binary PDF and DOCX
> >> > files which personally I find a bit odd for a server product.
> >> >
> >> > They also had some outdated references to Univ of Manchester and
> >> > Taverna 2.5.
> >> >
> >> >
> >> > So I changed it to more open formats MarkDown and ODT and added the
> >> > Apache License headers:
> >> >
> >> >
> >> https://github.com/apache/incubator-taverna-server/blob/
> master/install.md
> >> >
> >> https://github.com/apache/incubator-taverna-server/blob/
> master/install.odt
> >> > https://github.com/apache/incubator-taverna-server/blob/
> master/usage.md
> >> > https://github.com/apache/incubator-taverna-server/blob/
> master/usage.odt
> >> >
> >> > Some more tidy-up could be done (e.g. use ```code``` blocks for the
> XML
> >> > examples).
> >> >
> >> >
> >> > The documentation seems very overlapping (or equal) to the 2.5
> >> > Taverna Server documentation that also lives online in the old wiki:
> >> >
> >> > 

Re: Taverna Server documentation

[Stian Soiland-Reyes]

Hmm.. I had a good fight with Markdown. It seemed to think that the
indentation of the config block (intending ) was actually a
continuation of the unordered list above.. How lovely to not have
start-stop tags, uh..

See now at 
http://taverna.staging.apache.org/documentation/server/3.1/install#configuration-property-list
(quite a few ctrl-shift-R seems to be needed)

The Workflow State diagram I hacked together quickly using
https://www.draw.io/ as the one in the .docx was hard to get to look
good outside Word.


So this looks kind of OK, so I'll link to that in the announcement.

On 18 January 2018 at 14:22, Ian Dunlop  wrote:
> Hello,
>
> Styling seems to have gone a bit crazy on the install guide “Configuration 
> Property List” part, lot’s of bold headers. 
> (http://taverna.staging.apache.org/documentation/server/3.1/install)
> In http://taverna.staging.apache.org/documentation/server/3.1/usage some of 
> the code blocks haven’t rendered correctly, you can still see the ```xml 
> markup in some places.
> Also why is the workflow state not rendered as a Taverna workflow (BTW that’s 
> a joke )
>
> Overall, good job.
> @Gale Happy New Year. Great to hear from you. Hope things are going well for 
> you.
>
> Cheers,
>
> Ian
>
> Sent from Mail for Windows 10
>
> From: Stian Soiland-Reyes
> Sent: 18 January 2018 12:41
> To: dev@taverna.incubator.apache.org
> Subject: Re: Taverna Server documentation
>
> I think we can say the distinction is if the documentation is
> code-related (stays in git aka GitHub) or user-related (stays on our
> website).  With Taverna Server it's a bit tighter together.. all the
> API examples could change from one release to another and easily be
> outdated.
>
> Agree on that the headers and code sections looks better in GtHub rendering.
>
> It could be that we can make some tweaks to our website CSS to make it
> more similar?
> I think we are using Bootstrap and a couple of custom overrides in
> https://github.com/apache/incubator-taverna-site/tree/trunk/content/css
>
> On 5 January 2018 at 15:50, Gale Naylor  wrote:
>> Happy New Year, all!
>>
>> I was only able to take a quick look on my phone. But the docs look pretty
>> good!
>>
>> Stian, what would be the advantage of the docs being on the Apache site vs
>> GitHub? I do like the headers and code sections better in GitHub.
>> Personally, the Apache CMS headings seem large and h1/h2 are fairly
>> similar. Also, I like the gray code rendering. But not a big deal.
>>
>> Cheers!
>>
>> Gale
>>
>> On Thu, Jan 4, 2018, 7:18 AM Stian Soiland-Reyes  wrote:
>>
>>> I updated
>>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>>> to include some table of content - it's still very long and could
>>> probably be split into multiple pages.
>>>
>>> As I fixed some things in its example XML I think it would be cumbersome
>>> to also maintain a OpenOffice version, so I removed those.
>>>
>>> Would this documentation live in GitHub as it is now, or as
>>> separate pages under
>>> https://taverna.incubator.apache.org/documentation/server/ ?
>>>
>>> I had a quick go:
>>>
>>> http://taverna.staging.apache.org/documentation/server/3.1/
>>> http://taverna.staging.apache.org/documentation/server/3.1/install
>>> http://taverna.staging.apache.org/documentation/server/3.1/usage
>>>
>>> Stylistically I think those look quite nice.. your views?
>>>
>>> (Compare with GitHub rendering
>>> https://github.com/apache/incubator-taverna-server/blob/master/README.md
>>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>>> )
>>>
>>> Note as I just copied from GitHub, that there are a couple of MarkDown
>>> differences that makes the /usage examples look broken or perhaps too red.
>>>
>>>
>>>
>>> On Wed, 6 Dec 2017 11:12:04 +, Stian Soiland-Reyes 
>>> wrote:
>>> > I had a look at the documentation included in the Taverna Server git
>>> > repository https://github.com/apache/incubator-taverna-server
>>> >
>>> > Both install and usage are quite extensive, and describes both how to
>>> > install it and how the services are invoked.
>>> >
>>> > For some reason these where in the repository as binary PDF and DOCX
>>> > files which personally I find a bit odd for a server product.
>>> >
>>> > They also had some outdated references to Univ of Manchester and
>>> > Taverna 2.5.
>>> >
>>> >
>>> > So I changed it to more open formats MarkDown and ODT and added the
>>> > Apache License headers:
>>> >
>>> >
>>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>>> >
>>> https://github.com/apache/incubator-taverna-server/blob/master/install.odt
>>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.odt
>>> >
>>> > Some more tidy-up could be done 

Re: Publishing Taverna Server 3.1.0-incubating

[Stian Soiland-Reyes]

I will send this announcement shortly:
https://s.apache.org/taverna-server-3.1.0

First I will just fix some of those formatting issues in the
documentation pages, as Ian pointed out.

On 18 January 2018 at 02:04, Stian Soiland-Reyes  wrote:
> In the morning all the mirrors should be good and we can send an
> ANNOUNCE email to announce@apache.  Would anyone care to draft one for
> Taverna Server 3.1.0?
>
> Here's the previous one for Cmd Line:
>
> https://lists.apache.org/thread.html/29484e362f583d71fb99b2f6c334da9010446dcd97060937e5aaa760@%3Cannounce.apache.org%3E
>
> On 18 January 2018 at 02:02, Stian Soiland-Reyes  wrote:
>> After the successful VOTE on Taverna Server 3.1.0 RC3 (here and on
>> general@incubator) I have:
>>
>>
>> published RC3 in dist, now live from
>> https://www.apache.org/dist/incubator/taverna/source/ and most of the
>> mirrors.
>>
>> Published Maven staging repository:
>> http://central.maven.org/maven2/org/apache/taverna/server/
>>
>> Re-tagged in git:
>> https://github.com/apache/incubator-taverna-server/releases/tag/3.1.0-incubating
>>
>> (git tag -s 3.1.0-incubating 3.1.0-incubating-RC3
>> git push origin 3.1.0-incubating
>> git tag -d 3.1.0-incubating-RC3
>> git push origin :3.1.0-incubating-RC3)
>>
>>
>> Bumped taverna-server version to 3.2.0-incubating-SNAPSHOT
>> and taverna-maven-parent to 4-incubating-SNAPSHOT
>> using mvn release:update-versions
>>
>> Updated most (all?) of the git repositories to use
>> apache-taverna-maven-parent 3-incubating instead of
>> 3-incubating-SNAPSHOT or 2-incubating.
>>
>>
>>
>>
>>
>> Website:
>>
>> Added sha256/sha512 hash links to most (all?) of our downloads.
>>
>> Updated https://taverna.incubator.apache.org/download/server/ --
>> Server 2.5 is now just barely mentioned in bottom of page.
>>
>> Published https://taverna.incubator.apache.org/documentation/server/3.1/
>>  (no changes from earlier email, just now accessible from above)
>>
>> Updated https://taverna.incubator.apache.org/ banner on top
>>
>> Updated top bar menu to call it "Apache Taverna Server"
>>
>> Updated javadoc on
>> https://taverna.incubator.apache.org/javadoc/taverna-server/  (I was
>> unable to build these with mvn site -Pfull-site -- had to use mvn
>> javadoc:aggregate
>>
>>
>>
>> Tried, not so successfully, to publish the Taverna Server namespaces on
>> https://taverna.incubator.apache.org/ns/  by copy-pasting from WADL,
>> but I think I got some xmlns declarations wrong).  Also some
>> namespaces like http://ns.taverna.org.uk/2010/xml/server/wsdl/ didn't
>> have an XSD.
>>
>>
>> --
>> Stian Soiland-Reyes
>> http://orcid.org/-0001-9842-9718
>
>
>
> --
> Stian Soiland-Reyes
> http://orcid.org/-0001-9842-9718



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

Re: The app URI scheme -> IANA

[Stian Soiland-Reyes]

It seems getting a provisional allocation with IANA will take just
some days - so I am not sure why this was never done to start with.


Thanks Andy, who helped fix this quickly in Jena - for working with
the current Jena release I let the Taverna Language part that parses
RDF/XML use a fake file:/// URI reference instead.
https://github.com/apache/incubator-taverna-language/pull/37/files

It's not ideal as it has to translate back and forward to match up
again with the RO manifest. Let's try to check if we can catch up with
Jena when we ship Taverna Language next - I think it's due a release
as well to include some recent pull requests.



Yes, no-one should use RDF/XML today.. but that's what COMBINE archives mandate:
http://co.mbine.org/specifications/omex.version-1.pdf#subsection.4


  2014-06-26T10:29:00Z
https://github.com/apache/incubator-taverna-language/blob/master/taverna-scufl2-wfbundle/src/test/resources/org/apache/taverna/scufl2/rdfxml/example/workflowBundle.rdf#L23
:)

On 18 January 2018 at 14:59, Andy Seaborne  wrote:
> Jena doesn't enforce IANA registration.
>
> https://issues.apache.org/jira/browse/JENA-1462
>
> only applied to RDF/XML.
>
> Workaround 1: don't use RDF/XML!
>
> Workaround 2:
>
> Turn off IANA scheme registration checking on:
>
> IRIFactory.iriImplementation()
>
> which was the (incorrectly) used IRIFactory for RDF/XML parsing.
>
>   https://github.com/apache/jena/pull/342/commits/aecfaac0d6
>
> Proper fix: next release.
>
> Andy
>
>
> On 18/01/18 14:30, Ian Dunlop wrote:
>>
>>
>> Hello,
>>
>> Is “fluctual” actually a word?
>> Anyway, what’s the headline news here? Jena can’t parse app:// URLs
>> because they aren’t an approved standard but we need them for the RO bundle.
>> Couldn’t we change the Jena code to play nicely and parse app://? I
>> appreciate getting standards correct but how long will it take?
>>
>> Cheers,
>>
>> Ian
>>
>> Sent from Mail for Windows 10
>>
>> From: Stian Soiland-Reyes
>> Sent: 17 January 2018 19:35
>> To: dev@taverna.incubator.apache.org
>> Subject: The app URI scheme -> IANA
>>
>> In TAVERNA-1027 we came across the app URI scheme
>> not being IANA registered, and since been abandoned
>> by W3C (as the working group collapsed).
>>
>> Well I'm trying to fix that - at least with a provisional registration
>> and an Internet-Draft:
>>
>> https://tools.ietf.org/html/draft-soilandreyes-app-00
>>
>> Comments welcome - preferably as issues/pull requests
>> in https://github.com/stain/I-D
>>
>>
>



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

Re: The app URI scheme -> IANA

[Andy Seaborne]

Jena doesn't enforce IANA registration.

https://issues.apache.org/jira/browse/JENA-1462

only applied to RDF/XML.

Workaround 1: don't use RDF/XML!

Workaround 2:

Turn off IANA scheme registration checking on:

IRIFactory.iriImplementation()

which was the (incorrectly) used IRIFactory for RDF/XML parsing.

  https://github.com/apache/jena/pull/342/commits/aecfaac0d6

Proper fix: next release.

Andy

On 18/01/18 14:30, Ian Dunlop wrote:


Hello,

Is “fluctual” actually a word?
Anyway, what’s the headline news here? Jena can’t parse app:// URLs because 
they aren’t an approved standard but we need them for the RO bundle. Couldn’t 
we change the Jena code to play nicely and parse app://? I appreciate getting 
standards correct but how long will it take?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2018 19:35
To: dev@taverna.incubator.apache.org
Subject: The app URI scheme -> IANA

In TAVERNA-1027 we came across the app URI scheme
not being IANA registered, and since been abandoned
by W3C (as the working group collapsed).

Well I'm trying to fix that - at least with a provisional registration
and an Internet-Draft:

https://tools.ietf.org/html/draft-soilandreyes-app-00

Comments welcome - preferably as issues/pull requests
in https://github.com/stain/I-D

RE: The app URI scheme -> IANA

[Ian Dunlop]

Hello,

Is “fluctual” actually a word?
Anyway, what’s the headline news here? Jena can’t parse app:// URLs because 
they aren’t an approved standard but we need them for the RO bundle. Couldn’t 
we change the Jena code to play nicely and parse app://? I appreciate getting 
standards correct but how long will it take?

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 17 January 2018 19:35
To: dev@taverna.incubator.apache.org
Subject: The app URI scheme -> IANA

In TAVERNA-1027 we came across the app URI scheme
not being IANA registered, and since been abandoned
by W3C (as the working group collapsed).

Well I'm trying to fix that - at least with a provisional registration
and an Internet-Draft:

https://tools.ietf.org/html/draft-soilandreyes-app-00

Comments welcome - preferably as issues/pull requests
in https://github.com/stain/I-D


-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

RE: Taverna Server documentation

[Ian Dunlop]

Hello,

Styling seems to have gone a bit crazy on the install guide “Configuration 
Property List” part, lot’s of bold headers. 
(http://taverna.staging.apache.org/documentation/server/3.1/install)  
In http://taverna.staging.apache.org/documentation/server/3.1/usage some of the 
code blocks haven’t rendered correctly, you can still see the ```xml markup in 
some places.
Also why is the workflow state not rendered as a Taverna workflow (BTW that’s a 
joke )

Overall, good job.
@Gale Happy New Year. Great to hear from you. Hope things are going well for 
you.

Cheers,

Ian

Sent from Mail for Windows 10

From: Stian Soiland-Reyes
Sent: 18 January 2018 12:41
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna Server documentation

I think we can say the distinction is if the documentation is
code-related (stays in git aka GitHub) or user-related (stays on our
website).  With Taverna Server it's a bit tighter together.. all the
API examples could change from one release to another and easily be
outdated.

Agree on that the headers and code sections looks better in GtHub rendering.

It could be that we can make some tweaks to our website CSS to make it
more similar?
I think we are using Bootstrap and a couple of custom overrides in
https://github.com/apache/incubator-taverna-site/tree/trunk/content/css

On 5 January 2018 at 15:50, Gale Naylor  wrote:
> Happy New Year, all!
>
> I was only able to take a quick look on my phone. But the docs look pretty
> good!
>
> Stian, what would be the advantage of the docs being on the Apache site vs
> GitHub? I do like the headers and code sections better in GitHub.
> Personally, the Apache CMS headings seem large and h1/h2 are fairly
> similar. Also, I like the gray code rendering. But not a big deal.
>
> Cheers!
>
> Gale
>
> On Thu, Jan 4, 2018, 7:18 AM Stian Soiland-Reyes  wrote:
>
>> I updated
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> to include some table of content - it's still very long and could
>> probably be split into multiple pages.
>>
>> As I fixed some things in its example XML I think it would be cumbersome
>> to also maintain a OpenOffice version, so I removed those.
>>
>> Would this documentation live in GitHub as it is now, or as
>> separate pages under
>> https://taverna.incubator.apache.org/documentation/server/ ?
>>
>> I had a quick go:
>>
>> http://taverna.staging.apache.org/documentation/server/3.1/
>> http://taverna.staging.apache.org/documentation/server/3.1/install
>> http://taverna.staging.apache.org/documentation/server/3.1/usage
>>
>> Stylistically I think those look quite nice.. your views?
>>
>> (Compare with GitHub rendering
>> https://github.com/apache/incubator-taverna-server/blob/master/README.md
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> )
>>
>> Note as I just copied from GitHub, that there are a couple of MarkDown
>> differences that makes the /usage examples look broken or perhaps too red.
>>
>>
>>
>> On Wed, 6 Dec 2017 11:12:04 +, Stian Soiland-Reyes 
>> wrote:
>> > I had a look at the documentation included in the Taverna Server git
>> > repository https://github.com/apache/incubator-taverna-server
>> >
>> > Both install and usage are quite extensive, and describes both how to
>> > install it and how the services are invoked.
>> >
>> > For some reason these where in the repository as binary PDF and DOCX
>> > files which personally I find a bit odd for a server product.
>> >
>> > They also had some outdated references to Univ of Manchester and
>> > Taverna 2.5.
>> >
>> >
>> > So I changed it to more open formats MarkDown and ODT and added the
>> > Apache License headers:
>> >
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.odt
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.odt
>> >
>> > Some more tidy-up could be done (e.g. use ```code``` blocks for the XML
>> > examples).
>> >
>> >
>> > The documentation seems very overlapping (or equal) to the 2.5
>> > Taverna Server documentation that also lives online in the old wiki:
>> >
>> > https://taverna.incubator.apache.org/documentation/server/
>> >
>> > .. but I have not checked this page by page.
>> >
>> >
>> >
>> > What do you think:
>> >
>> > Is the Markdown version more or less maintainable?
>> >   (e.g. the tables can get messy)
>> >
>> > Do we keep maintaining the OpenDocument versions (packaged as PDF in
>> release)?
>> >
>> > Do we keep the Markdown documentation as part of the git repository (and
>> > hence the Taverna Server distribution), or move it to the
>> > taverna.apache.org website? (it would probably work out of the
>> > box)
>> >
>> >
>> 

Re: Taverna Server documentation

[Stian Soiland-Reyes]

I think we can say the distinction is if the documentation is
code-related (stays in git aka GitHub) or user-related (stays on our
website).  With Taverna Server it's a bit tighter together.. all the
API examples could change from one release to another and easily be
outdated.

Agree on that the headers and code sections looks better in GtHub rendering.

It could be that we can make some tweaks to our website CSS to make it
more similar?
I think we are using Bootstrap and a couple of custom overrides in
https://github.com/apache/incubator-taverna-site/tree/trunk/content/css

On 5 January 2018 at 15:50, Gale Naylor  wrote:
> Happy New Year, all!
>
> I was only able to take a quick look on my phone. But the docs look pretty
> good!
>
> Stian, what would be the advantage of the docs being on the Apache site vs
> GitHub? I do like the headers and code sections better in GitHub.
> Personally, the Apache CMS headings seem large and h1/h2 are fairly
> similar. Also, I like the gray code rendering. But not a big deal.
>
> Cheers!
>
> Gale
>
> On Thu, Jan 4, 2018, 7:18 AM Stian Soiland-Reyes  wrote:
>
>> I updated
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> to include some table of content - it's still very long and could
>> probably be split into multiple pages.
>>
>> As I fixed some things in its example XML I think it would be cumbersome
>> to also maintain a OpenOffice version, so I removed those.
>>
>> Would this documentation live in GitHub as it is now, or as
>> separate pages under
>> https://taverna.incubator.apache.org/documentation/server/ ?
>>
>> I had a quick go:
>>
>> http://taverna.staging.apache.org/documentation/server/3.1/
>> http://taverna.staging.apache.org/documentation/server/3.1/install
>> http://taverna.staging.apache.org/documentation/server/3.1/usage
>>
>> Stylistically I think those look quite nice.. your views?
>>
>> (Compare with GitHub rendering
>> https://github.com/apache/incubator-taverna-server/blob/master/README.md
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> )
>>
>> Note as I just copied from GitHub, that there are a couple of MarkDown
>> differences that makes the /usage examples look broken or perhaps too red.
>>
>>
>>
>> On Wed, 6 Dec 2017 11:12:04 +, Stian Soiland-Reyes 
>> wrote:
>> > I had a look at the documentation included in the Taverna Server git
>> > repository https://github.com/apache/incubator-taverna-server
>> >
>> > Both install and usage are quite extensive, and describes both how to
>> > install it and how the services are invoked.
>> >
>> > For some reason these where in the repository as binary PDF and DOCX
>> > files which personally I find a bit odd for a server product.
>> >
>> > They also had some outdated references to Univ of Manchester and
>> > Taverna 2.5.
>> >
>> >
>> > So I changed it to more open formats MarkDown and ODT and added the
>> > Apache License headers:
>> >
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.md
>> >
>> https://github.com/apache/incubator-taverna-server/blob/master/install.odt
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.md
>> > https://github.com/apache/incubator-taverna-server/blob/master/usage.odt
>> >
>> > Some more tidy-up could be done (e.g. use ```code``` blocks for the XML
>> > examples).
>> >
>> >
>> > The documentation seems very overlapping (or equal) to the 2.5
>> > Taverna Server documentation that also lives online in the old wiki:
>> >
>> > https://taverna.incubator.apache.org/documentation/server/
>> >
>> > .. but I have not checked this page by page.
>> >
>> >
>> >
>> > What do you think:
>> >
>> > Is the Markdown version more or less maintainable?
>> >   (e.g. the tables can get messy)
>> >
>> > Do we keep maintaining the OpenDocument versions (packaged as PDF in
>> release)?
>> >
>> > Do we keep the Markdown documentation as part of the git repository (and
>> > hence the Taverna Server distribution), or move it to the
>> > taverna.apache.org website? (it would probably work out of the
>> > box)
>> >
>> >
>> > --
>> > Stian Soiland-Reyes
>> > http://orcid.org/-0001-9842-9718
>> >
>>



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718