Holger, Here's the error message I receive (I'm using Postman to send the web service request)
Cannot evaluate Script:org.topbraid.core.servlet.HttpErrorException: Failed service request /qudt_owl_schema/qudt/TurtleSnippet/URI/ http://qudt.org/schema/qudt/Unit: TypeError: (intermediate value).serializeRDF is not a function I have attached a json file containing the results of the owl:imports query you suggested. You will see I added a few extra EDG graphs in the hope of bringing in io.serializeRDF. I don't see any dash graph, except for the GraphQL one. Finally, I also just did a recursive search of my workspace to see if I could find any occurrence of "serializeRDF" that yielded zero hits. Where does the function definition reside? Steve On Thu, Jun 23, 2022 at 7:05 PM Holger Knublauch <[email protected]> wrote: > > On 2022-06-24 12:36 am, Steve Ray wrote: > > Hi, > I have until recently been successfully using IO.serializeRDF in a > dash:ResourceService. I'm running TBC-ME 7.0 for reasons I will explain > below. > However, I'm now getting an error message when I call it. My current > hypothesis: > 1. The EDG collection that contains my code used to also include a graph > "DASH Data Shapes Vocabulary", but the last time I rebuilt my workspace, > that graph mysteriously no longer appears in the available graphs to > include. Is it possible that IO.serializeRDF is thus not visible? > > To check whether dash is really not imported you could run a query such as > > SELECT DISTINCT ?g { ?x owl:imports ?g } > > in the SPARQL query panel. Under normal circumstances there is always some > subgraph in your EDG graphs that will owl:import dash. > > Even if not, IO.serializeRDF should be there. I checked that it was > introduced with TB 7.0.0. > > What error message do you get when you invoke it? > > In a possibly related problem, I also no longer see > teamwork.topbraidlive.org in my TBC-ME workspace in versions higher than > 7.0, and my SWP scripts depended on it. Hence, until I figure out how to > adapt, I am stuck running 7.0 for my services. > > Yeah, TBC 7.1 had been further simplified and decoupled from EDG. If > you're a typical TBC user that has used TBC for a long time, there is > really no reason to upgrade to that version. > > For the latest features such as ADS improvements, EDG Studio is a much > better choice as it evolves alongside the EDG product. However that > requires a different license altogether. > > Holger > > > Help, please! > > > Steve > > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/CAGUep87iDuzZ2P1%3DYn05XKDaXAfAZKxz5mv4amsBfOZ%3DRfX1Fw%40mail.gmail.com > <https://groups.google.com/d/msgid/topbraid-users/CAGUep87iDuzZ2P1%3DYn05XKDaXAfAZKxz5mv4amsBfOZ%3DRfX1Fw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/642c2262-9d60-a8d6-91a7-8a50112115e6%40topquadrant.com > <https://groups.google.com/d/msgid/topbraid-users/642c2262-9d60-a8d6-91a7-8a50112115e6%40topquadrant.com?utm_medium=email&utm_source=footer> > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CAGUep87fSTNaJ8vZTcPhJ4s_j%3DAqcLFM0T42ZXbKMVigjLnJgQ%40mail.gmail.com.
export.json
Description: application/json
