On 1/28/2014 10:57, Anton Kulaga wrote:
Thank you for the response,
I think putting spin-api to the public repository is the best way to
make it widely adopted and get more feedback and contributions from
the community.
At the moment I am trying to apply SPIN in my app (that uses BigData
as repository) to store and retrieve SPARQL quires and SPIN
Templates ( I am not interested in other features right now ), is
there any Sesame adapter for SPIN-API or at least a test suite ( +
guidlines) that one can use for implementing it? I think lack of
Sesame support together with lack of public repository is the main
obstacle to wide SPIN adoption.
Native sesame support would require a completely new implementation,
which is not on our roadmap but would be a nice open source project for
someone else.
Other sesame support is available through Graph-level adapters. We have
done this with TopBraid. The SPIN API doesn't care what the underlying
query graph is, so it can be a Graph that redirects its requests to a
Sesame server.
>We had thought about branching off a second, public repository but
this appeared to be too difficult to synchronize so we haven't done
this yet.
Well, you can have several branches (you can use git submodule to get
them directly from github) as well as put a github hook to the build
server (I did this with travis but actually it is possible to
configure a variety of build servers there) so if somebody makes a
pull request that breaks integration with other TopBraid code you will
immediately know it and will not merge that commit to the master branch.
We would not be able to let 3rd party code go directly into the product
code base. I don't know git well enough to configure it in a way that
would allow me to push changes to both a public and a local repository,
but you are right that this is the way to go. I will discuss internally.
P.S. By the way, http://spinrdf.org/ is down now ( =(
Thanks for pointing this out - we have just moved the TQ web site and I
guess the SPIN web site got temporarily deactivated. We're looking into
this.
Thanks
Holger
--
-- You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL
Web Pages and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
