Page MenuHomePhabricator

[RDFIO] Feature request: Ability to create and modify template calls via RDFIO.
Closed, InvalidPublic

Description

Author: joel.sachs

Description:
Since most SMW is stored via templates, perhaps RDFIO should be able to create and modify template calls based on the triples it is importing. There was some conversation between Yaron and Samuel about this in October 2013 [1]. A lot of assumptions would probably need to be made about the schema of the imported data to make this work effectively.

  1. http://sourceforge.net/p/semediawiki/mailman/message/31549620/

Version: unspecified
Severity: normal

Details

Reference
bz61999

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 22 2014, 3:00 AM
bzimport set Reference to bz61999.

samuel.lampa wrote:

Hi. I think this mail best describes the thinking so far on how to implement this: http://sourceforge.net/p/semediawiki/mailman/message/31553790/

Quoting the relevant part: "... think it is possible to implement, especially for RDF data where entities are linked to an OWL class. Then one can check up which
template is linked from the category page equivalent to that OWL class,
and use that to add facts."

So, given an OWL class, we can get the relevant Category, and from that, the relevant template, which should be what is needed to pattern match and update, a template call filled with data, in a wiki page.

samuel.lampa wrote:

And for pages that already have template calls, we can actually just look up those template definitions, to see which of the fields are controlling a fact that corresponds to any of the RDF triples for the current page.

This will of course require a little bit of clever parsing of the template definition, but it should by all means be possible.

For templates that itself use a lot of template calls, I think there is a way to get a wiki article (the template article in this case) with all subsequent template calls expanded ... which should in most cases be enough to get the mapping between template fields and the SMW properties used.

zahara_ego wrote:

Further to Yaron's comment on visualisation, and Samuel's regarding users who are not very familiar with the technology, I'm thinking along the lines of displaying a simplified entity diagram so that the user can confirm the import is what they want. Default template matching can be done on the basis of the entity types, and where this is incorrect or the RDF schema is unknown, the user can match items and relationships to templates from a list.

Zahara is proposing this OPW project:

Visual Import and Template Matching for RDFIO
https://www.mediawiki.org/wiki/User:Zahara/OPW_Proposal_Round_8

Are there mentors available for this project?

zahara_ego wrote:

I've been in touch with Joel & Samuel regarding this - currently drafting my proposal.

joel.sachs wrote:

(In reply to Quim Gil from comment #4)

Zahara is proposing this OPW project:

Visual Import and Template Matching for RDFIO
https://www.mediawiki.org/wiki/User:Zahara/OPW_Proposal_Round_8

Are there mentors available for this project?

Hi Quim,

Both Samuel and I are happy to mentor this project - we think it could result in SMW instances being much more active participants in the ecology of the semantic web.

Alright, then please step in as official mentors in Google Melange. Instructions: https://www.mediawiki.org/wiki/Mentorship_programs/Possible_mentors

FOSS OPW round 8 has finished. zahara aka Ali King wrote these reports:

https://www.mediawiki.org/wiki/Extension:RDFIO/Template_matching_for_RDFIO/Reports

However, it is unclear to me whether the project has been completed, and in any case the required final blog post seems to be missing.

Please wrap up your project properly, documenting what was done and what was left pending, if anything.

Liuxinyu970226 renamed this task from [RDF] Feature request: Ability to create and modify template calls via RDFIO. to [RDFIO] Feature request: Ability to create and modify template calls via RDFIO..Sep 17 2018, 2:16 PM
Liuxinyu970226 added a subscriber: Denny.
Peachey88 subscribed.

Closing as invalid, as extension tracks issues upstream at GitHub and OPW project was never wrapped up.