La Casa nel ~Mare~Running away from slavery

I’m trying to understand:

1. how I could link bug data coming from a Hackystat server with bug data coming from external datasets
2. which are these datasets and how could I retrieve their hosts
3. how could I know the proper uri to use their own sparql endpoints (necessary to browse their internal stored data)
4. how could I allow at least Hackystat servers to browse their bug data with each other; which means how could I implement a sparql endpoint or use an already existent tool even if I don’t have any database (there are lots of tools out there providing also sparql endpoints but only if linked to a database)

Do you know how bugs can be linked? and tests? and development phases? No one has already linked them and no one knows. To search for linkable data which not adhere to a simple pattern such as the one used for books for example. I need a Sparql endoint, which generally requires a database (all the tools providing them requires a database), relational or not, with which communicate through a mapping or directly, in which are stored data. But I was discouraged to use a database. Consequently I hope it’s not so, but it could be necessary for me to handle by myself the sparql syntax translating queries to SensorBase Api calls.

Moreover I need to have at least linked data about bugs and tests implemented within the 25th of July; then I should have also linked data about users and projects within the end of July. While implementing them I’m going also to refine the Api to make the server following the official rules to construct URIs and publish ontologies stated at http://www.w3.org/TR/chips/ and at http://www.w3.org/TR/swbp-vocab-pub/ .

HOWEVER talking about more concrete things, this is the point reached currently by me while trying to clarify the doubts listed above:
Since now the only way to link a bug with another external one, consists in searching external datasets for bug descriptions containing the URI of the bug that you want to link, within their ’summary’ or ‘description’ fields.
I’m searching for an alternative way to determine if two bugs are linkable, because this one imply that external developers know the URI of my own bug a priori, otherwise they couldn’t insert it in the description of their bugs, and I find this implication a little bit too constrained.
However even if finally I’ll use this mechanism to search for linkable external bugs, I need a mechanism to retrieve all those external datasets. Even retrieving the other hackystat servers could become a problem. I’d like to avoid having a static list of datasets to crawl..I’d like to use a more dynamic way to list them…a list which is enlarged as new datasets become available and which is available itself to everyone. What I’d like to have is a framework such Umbel that provides subject concepts of which datasets are instances according to their topic. Then instead of search for a list of datasets related to the ‘Bug’ topic, I could simply declare myself of being an instance of the Umbel subject concept ‘Bug’ and then crawl or the other instances of that same concept. but I don’t know if this is actually realizable and I’ve asked for it on their mailing list, still waiting for an answer.
if this will be not realizable I’ll need a static list of hosts inviting at least the users of other Hackystat servers to add themself to this list.

Then I have to better focus on ways to link tests.

I’m really busy.
cheers & cheers
myriam