ToRDF always puts Description around anon nodes; never typednodes

I here's the testcase in full:

@prefix ex: <http://example/vocab#>.
[ a ex:Foo].

# test with: python ../ 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.

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

Received on Monday, 21 January 2002 18:03:50 UTC