 |
 |
IMHO, I'd recommend explicitly coding a "SCHEME" of "URL" for Identifier or Rights. In some environments, you might be working with paper documents, Web documents, a lotus notes database, ad nauseum. In such an environment it would be dangerous to assume that "no specified scheme means the default scheme", since a Notes-based program might prefer the "default" scheme to be specific to a Lotus Notes database, while an Oracle based program might prefer the "default" identifier scheme to simply be a table.field=value. Also, when serving HTML documents with the metadata embedded, it's worth the effort to encode the DC.Identifier and DC.Format, since something that is text/plain at location "ftp://ftp.somewhere.com/thisfile.txt" might end up being served to the client through "http://www.somewhereelse.com/my_page.html", with the metadata embedded after being collected from the document management sytem at somewhere.com. I know, I know... it's a manufactured example, and the HTML format version should have it's own metadata attached indicating DC.Source, etc. I've got a better example. One you can try right now. "File/Save As...", select "Source". Open the file with a text editor. "File/Print". Bingo - if DC.Location had been coded explicitly in the Dublin Core data, you'd know where to look to find the original document. If you wrote the location on the paper, then you've just explicitly coded the DC.Source field, so that doesn't count. Also, in that example, there's no indication on the printout that the electronic document was actually text/html, rather than a sample of HTML coding, stored in a text file, that should be categorised as DC.Format="text/plain". Regards, Alex Satrapa (master of manufactured examples) Andy Powell wrote: > On Thu, 15 Oct 1998, Titia van der Werf wrote: > > Format scheme: > > MIME types: <LINK REL=IMT HREF"ftp://ftp.isi.edu/in-notes/rfc2046.txt"> > > Question... for DC embedded into HTML why recommend embedding a URI using > DC.Identifier and a MIME type using DC.Format at all? The URL is implicit > and the MIME type is typically served by the Web server?? > > > Date: > > <LINK REL=ISO8601 HREF="http://www.w3.org/TR/NOTE-datetime"> > > > > Language: > > <LINK REL=ISO639-1 HREF="ftp://ftp.isi.edu/in-notes/rfc1766.txt"> > > > > Country code (to accompany language code, if necessary) > > <LINK REL=ISO3166 > > HREF="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt"> > > > > For the DC scheme itself, we would like to do something similar, we > > thought of : > > DC : <LINK REL=DC HREF="ftp://ftp.isi.edu/in-notes/rfc2413.txt"> > > > > what would you recommned? > > Are you developing harvesting tools that make use of all these embedded > <LINK REL> tags? > > Andy. > -- > UK Office for Library and Information Networking > University of Bath, Bath, BA2 7AY, UK Voice: +44 1225 323933 > http://www.ukoln.ac.uk/ukoln/staff/a.powell.html Fax: +44 1225 826838