 |
 |
> From [log in to unmask] Thu Oct 18 13:18 MET 2001 > X-Meta: <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns:dc="http://purl.org/dc/elements/1.1/"> <rdf:Description about=""> > <dc:publisher> UKOLN > MIME-Version: 1.0 > Date: Thu, 18 Oct 2001 12:08:27 +0100 > From: Andy Powell <[log in to unmask]> > Subject: Re: DC-ARCHITECTURE Digest - 16 Oct 2001 to 17 Oct 2001 (#2001-55 > ) > To: [log in to unmask] > > On Thu, 18 Oct 2001, Thomas Baker wrote: > > > On Thu, 18 Oct 2001, Dan Brickley wrote: > > > > All of this could be done using hard-coded URLs :-( or via appropriate > > > > links to the registry :-). RDDL looks, to me, like a good candidate > > > > language for providing these linkages. Otherwise, how is someone going to > > > > get from the namespace URI to the registry? > > > > > > How about brief human-readble 'welcome and table of contents' in XHTML > > > with the RDF Schema embedded in-line, alongside RDDL serving as a > > > machine-friendly table of contents pointing off to all the other goodies? > > I'm not clear what you mean by 'alongside' here. We only have one URI, > the namespace URI, so we can only point at one thing. Does the namespace > URI resolve to the XHTML which points at the RDDL or does the namespace > URI resolve to the RDDL which points at the XHTML? A resource can point to itself - that's definitely not the problem. We can provide metadata about ourselves. We quite often do. rs > > > Could those goodies include translations? Rachel alluded to problems in > > implementing this. > > Then handle the complexity in the registry and use RDDL (or whatever we > decide to put at the namespace URI) to point to appropriate places in the > registry? > > Andy > -- > Distributed Systems and Services > UKOLN, University of Bath, Bath, BA2 7AY, UK [log in to unmask] > http://www.ukoln.ac.uk/ukoln/staff/a.powell Voice: +44 1225 323933 > Resource Discovery Network http://www.rdn.ac.uk/ Fax: +44 1225 826838 >