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 Apache Taverna (incubating) team is pleased to announce the release of
apache-taverna-server 3.1.0-incubating
This announcement is also available at:
https://s.apache.org/taverna-server-3.1.0
Apache Taverna is a domain-independent suite of tools used to design
and execute data-driven workflo
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#con
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 ca
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:/
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/X
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 ho
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’
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 he
