-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kirkham, Pete (UK) wrote: | |>Three triples |> | | |>_:a rdf:type r1:date . |>_:a xxx:transform eg:r2-to-r1.xsl . |>_:a rdf:value "4th June 2004" . |> | | |>We might expect xxx:transform to have semantics along the lines of |> | | |>"the object of this statement is an XSLT transform that when | | |>applied to the subject serialized in such-and-such a way gives | | |>additional triples that are also true." | | | Which is where the problem is- you want | _:a rdf:type r1:date . | _:a rdf:value "2004-06-04" . | | but after the transform you've got | _:a rdf:type r1:date . | _:a rdf:value "4th June 2004" . | _:a rdf:value "2004-06-04" . Ah, I see what you mean. I understood Danny's suggestion to mean that one begins: _:foo ex:date _:a . _:a rdf:type r1:date . _:a rdf:value "2004-06-04" . and gets: _:foo ex:date _:a . _:a rdf:type r1:date . _:a rdf:value "2004-06-04" . _:foo ex:date _:b . _:b rdf:type r2:date . _:b rdf:type "4th June 2004" [which, now I look at it, could be nasty (in the xslt) if _:a is the object in multiple statements.] I guess we need to ask Danny what he meant. Damian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAwISSAyLCB+mTtykRAkIbAJ9J4JWU1S9SmMWen5ZTeJMt73hTdgCg9yav 4HpVs7yhPC4PssEJ0x5uol4= =Y6EL -----END PGP SIGNATURE-----Received on Friday, 4 June 2004 10:22:21 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:50 UTC