Hi Oleksandr,
We do have similar requirement of publish/export taxonomies to custom
format like HTML, CSV, XML, json, etc. If you are already done with this
then could you please share your experience. What could be the better way
to do it, using SWP or SPARQLMotion or creating a new Java servlet?
Thanks,
Sanjeev
On Tuesday, February 21, 2017 at 1:59:07 PM UTC+5:30, Oleksandr Mandryk
wrote:
>
> Hi Holger,
>
> Thank you and RY! :) Looks like it's exactly what I need.
>
> Best regards,
> Oleksandr Mandryk
>
> On Tuesday, February 21, 2017 at 2:28:55 AM UTC+1, Holger Knublauch wrote:
>>
>> A colleague (thanks RY) just reminded me that we do have a help page on
>> the Java extension mechanism:
>>
>> TBC > Help > Help Contents > TopBraid Composer > Extending TopBraid
>> Suite
>>
>> HTH
>> Holger
>>
>>
>> On 21/02/2017 10:00, Oleksandr Mandryk wrote:
>>
>> Hi Holger,
>>
>> thank you very much for the explanation!
>>
>> Best regards,
>> Oleksandr Mandryk
>>
>> On Tuesday, February 21, 2017 at 12:33:34 AM UTC+1, Holger Knublauch
>> wrote:
>>>
>>> Hi Oleksandr,
>>>
>>> with Java there is quite a bit of complexity involved. You would need to
>>> develop an Equinox/Eclipse plugin - there are general guides on how to get
>>> started on the web. This plugin would need to declare a dependency on the
>>> plugin org.topbraid.core and org.topbraid.lib.jena. Then write your SPARQL
>>> function against the Jena API by implementing the Function interface. Tell
>>> TopBraid about it through the extension point
>>> org.topbraid.core.sparqlfunctions. You then need to create an Equinox
>>> bundle for this and add that bundle to the dropins folder of your TopBraid
>>> installation.
>>>
>>> 5.3 will include an experimental JavaScript integration that would allow
>>> people to create new functions without going through these complex steps.
>>>
>>> Currently supported alternatives include SWP and SPARQLMotion, both of
>>> which could be used to produce the output you are describing below.
>>>
>>> HTH
>>> Holger
>>>
>>> On 21/02/2017 9:25, Oleksandr Mandryk wrote:
>>>
>>> Hi Holger,
>>> thank you very much for quick reply!
>>>
>>> I'm Java software engineer so Java would be the most comfortable option
>>> for me.
>>>
>>> Could you please explain a little bit more? By "Java is a supported
>>> option" you mean that idea with servlet is ok
>>> or there is something like API that allows integrate a Java service?
>>>
>>> Regarding SPARQL currently I have no idea how to implement a function
>>> that will convert RDF to XML like this:
>>>
>>> <hierarchy>
>>> <properties>
>>> <hierarchy.name>Hierarchy Name</hierarchy.name>
>>> </properties>
>>> <nodes>
>>> <hierarchy.node ID="123" version="1000">
>>> <node.name>Node Name</node.name>
>>> <payload>
>>> <topic.order>1</topic.order>
>>> </payload>
>>> <nodes>
>>> ...
>>> </nodes>
>>> </hierarchy.node>
>>> </nodes>
>>> </hierarchy>
>>>
>>> Thank you.
>>>
>>> Best regards,
>>> Oleksandr Mandryk
>>>
>>> On Monday, February 20, 2017 at 10:44:14 PM UTC+1, Holger Knublauch
>>> wrote:
>>>>
>>>> Yes Java is a supported option. In your case it could be a SPARQL
>>>> function that returns a string based on the current query graph.
>>>>
>>>> However, in what language would you like to implement such a capability
>>>> if you had the choice?
>>>>
>>>> Holger
>>>>
>>>>
>>>> On 21/02/2017 2:01, Oleksandr Mandryk wrote:
>>>>
>>>> Hi All,
>>>>
>>>> Could you tell me please what is the most appropriate way to add the
>>>> possibility
>>>> to export taxonomy to the custom format in addition to JSON-LD,
>>>> N-Triples, RDF/XML, Turtle.
>>>>
>>>> I think it will be pretty hard to implement such export service using
>>>> SWP or SPARQLMotion.
>>>>
>>>> So I'm considering creation of a new Java servlet, build it to the JAR
>>>> file and integrate it to EVN
>>>> by uploading this jar to tomcat and changing web.xml.
>>>>
>>>> Is it a good idea or there are any better options?
>>>>
>>>> Thank you!
>>>>
>>>> Best regards,
>>>> Oleksandr Mandryk
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Group "TopBraid Suite Users", the topics of which include the TopBraid
>>>> Suite family of products and its base technologies such as SPARQLMotion,
>>>> SPARQL Web Pages and SPIN.
>>>> To post to this group, send email to [email protected]
>>>> ---
>>>> 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/d/optout.
>>>>
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google Group
>>> "TopBraid Suite Users", the topics of which include the TopBraid Suite
>>> family of products and its base technologies such as SPARQLMotion, SPARQL
>>> Web Pages and SPIN.
>>> To post to this group, send email to [email protected]
>>> ---
>>> 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/d/optout.
>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Group
>> "TopBraid Suite Users", the topics of which include the TopBraid Suite
>> family of products and its base technologies such as SPARQLMotion, SPARQL
>> Web Pages and SPIN.
>> To post to this group, send email to [email protected]
>> ---
>> 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/d/optout.
>>
>>
>>
--
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/d/optout.
