working through some SWA/SWP/EDG development I keep finding myself having 
to context-switch between different styles and locations for functions.

For SWP generally, http://uispin.org/ui.html
For SWA - its http://localhost:8083/tbl/swp?_viewClass=swadoc:Index
For teamwork - 
its http://localhost:8083/tbl/swp?_viewClass=teamworkdoc:SPARQLFunctions

then we have functions like smf:userWithName()  - i havent found where 
these are documented at all yet,

then then are SPARQLmotion functions -  these seem mainly available via the 
TBC help system - maybe thats pulling in 
this https://www.topquadrant.com/sparqlmotion/lib.html and restyling it?  
Stiull havent found smf: and spif: yet ...

The guide at  
https://www.topquadrant.com/2010/01/05/how-to-write-new-sparql-functions-with-spin/
  
says "The “TopBraid SPARQLMotion Functions Library” page of TopBraid 
Composer's online help lists ...

but this is sadly not a link ..

There seem to be libraries for spif: and spl: here http://spinrdf.org/spif 
and here http://spinrdf.org/spl#   - but no obvious links to documentation 
- and not finding it by google.

also other namespaces for functions like afn:now()

So, there seem to be at least 7 different libraries of useful stuff.  I 
suspect there are more.

what about magic properties and SPIN templates accessible to EDG developers 
for instance.

Should I favour one over another - can we at least enumerate these in some 
sort of hierarchy of stability and support both within TQ and the wider 
community?

Could perhaps an index of all the non-deprecated functions be published as 
a RDF file - and rendered as HTML where each function is referenced along 
with a link to its appropriate online documentation, and ideally relevant 
guides and tutorials? 


-- 
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.

Reply via email to