Hi, First of all, the SMW architecture changes sound great. I can't wait to try out the triple store connection, I might even try it with Open Virtuoso.
Related to that, I have a student who wants to work on the topic "Using wiki technology for browsing linked data". Our basic idea is it to resolve and to follow-your-nose-browse URIs using SMW (similar to but more general than Shortipedia). For that, we would try to use vocabulary/RDF import functionalities of SMW (thus, also related to RDFIO), e.g., equivalentURI to represent URIs on the web. Therefore, my two questions: * Do the architecture changes also include import functionalities? * Are there specific architecture changes that we might find useful? Best, Benedikt -- AIFB, Karlsruhe Institute of Technology (KIT) Phone: +49 721 608-47946 Email: benedikt.kaemp...@kit.edu Web: http://www.aifb.kit.edu/web/Hauptseite/en -----Original Message----- From: Markus Krötzsch [mailto:mar...@semantic-mediawiki.org] Sent: Tuesday, March 29, 2011 10:16 AM To: Samuel Lampa Cc: Benedikt Kaempgen; smw dev list Subject: Re: [SMW-devel] RDF Import On 28/03/11 22:42, Samuel Lampa wrote: <snip> > Generally, I feel that RDFIO really would be helped by some thorough > refactoring. If I get the time and strength one of these days, I might > give this a go (I'll have to do something, at least before, or in the > summer, due to other projects I'm involved in, which needs RDFIO), but > since this is a bit into the future, feel free to go on make patches or > commits (and feel free to ping me by email to keep me updated on the > thinking behind them :))! > > Hope this info helps, and hope to pay a bit more attentionn to RDFIO soon! Related note: SMW 1.6 will bring a number of related changes that are needed for better RDF store support. On the one hand, SMW will then provide internal functions that RDFIO might find useful (e.g. mapping URIs and literals to SMW data objects), on the other hand, SMW will have a number of internal changes that will require compatibility updates in many extensions (I will update this list about these things as soon as they are more definite). Regards, Markus > >> Best, >> >> Benedikt >> >> -- >> Karlsruhe Institute of Technology (KIT) >> Institute of Applied Informatics and Formal Description Methods (AIFB) >> >> Benedikt Kämpgen >> Research Associate >> >> Kaiserstraße 12 >> Building 11.40 >> 76131 Karlsruhe, Germany >> >> Phone: +49 721 608-47946 (!new since 1 January 2011!) >> Fax: +49 721 608-46580 (!new since 1 January 2011!) >> Email: benedikt.kaemp...@kit.edu >> Web: http://www.kit.edu/ >> >> KIT - University of the State of Baden-Wuerttemberg and >> National Research Center of the Helmholtz Association >> >> >> -----Original Message----- >> From: Markus Krötzsch [mailto:mar...@semantic-mediawiki.org] >> Sent: Wednesday, February 09, 2011 1:11 PM >> To: Samuel Lampa >> Cc: semediawiki-devel@lists.sourceforge.net>> SMW developer list >> Subject: Re: [SMW-devel] RDF Import >> >> On 07/02/2011 21:33, Samuel Lampa wrote: >>> On 02/07/2011 10:20 PM, Samuel Lampa wrote: >>>> I'm sure far from everything is perfectly thought out in RDFIO, but >>>> maybe it can be a useful starting point work for similar things like >> this. >>> >>> Thinking aloud now: .... Maybe, as much as there has recently been >>> discussions about merging efforts to provide a more generalized/ >>> integrated SPARQL/RDF store functionality [1], it might be a good time >>> to think also about a more generalized/integrated RDF/OWL import >>> functionality too? >> >> I agree, and the former is really a prerequisite of the latter. Ideally, >> SMW could thus obtain access to external Linked Data (cached locally for >> query answering). Ways of dynamically locating and pulling such data >> have already been explored in the SMW-based ShortiPedia prototype >> (shortipedia.org). >> >> In any case (to answer Benedikt's initial email), the old vocabulary >> import functionality and the equivalent URI method both affect the RDF >> export only, and do not contribute to the data as viewed in SMW (e.g. >> via queries). This whole aspect of SMW needs to be rethought. >> >> Markus >> >> >> ---------------------------------------------------------------------------- >> -- >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Semediawiki-devel mailing list >> Semediawiki-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel >> >> >> >> ---------------------------------------------------------------------------- -- >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> >> >> >> _______________________________________________ >> Semediawiki-devel mailing list >> Semediawiki-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > >
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
