The options below are currently only useful for tools that do not parse SPIN RDF - it basically means that each SPIN RDF query object also contains a sp:text string with a human-readable (and easy to parse) string. TopBraid's editors do not use these settings yet for editing.
I can see that there is a case in which users want to keep the SPARQL query string exactly like they entered it. However, this may also mean that many of the benefits of the SPIN RDF notation are lost, e.g. queries might become invalid if a resource URI or a prefix have been renamed. Anyway, for 3.0 I have added another boolean option to the SPIN Preferences page. If the "verbatim" mode is activated, the system will use the stored sp:text for the editor fields, and leave the string exactly as entered by the user. The internal engines such as constraint checker will still use the RDF notation, i.e. queries cannot become easily invalid. I hope this addresses your concerns, Tim? Holger On Mar 26, 2009, at 11:32 PM, Pierre wrote: > >> is it possible to store them in "as entered" text form as well as >> SPIN RDF? > > Preferences > TopBraid Composer > SPIN > Also generate sp:text > representation of queries: > x Yes, with prefix declarations (verbose) > o Yes, without prefixes (compact) > > Pierre > > On Mar 27, 4:49 am, "Smith, Tim" <[email protected]> wrote: >> Hmmm... Does that mean storing them twice? >> >> The issue that I'm going to face is that I have dozens of long (50+ >> lines) CONSTRUCT queries with lots of comments. Can I assume I'm >> going >> lose the comments when I move those scripts from 2.6.2 to 3.0? >> >> In my current work, I had a PREFIX statement at the top of the >> CONSTRUCT >> query and pressing OK in the module removed the PREFIX and expanded >> the >> prefix to the full URI in the query text. I don't usually embed >> PREFIX >> statements into the queries in modules but if you do and they get >> replaced and expanded, that will make for a really messy query to >> edit. >> >> I understand the logic of storing them in SPIN RDF but is it >> possible to >> store them in "as entered" text form as well as SPIN RDF? It seems >> that >> the logic is in place to generate the SPIN RDF from the text >> representation already. It would be nice if the GUI could store >> them as >> entered too. >> >> Tim >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Holger >> Knublauch >> Sent: Thursday, March 26, 2009 11:22 PM >> To: [email protected] >> Subject: [tbc-users] Re: SPARQL Comment Support in SM scripts >> >> Hi Tim, >> >> this has been disabled for now (by default) because SPARQLMotion >> modules >> now store the SPARQL queries in SPIN RDF format. This format >> currently >> only supports comments in the beginning of the query, e.g. >> >> # This query is trivial. >> >> # Yes. Really trivial. >> >> ASK WHERE { >> >> } >> >> will be stored OK. All other comments are currently lost because this >> would require some deep magic with the Jena SPARQL parser. >> >> A work-around is to save your queries as strings (that's still >> allowed >> but not encouraged by the UI). This would mean editing those values >> differently, e.g. with the source code editor :( I can think of a >> number >> of UI work-arounds that would always store them as strings if that's >> needed by anyone. >> >> Holger >> >> On Mar 26, 2009, at 7:44 PM, Smith, Tim wrote: >> >> Hi - in TBC 3.0 Beta 2 comments are still deleted when entering >> them in >> SPARQLMotion modules such as CONSTRUCT queries, etc. >> >> Any chance comments will be supported in the final release? It is >> very >> much of a pain to have comments deleted! There is no way to document >> your SPARQL in those modules and all good coders document their >> code... >> J >> >> Thanks, >> >> Tim > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
