- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Tue, 17 May 2005 15:32:06 +0200
- To: "public-rdf-in-xhtml-tf.w3.org" <public-rdf-in-xhtml-tf@w3.org>
Still trying to get some movement, here is a list of some suggestions for solutions: 1) Two new attributes to represent subject and object when they are bnodes, such as <link some="a" rel="foaf:mbox" href="xxx" /> <link some="b" rel="foaf:mbox" href="yyy" /> <link some="a" rel="foaf:knows" other="b" /> Disadvantage: relatively large amount of infrastructure for a rare case.o do. Advantage: quick t 2) A new URL scheme. <link about="unknown:a" rel="foaf:mbox" href="xxx" /> <link about="unknown:b" rel="foaf:mbox" href="yyy" /> <link about="unknown:a" rel="foaf:knows" href="unknown:b" /> Advantage: works now (ie trying to dereference would give you an error); uses existing attributes. Disadvantage: slow IETF process to register 3) A new XPointer scheme <link about="#unknown(a)" rel="foaf:mbox" href="xxx" /> <link about="#unknown(b)" rel="foaf:mbox" href="yyy" /> <link about="#unknown(a)" rel="foaf:knows" href="#unknown(b)" /> Advantage: uses existing attibutes; W3C process to register. Disadvantage: have to write the spec 4) Some trick using undefined id's, maybe <link about="#_a" rel="foaf:mbox" href="xxx" /> <link about="#_b" rel="foaf:mbox" href="yyy" /> <link about="#_a" rel="foaf:knows" href="#_b" /> Advantage: existing attributes; quick Disadvantage: fragile 5) Use some illegal form of URLs when representing bnodes: <link about="##a" rel="foaf:mbox" href="xxx" /> <link about="##b" rel="foaf:mbox" href="yyy" /> <link about="##a" rel="foaf:knows" href="##b" /> Advantage: may work now. Disadvantage: validation. Any more? Steven
Received on Tuesday, 17 May 2005 13:37:15 UTC