> > ...should collapse all whitespace (including newlines) into a single > space? Exactly what I meant to say. If you can provide links to other examples that have different escape > characters, that would probably help. I don't go through everything, I just encountered some when looking around. But the ones I have encountred are: http://schema.org/WebPage, http://schema.org/CreativeWork, http://schema.org/Person, http://schema.org/Review, http://schema.org/LocalBusiness On Fri, Apr 4, 2014 at 5:12 PM, Dan Scott <dan@coffeecode.net> wrote: > On Fri, Apr 04, 2014 at 04:52:04PM +0200, Jarno van Driel wrote: > >> First off, great news, the new format adds a lot of value. Especially the >> reversed order of Types makes for less scrolling. >> >> Now as for the bugs, the JSON-LD examples seem to be full of escape >> characters (\) and newlines (\n). I guess something went wrong when >> converting. >> > > So for an example, http://schema.org/MedicalScholarlyArticle has an > embedded > newline in the top-level "name" element. That's valid JSON, but I > guess you're suggesting that that newline is an artifact of the > microdata version having line-wrapped strictly for formatting purposes > and that the automated conversion to JSON-LD should collapse all > whitespace (including newlines) into a single space? > > If you can provide links to other examples that have different escape > characters, that would probably help. >
Received on Friday, 4 April 2014 15:22:08 UTC