Eddy;  Thank you for your detailed feedback.  We will generate a new
version of the tutorial based on these comments within the next day or
so.  There are a few clarification and answers to questions below:

<It is interesting to note the URL's are automatically imported and
converted into prefixes.
If a fill URL remains, there is a typing error.
This might be a feature added afterwards in TB but it is mentioned no
where until now.(except my mistake) >

URIs are converted to qnames whenever a prefix is recognized. See the
Ontology home for the defined prefixes.  In this case, the prefixes
are defined by choosing "Assert new prefixes".  The explanation goes a
bit beyond this tutorial, but we can look into providing a brief
explanation.  There is a brief explanation of qnames at:
  Help Contents > TopBraid Composer > User Interface Overview > Labels
Display Mode

...and more can be found under:
  Help Contents > TopBraid Composer > How to? > Modify namespaces and
prefixes

<For one or another reason, the triples for the predicate capital of
the source file are
generated with the predicate Capital (yes, literally capitalized ;-)).
>

This should be the predicate "capital", not "Capital", unless you
defined a "Capital" predicate instead.

<Page 28, point 14>

Sorry, there is a typo in the tutorial.  Try:
  
http://localhost:8083/tbl/actions?action=sparqlmotion&id=ReturnCapital&arg1=Germany

-- Scott

On Jul 6, 3:11 am, "Eddy Vanderlinden" <[email protected]> wrote:
> Hello,
>
> I tried the exercises on SPARQLMotion and found the tutorial amazingly good !
>
> As it goes, here and there are some typing errors we could report, or 
> suggestions from a novel user's point of view.
> There are here-after. In the hope you can use them to spare time for others 
> in searching.
>
> Again, congratulations, I leaned a lot. Hope we will find more of those.
>
> Page 7, point 4:
> 4. From the Scripts menu, select Create SPARQLMotion
>
> Script. This will prompt you for the first module
>
> Page 13, the construct query:
> CONSTRUCT {?country1 owl:sameAs ?country2}
> WHERE {?country1 ahttp://www.topbraid.org/owl/geo/region#Country.
> ?country1 <http://www.topbraid.org/owl/geo/US-states#postalAbbreviation> 
> ?value.
> ?country2 ahttp://topbraid.org/countries#Country.
> ?country2 <http://topbraid.org/countries#abbreviation> ?value.}
>
> It is interesting to note the URL's are automatically imported and converted 
> into prefixes.
> If a fill URL remains, there is a typing error.
> This might be a feature added afterwards in TB but it is mentioned no where 
> until now.(except my mistake)
>
> Page 18, point 3:
> Click Debug to run the script. Select all check boxes as shown
> in the dialog and click Close.
>
> The dialog shows the option "infer result triples (temporarily) unchecked.
> To obtain the expected results, we have to check the box however.
> Perhaps replace the picture could be an idea ?
>
> Page 21, comments to point 19:
> - those
> we generated (output of SelectDBPediaURI) and those
> that come from the capitals.owl model
> (LoadCountries). Therefore we merge these triples by
>
> Proposition to replace capitals.owl by countries.owl in the text.
>
> Page 22, point 20
> After running the construct, when we look at the "home" page, we can find a 
> warning message stating "Warning: This model currently contains more than one 
> owl:Ontology".
> This is due to a xml:base statement.
> When clicking the link, TB proposes to correct.
> Would it be a good practice to foressee this automatically or as a standard 
> procedure in the tutorial ?
>
> Page 23, point 27
> LET (?namespaceURI := smf:buildURI ("{?namespace}")) .
>
> The additional bracket makes the construct query work.
>
> Page 24, point 9
> WHERE { LET (?namespaceURI := smf:buildURI ("{?namespace}")) .}
>
> The additional bracket makes the construct query work.
>
> Page 26, point 5
> 5. Create an instance of ReturnText (subtype of Export To Remote) and name it 
> ReturnCapital_
> script. Connect CreateResponse to ReturnCapital.
>
> The underscore proposed at the EOF is used further in the exercise.
>
> Page 27, point 11
> 11. The script will take a string as an input (via sp:arg1), query the 
> ontology, and return the result. Enter
> the following query in GetCapital:
>
> SELECT ?capitalLabel
> WHERE {LET (?countryLabel := smf:setLanguage(?arg1, "en"))
> ?country rdfs:label ?countryLabel.
> ?country <http://www.topbraid.org/owl/geo/region#capital> ?capital.
> ?capital rdfs:label ?cap .
> FILTER ( lang(?cap) = "en" )
> LET (?capitalLabel := smf:setLanguage(?cap, ""))}
>
> As mentioned above, the imports follows automatically with a prefix 
> convertion in the statement as a consequence.
> Very happy with that, it makes the statement more readable, but...
> For one or another reason, the triples for the predicate capital of the 
> source file are
> generated with the predicate Capital (yes, literally capitalized ;-)).
>
> We have thus to adjust the automatically converted select statement as 
> follows to make him run:
> SELECT ?capitalLabel
> WHERE {
> LET (?countryLabel := smf:setLanguage(?arg1, "en")) .
> ?country rdfs:label ?countryLabel .
> ?country region:Capital ?capital .
> ?capital rdfs:label ?cap .
> FILTER (lang(?cap) = "en") .
> LET (?capitalLabel := smf:setLanguage(?cap, "")) .
>
> }
>
> This might be a new feature.
>
> Without this adaptation, the script does not return the capital.
>
> Page 28, point 14
>
> The answer in the web-browser on the input request is:
>
> HTTP ERROR: 404
> Not FoundRequestURI=/tbl/servlet
>
> Powered by Jetty://
>
> Should there be anything else to activate ?
>
> Page 29, point 3 in par 6.1
>
> 3. With ImportCountries class selected, drag and drop sparql:constructor 
> property on to the form.
>
> I didn't find a sparql:constructor, but with the spin:constructor, it worked 
> fine.
>
> Suppose this is a rather new feature.
>
> Hope this was of some help for others who try to finish the exercises too.
>
> Kind regards
>
> Eddy Vanderlinden.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to