- From: Richard Light <richard@light.demon.co.uk>
- Date: Mon, 4 Jan 2010 12:26:32 +0000
- To: "ZENG, MARCIA" <mzeng@kent.edu>, "iso25964@list.niso.org" <iso25964@list.niso.org>, "nkos-l@oclc.org" <nkos-l@oclc.org>
- Cc: public-lod@w3.org
In message <OoPLKWGZ$nLLFwda@light.demon.co.uk>, Richard Light <richard@light.demon.co.uk> writes >In message ><E5085AA25A4425438F00618C266E0274B89901439E@KENTS-MBX02.KENTS.LOCAL>, >"ZENG, MARCIA" <mzeng@kent.edu> writes >>[Note: The introduction to VMF (The Vocabulary Mapping Framework) is >>available from the link of this page or at: >>http://cdlr.strath.ac.uk/VMF/documents/VocabularyMappingFrameworkIntrod >>uctionV1.0(091212).pdf >>] --mz > >Hi, > >Not finding a handy Turtle parser for my Windows environment, I have >been developing one to read this framework. However, I hit a >road-block around line 59,366 of the complete source, as soon as some >French text appeared in a literal string. Shouldn't the encoding be >UTF-8, as per the Turtle spec [1] ? > >Richard > >[1] http://www.w3.org/TeamSubmission/turtle/ Further to this, I provided an option in my parser to treat the input as having ISO-8859-1 encoding (contrary to the Turtle spec), and have now successfully loaded the statements from VMF into a home-made ModesXML "triple store". However, since Protege loads the VMF as it stands, does this not mean that the Protege Turtle parser is failing to respect the Turtle spec (and thereby propagating bad/incorrect practice)? Richard -- Richard Light
Received on Monday, 4 January 2010 12:27:10 UTC