From: mitra@path.net (Mitra)
Date: Thu, 21 Oct 1993 10:26:38 PST
In-Reply-To: ccoprmm@oit.gatech.edu (Michael Mealling)
To: ccoprmm@oit.gatech.edu
Subject: Re: New URM paper with additions!
Message-Id: <9310211026.aa25721@pandora.sf.ca.us>
Michael
Thanks for taking the critque in the constructive way it was intended,
sorry I forgot that your offer of a "beer" was not prepended by a language
set, so should probably default to en_US:beer as opposed to en_UK:beer
which are substantially different concepts.
Three points.
URL in Meta information: You have concerns that this could break
things. I think the concept of a URL in the Meta information is broken.
Defining URL: as a a IAFA tag is one thing, but it doesnt convey
semantics. The URM definition adds semantics to this. URL's cannot occur
INSIDE URMs in your definition as they have no meaning there.
SGML as an encoding type. If some people want to use SGML for encoding
types, then thats eminently reasonable, but to my mind that is an
alternative encapsulation of the same information. So for a URM you get something
like
<urm>iafa:en_US.isio88591
<author>Michael Mealing</author>
<title>My book</title>
</urm>
As opposed to trying to encode SGML within your format. Since the
information content of the two is identical, translating between an IAFA
context (e.g. a Mime header) and a SGML context (e.g. a Web document) is
trivial. I'm not an SGML expert, so I'm sure those on this list can
comment on whether this is appropriate.
Re High Skool; If we want back compatibility with US high-school term
paper format, then I propose that be an added applicability statement on
the kinds of meta information that should be carried in a citation.
(Note citation as opposed to URC).
- Mitra