Cool!

Actually, Neo4j has a (almost) complete SPARQL layer now, so it will
be interesting to see if that will be sufficient to support the qi4j
scenarios ...

/peter

GTalk: neubauer.peter
Skype peter.neubauer
ICQ 18762544
Phone +46704 106975
LinkedIn http://www.linkedin.com/in/neubauer
Twitter http://twitter.com/peterneubauer

http://www.neo4j.org - New Energy for Data - the Graph Database.
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.




On Fri, Aug 15, 2008 at 7:36 AM, David Leangen <[EMAIL PROTECTED]> wrote:
>
> Wow!
>
> This is great stuff!! :-)
>
>
>
>
> On Aug 15, 2008, at 2:27 PM, Rickard Öberg wrote:
>
>> Hey,
>>
>> I just committed a first version of a SPARQL endpoint. It sits at
>> /qi4j/query, and if you just go there with a web browser it will
>> show a
>> HTML form where you can enter a SPARQL query. When submitted the query
>> will be sent to the RDF repository that backs the EntityFinder, so you
>> can essentially introspect and test queries. The result back is in
>> RDF/XML, as per the SPARQL WebService spec. If you go to
>> /qi4j/query.html however the result from the submit will be in XHTML
>> (actually it's the same RDF/XML but with an XSLT processing
>> instruction
>> to convert it to XHTML), so it is much easier to read :-)
>>
>> You can also use /qi4j/query.srj if you want the results formatted as
>> JSON, for AJAX apps.
>>
>> I implemented this for use with a SPARQL EntityFinder on the client,
>> but
>> a nice side-effect is that this also makes it easier to do webapps
>> that
>> access your domain model through AJAX or similar. Basically, you can
>> now
>> use something like Neo4j as your EntityStore, Sesame for the indexing,
>> write the domain model in Java/Qi4j, and then access it automagically
>> through SPARQL/RDF. Cool stuff!
>>
>> /Rickard
>>
>> _______________________________________________
>> qi4j-dev mailing list
>> [email protected]
>> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>
>
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>
>

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to