Re: ToRDF always puts Description around anon nodes; never typednodes

Presumably this is a choice -- the output makes sense and
correctly encodes the data but just isn't
rdf as she is spoken normally.

The output scares me too, because I have not been able
to find an intellectually satisfying API for the generator.

I had a look at it yesterday and decided it should be low
priority but if it used to work, or is actually incorrect, I'll fix it
before other things.

Tim

----- Original Message ----- 
From: "Dan Connolly" <connolly@w3.org>
To: "Tim Berners-Lee" <timbl@w3.org>
Cc: <www-archive+n3bugs@w3.org>; <connolly@w3.org>
Sent: Monday, January 21, 2002 6:03 PM
Subject: ToRDF always puts Description around anon nodes; never typednodes


> I here's the testcase in full:
> 
> --8<--
> @prefix ex: <http://example/vocab#>.
> [ a ex:Foo].
> 
> 
> # test with: python ../cwm.py typednode.n3 --rdf
> # you should get a typednode in the RDF output,
> # i.e. not a Description element.
> # as of 21Jan2002, you get Description. bug.
> --8<--
> 
> checked in as swap/test/typednode.n3
> 
> The problem seems to come from recent
> changes to notation3.ToRDF.startAnonymous, but the code
> around there scares me... I couldn't find
> a fix.
> 
> -- 
> Dan Connolly, W3C http://www.w3.org/People/Connolly/
> 
>

Received on Tuesday, 22 January 2002 09:31:48 UTC