[10730] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: About URNs and Meta content

daemon@ATHENA.MIT.EDU (Andrew Daviel)
Thu Mar 20 20:09:15 1997

Date: Thu, 20 Mar 1997 17:02:23 -0800 (PST)
From: Andrew Daviel <andrew@andrew.triumf.ca>
Reply-To: advax@triumf.ca
To: didier ph martin <dmartin@cedep.com>
Cc: W3 org <www-talk@w3.org>
In-Reply-To: <199703200335.WAA08674@octave.collegeleboeuf.qc.ca>
Resent-From: www-talk@w3.org

On Wed, 19 Mar 1997, didier ph martin wrote:

> typing for Meta Content (also called profiles). We came with a new spec
> which is located at http://www.netfolder.com/SDK/index.htm.

Re.   MCF embedded into a HTML file, since DC is settling on
  <meta name="DC.creator"  content="Conan Doyle">
(with some wrangling about where to put SCHEME) 
and we already have well-established
  <meta name="description" content="detective stories">
I thought perhaps one might use e.g.
   <meta name="MCF.authorIndividual"  content="Conan Doyle">
In the comment version (waiting on new tags), it's hard to see how
to parse the MCF distinct from random comments, JavaScript, etc.


In the mail-header version there's nothing to identify the
X-info as MCF, to distinguish it from all the other stuff like
X-Mailer, X-Comment, X-Face, X-Report-Type etc. that turns up in my 
mailbox.  How about  X-MCF.TocOf  etc. ?

Re. http transport; correspondance I have had from Roy Fielding suggests 
that one shouldn't invent arbitrary random HTTP headers; the 
"X-" convention is undefined in RFC 2068.


Meanwhile, some DC people say they're going to move to PICS or XML
in a year or two, and I thought I was confused enough already ... :-}

Andrew Daviel
TRIUMF/Vancouver Webpages


home help back first fref pref prev next nref lref last post