W3C home > Mailing lists > Public > public-html-data-tf@w3.org > December 2011

Re: ANN: Multi-syntax Markup Translator: http://rdf-translator.appspot.com/

From: Alex Stolz <alex.stolz@ebusiness-unibw.org>
Date: Wed, 28 Dec 2011 10:08:46 +0100
Cc: KANZAKI Masahide <mkanzaki@gmail.com>, Martin Hepp <martin.hepp@ebusiness-unibw.org>, public-lod@w3.org, HTML Data Task Force WG <public-html-data-tf@w3.org>
Message-Id: <D365B7C3-8639-4D32-B695-747ED5CC2845@ebusiness-unibw.org>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Hi,

On Dec 27, 2011, at 8:12 PM, Melvin Carvalho wrote:

> On 6 November 2011 20:04, Alex Stolz <alex.stolz@ebusiness-unibw.org> wrote:
>> Hello,
>> 
>> thanks for your issue report, Masahide. We fixed it, i.e. the converter is now able to handle UTF-8 characters properly.
>> An additional feature that we've been working on and could be of general interest is the integration of the RDF2RDFa and RDF2Microdata services that allow us to convert from any input format to RDFa or Microdata (still work in progress). E.g. it is now possible to go from RDF/JSON to RDFa.
>> 
>> Thanks to Martin Hepp and Andreas Radinger for valuable feedback and substantial contributions to this project!
> 
> Do you know if there's any way to turn on the CORS headers?

Yes, it is possible as per http://enable-cors.org/#how-gae. I enabled CORS headers now for all API requests, be it with "html=1"-parameter (pygmentized output with Content-type="text/html") or without (raw output using the most appropriate media type for each format). You can check it at http://enable-cors.org/#check.

Alex

> 
> 
> $.getJSON('http://rdf-translator.appspot.com/parse?of=rdf-json&url=http://bblfish.net/people/henry/card',
> function (data) { alert(JSON.stringify(data)) } )
> 
> gives
> 
> XMLHttpRequest cannot load ... is not allowed by Access-Control-Allow-Origin.
> 
> e.g.
> 
> Access-Control-Allow-Origin: *
> 
> http://www.w3.org/wiki/CORS_Enabled
> 
>> 
>> Best,
>> Alex
>> 
>> 
>> On Nov 4, 2011, at 3:39 AM, KANZAKI Masahide wrote:
>> 
>>> Hello, thank you for introducing useful tool.
>>> 
>>> It would be much nicer if the translator could handle non-ascii
>>> characters properly. (we got \u escaped string in JSON outputs, but
>>> garbage in other formats. It'd be better if can have non-escaped value
>>> in JSON as well).
>>> 
>>> cheers,
>>> 
>>> 2011/11/4 Martin Hepp <martin.hepp@ebusiness-unibw.org>:
>>>> (Apologies for cross-posting)
>>>> 
>>>> Dear all:
>>>> 
>>>> Alex Stolz, a PhD student in our group, has just released a nice multi-syntax data translation tool
>>>> 
>>>>    http://rdf-translator.appspot.com/
>>>> 
>>>> that can translate between
>>>> 
>>>> * RDFa,
>>>> * Microdata,
>>>> * RDF/XML,
>>>> * Turtle,
>>>> * NTriples,
>>>> * Trix, and
>>>> * JSON.
>>>> 
>>>> This service is built on top of RDFLib 3.1.0. For the translation between microdata and the other file formats it is using Ed Summers' microdata plugin and for RDF/JSON the plugin as available in the RDFLib add-on package RDFExtras.
>>>> 
>>>> The source code of this tool is available under a LPGL license.
>>>> 
>>> 
>>> 
>>> --
>>> @prefix : <http://www.kanzaki.com/ns/sig#> . <> :from [:name
>>> "KANZAKI Masahide"; :nick "masaka"; :email "mkanzaki@gmail.com"].
>> 
>> Alex Stolz
>> E-Business & Web Science Research Group
>> Universität der Bundeswehr München
>> 
>> e-mail:  alex.stolz@ebusiness-unibw.org
>> phone:   +49-(0)89-6004-4277
>> fax:     +49-(0)89-6004-4620
>> skype:   stalsoft.com
>> 
>> 
>> 

Alex Stolz
E-Business & Web Science Research Group
Universität der Bundeswehr München

e-mail:  alex.stolz@ebusiness-unibw.org
phone:   +49-(0)89-6004-4277
fax:     +49-(0)89-6004-4620
skype:   stalsoft.com
Received on Wednesday, 28 December 2011 09:09:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 December 2011 09:09:29 GMT