Yes, we can, and maybe we will, but doesn't defining a special case
because one form of a general one is used frequently enough run counter
to everything you know about software engineering? :-)
There is the case for generality. I agree it looks horrid.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Well, that should be enough to generate some healthy debate.
Yes. It has brought up the general and important issue of what
to do about metadata, which is useful too.
Here is a final idea. The HTML spec can be user-friendly
as people see it more often than the HTTP. So let the
HTTP have a general relationship field. Then specify an
architectural form (am I kidding?) to allow any DTD to
specify the semantics of a relationship element in terms of the
underlying relationship model.
Tim