- From: McBride, Brian <bwm@hplb.hpl.hp.com>
- Date: Sun, 4 Feb 2001 11:45:17 -0000
- To: "'Jonathan Borden'" <jborden@mediaone.net>
- Cc: RDF interest group <www-rdf-interest@w3.org>
Hi Jonathon,
I wish I better understood the relationship between RDF and
other XML languages like XLink and XPointer. Some more
homework for me I think.
> -----Original Message-----
> From: Jonathan Borden [mailto:jborden@mediaone.net]
> Sent: 04 February 2001 01:09
> To: McBride, Brian; 'Graham Klyne'; Dave Beckett
> Cc: RDF interest group
> Subject: RE: Containers
>
>
> Brian McBride wrote:
>
> >
> > I'm not sure what it would mean for a seq or an alt to have
> > an explicit rdfx:member property e.g.:
> >
> > <rdf:Seq>
> > <rdfx:member>foo</rdfx:member>
> > </rdf:Seq>
> >
> > Where in the sequence does this foo come?
>
> May I suggest that XPointer with its ChildSeq construction
> http://www.w3.org/TR/xptr#child-seqs has a good general
> solution to the
> container problem, e.g.:
>
> <rdf:Seq rdf:ID="foo">
> <rdfx:member>bar</rdfx:member>
> <rdfx:member>baz</rdfx:member>
> </rdf:Seq>
>
> can be addressed as:
>
> #foo/1
> #foo/2
If there was an RDF graph representation of the above,
e.g. in statement form:
{ (foo, rdf:type, rdf:Seq),
(foo, rdfx:member, "bar"),
(foo, rdfx:member, "baz")
}
an application which wanted to convert this to RDF XML
wouldn't know in which order to write the
members. Something more is needed to capture the
ordering in the graph.
Do you agree?
Brian
Received on Sunday, 4 February 2001 06:45:25 UTC