Don - to clarify, the information retrieved is not stored automatically; instead, you need to store it using an SMW tag. An example might be:

[[Created by artist::{{#external_value:Artist}}]]

Then you would query on "Created by artist".

Caching is an issue - if the value from the API changes, the value stored semantically won't change until it's refreshed manually, either by calling the refreshData script, or resaving that wiki page, or (if you're using a template) resaving the template.

-Yaron


On Thu, May 28, 2009 at 4:56 AM, Philipp Zaltenbach <zaltenbach@ontoprise.de> wrote:
Hi Don,

I would say using a triple-store as backend instead of the conventional
database backend depends on your scenario.
At ontoprise, we definitely need a triple-store, since it provides
advanced reasoning, e.g. for inverse, transitive and symmetric
properties or even complex rules. We use rules e.g. in our internal
software development wiki for triggering certain actions upon status
changes. Remote querying is also a big plus of a triple store backend,
because it allows you to integrate "live data" from SMW into other
applications.

We provide two triple-store connectors. One for Jena (for free) and one
for Ontobroker (commercial). The manual for the Jena triple-store
connector can be found at
http://smwforum.ontoprise.com/smwforum/index.php/Help:Basic_Triplestore_1.1
The difference between Ontobroker and Jena is that Ontobroker supports
rules and scales much better. You can also integrate other data-sources
via Ontobroker.

Best regards,
Philipp


don undeen schrieb:
> Mostly a question for Yaron, but the broader issue may have more interest.
>
> I was checking out the External Data extension, as it seems it could be very useful to us. We've got data in other stores, that we want to be able to reference from within our wiki.
>
> Let's say, for example, I've got a page, Category:ArtObject, named 1992.45.34. And we've got an relational database (called MST), that tells me that art object was made by "Fabio Ficasso",
>
> Using the External Data extension, I see how I can load the data from our art database, using an API like
> http://ourmuseum.org/api/getObjectData/1992.45.34 , and then parse it onto the page accordingly.
>
> What we're really after, however, is to go one step beyond that. I'd like to be able to write an ASK query on some other page, that queries, say, for pages of category:ArtObject,  which were made by "Fabio Ficasso". So what would need to happen is for that external data to be queried as well.
>
> Put another way, we want to be able to use the wiki itself as our data integration point. Insane? You tell me.
>
> I'm also looking for any halfway measures that anyone can propose. The External Data extension is itself a huge step towards that halfway point; I'm wondering how much farther we can push it.
>
> If I imagined the SMW backend as a literal triple store (instead of a mysql database) supporting remote endpoint queries, I could sort of imagine how the backend to all this could look.
> Judging from this thread:
> http://sourceforge.net/mailarchive/message.php?msg_id=9984a7a70709231041s16e90db9r7a5cfd2848347e85%40mail.gmail.com
>
> It seems people don't think much of the idea of replacing the MW backend with a full-fledged triplestore. Am I right? Performance issues (temporarily) aside, doesn't it seem like a better fit for SMW to sit on a triplestore? Performance issues NOT aside, perhaps not so much?
>
> Are there some other approaches people have taken to encorporating non-wiki data into their wikis?
>
>
> thanks again, for all your time and hard work.
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> Semediawiki-user mailing list
> Semediawiki-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/semediawiki-user
>

--
Philipp Zaltenbach
Professional Services
ontoprise GmbH – know how to use Know-how
- - -
ontoprise presents the new SemanticMiner for SharePoint:
http://www.ontoprise.de/en/home/news/news-en/cebit-2009-ontoprise-presents-the-new-semanticminer-for-sharepoint/
- - -
An der RaumFabrik 29; 76227 Karlsruhe; Germany
phone: +49 721 509809-0; Fax: +49 721 509809-11
mailto:zaltenbach@ontoprise.de, www: http://www.ontoprise.de
Registered office: Karlsruhe, Germany;  Register court: Mannheim, HRB 109540
Managing directors: Prof. Dr. Jürgen Angele, Dipl.Wi.-Ing. Hans-Peter Schnurr
- - -


------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
Semediawiki-user mailing list
Semediawiki-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-user