Re: [Virtuoso-users] content:encoded

Nathan, We're in process of making v6 release so it's probably impractical to make a patch. If v6 is not released during the weekend then I'll make an "unofficial" patch for the issue. Best Regards, Ivan Mikhailov OpenLink Software http://virtuoso.openlinksw.com On Thu, 2010-01-28 at 22:55 +000

Re: [Virtuoso-users] content:encoded

Thanks Ivan :) Any chance of an updated 6 as currently I'm getting the following: http://bit.ly/dueNeF my current build is Version 6.0.1-pre1.3124-pthreads regards & cheers, Nathan Ivan Mikhailov wrote: > Hello Nathan, > > That's the current status of version 5 tree: > > 1. Loading of XML l

Re: [Virtuoso-users] content:encoded

Hello Nathan, That's the current status of version 5 tree: 1. Loading of XML literals in RDF/XML and TTL is correct: -8<- DB.DBA.RDF_LOAD_RDFXML (' http://www.w3.org/1999/xhtml"; xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

Re: [Virtuoso-users] content:encoded

Just a quick chase up from myself as well with regards the following, particularly finding that the lack of serialization support in sparql results is limiting things a bit (can't expose a public sparql endpoint): any word / update / eta? Regards! Nathan wrote: > Hi Ivan, > > I think I explaine

Re: [Virtuoso-users] content:encoded

Hello Nathan, Re.loading: > Option 1: RDF+XML w/ CDATA > Without parseType="Literal" it should become a string. With CDATA it is a string, otherwise it's a RDF/XML structure error or something unexpected, depending on the content of the XML. > Option 2: rdf:XMLLiteral in turtle/n3 >

Re: [Virtuoso-users] content:encoded

Hi Ivan, I think I explained badly in the first place.. when one uploads XML contained in a CDATA section (via PUT to a rdf_sink folder), the XML contained is converted to (and stored as) a string literal, rather than an XMLLiteral. Need to do a bit of explaining here, as I've noted a few issues.

Re: [Virtuoso-users] content:encoded

Hello Nathan, We have a support for CDATA output but first of all, the XML serializer should know that an element should be encoded with CDATA. For an XSLT output, this can be controlled by options of the stylesheet. How was the XML in question generated? What's missing in that path? Best Regards

[Virtuoso-users] content:encoded

Hi All, Slight question about content:encoded (I know it's a bit of a special case). assumption(s): 1 - the following is valid content:encoded 2 - the following is invalid content:encoded

some html.

question / problem virtuoso consumes [1] perfectly, yet returns http://