From: Benedikt Kaempgen <firstname.lastname@example.org>
To: don undeen <email@example.com>; smw dev list <firstname.lastname@example.org>
Sent: Tue, December 7, 2010 2:57:21 PM
Subject: RE: [SMW-devel] RDFExport : rendering wikitext
I think, configuring the rdf export to transform content is not possible and
also not its intended purpose. Maybe there is a one-to-one mapping of wiki
syntax to html implemented in a script, somewhere? If so, you could use it
to do the transformation after the export.
Karlsruhe Institute of Technology (KIT)
Institute of Applied Informatics and Formal Description Methods (AIFB)
76131 Karlsruhe, Germany
Phone: +49 721 608-7946
Fax: +49 721 608-6580
Email: email@example.comWeb: http://www.kit.edu/
KIT – University of the State of Baden-Wuerttemberg and
National Research Center of the Helmholtz
From: don undeen [mailto:firstname.lastname@example.org
Sent: Thursday, December 02, 2010 6:22 PM
To: smw dev list
Subject: [SMW-devel] RDFExport : rendering wikitext
I'm working with the RDF export feature, so I can deliver wiki data to 3rd
For example, I've got an essay page, which has content that's contained in
the Text-type property "hasTextContentLeft"
, "hasTextContentMain", etc
So I was using the RDF Export feature to extract that data from a page.
However, in this essay content, the user may have done any of the formatting
stuff that one might do with the WYSIWYG editor. For example, adding
''this'' to make a word italicized.
When the RDF exporter delivers this data, it returns ''this'' . However,
it's a lot easier on my 3rd party app if it
only has to worry about
rendering HTML, not wiki text.
I'm wondering if there's a way to get the rdf exporter to return <i>this</i>
instead of ''this'' ?
I'm happy to write some sort of proxy that gets the RDF, then runs the
individual elements through the parser. But I'd like to reduce the amount of
overhead, and avoid any extra http calls to the MW api page.
What would be the best way to approach this?