Hi Peter,
just following up on this old thread, I have meanwhile added a new servlet
/tbl/describe that will do content negotiation in the spirit of the "cool URIs"
linked data movement. Basically, this looks at the incoming request and either
returns RDF triples or an HTML rendering, depending on the requested mime type.
For RDF triples, it will return the same triples that are shown when you go to
the Source Code tab of a selected resource in TBC: all triples where the
resource is the subject, plus any blank node trees that belong to it. The
latter includes OWL restrictions, SWRL and SPIN rules etc. For mime type
text/html, the servlet will delegate to a corresponding UISPIN call to deliver
the best suitable rendering for the resource.
Some details from the JavaDoc
/**
* A simple servlet to support using TBL as a linked data server.
* Depending on the request, this either returns a human-readable
representation of a resource
* (using UISPIN) or the relevant triples describing the resource.
*
* Arguments:
* _resource: the URI of a resource to render
* _format (optional): the mime type, overrides mime type of http
request
*
* Output:
* for application/rdf+xml: the relevant triples for that resource in
RDF/XML
* for text/turtle: the relevant triples for that resource in Turtle
* the UISPIN rendering for all other mime types
With this simple servlet, I believe the only thing you need to do with a TBL
server is to create an alias URL that matches the base URI of your ontologies,
e.g.
http://example.org/mymodel#MyClass
would have to be rewritten by your web server configuration to
http://my.org:8080/tbl/tbl/describe?_resource=http://example.org/mymodel#MyClass
(where the special characters of the argument would have to be properly URL
escaped).
I don't think we can do much on the TBL side to make this more out of the box,
so a little bit of server configuration would still be required on your end.
Please let me know if this would work for you - this is for 3.4
Regards,
Holger
On Aug 10, 2010, at 8:28 PM, peter wrote:
> Thanks, Holger, that sounds much like what I'm hoping for (URIs that
> look "natural" as opposed to TBL web services).
>
> Scott: The static export option is not suitable for my purpose (though
> useful in another context), and I wish to avoid the creation of
> specific web services. I'll happily wait till 3.4 comes out and see
> what's available.
>
> Cheers
> Peter
>
> --
> You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
> TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion 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
