- From: Boris Villazon-Terrazas <bvillazon@fi.upm.es>
- Date: Wed, 7 Mar 2012 02:06:16 +0100
- To: Richard Cyganiak <richard@cyganiak.de>
- Cc: Public-Rdb2rdf-Wg RDB2RDF <public-rdb2rdf-wg@w3.org>
- Message-Id: <73C6F6B6-F44C-4C95-87F5-27C48A706CB4@fi.upm.es>
Hi Richard On Mar 6, 2012, at 2:05 PM, Richard Cyganiak wrote: > On 6 Mar 2012, at 11:36, Boris Villazon-Terrazas wrote: >>>> so, the resultant object would be an IRI ? >>>> <data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg==> >>> >>> Yes. >> >> In order to generate the html doc [1], I'm using NxParser [2] for parsing the output files (nq files), and currently it has some problems parsing that URIs. I'll look for a work around. It seems to be there is a new version of the parser [3]. > > FWIW, here's the spec for data URLs: > http://www.ietf.org/rfc/rfc2397 > > If NxParser doesn't accept it, then that's a bug and should be reported to the authors. > > As I said, this data URL works in every modern web browser, so it isn't some exotic fringe syntax either. It was me …. there is no problem with NxParser … everything is ok now. The TC is available at http://www.w3.org/2001/sw/rdb2rdf/test-cases/#R2RMLTC0016e Thanks Boris > > Best, > Richard > > > >> >> Boris >> >> [1] http://www.w3.org/2001/sw/rdb2rdf/wiki/TestCases >> [2] http://sw.deri.org/2006/08/nxparser/ >> [3] http://code.google.com/p/nxparser/ >> >> >> >>> Richard >>> >>> >>> >>> >>> >>>> >>>> Best >>>> >>>> Boris >>>> >>>> [1] http://www.w3.org/2001/sw/rdb2rdf/test-cases/#R2RMLTC0016e >>>> >>>> >>>>> >>>>> Best, >>>>> Richard >>>>> >>>>> [1] http://en.wikipedia.org/wiki/Data_URI_scheme >>>> >>> >>> >> > >
Received on Wednesday, 7 March 2012 01:06:43 UTC