Lists Home |
Date Index |
- From: "Rick Jelliffe" <email@example.com>
- To: <firstname.lastname@example.org>
- Date: Mon, 1 Dec 1997 17:03:00 +1100
> From: Peter Murray-Rust <email@example.com>
> XML(SGML) entities (NOTATION) have traditionally used PUBLIC and FPIs
> (Formal Public Identifier) for adding type information. This works if there
> is a registry of FPIs for this purpose. Without it is not much use.
(Peter Flynn had such a registry of FPIs this year.)
> impression - and I'm happy to be corrected - is that there are few useful
> FPIs for Typing objects.
> As yet, MIME is not part of the XLL mechanism. I wish it was, and keep
> squeaking for it. If it isn't I suggest we use XDEV:MIME as a FUA
> 'frequently used attribute' in XML-LINKs.
You can make up your own FPIs *now* for all MIME types using the following
PUBLIC "+//IDN ds.internic.net/rfc/rfc2046.txt//NOTATION
Multipurpose Internet Mail Extensions::video/mpeg//EN">
The important thing about an FPI is that it does not have to be syntactically
correct to work, unlike a system identifier. OF course, getting an agreed
on form will be best.
It is interesting to note that I found it very difficult to find the
official site for the RFC. There is nothing I could find at IETF, IANA,
Internet Sosiety, and searching on websites did not help. For people
in this situation, they can use FPIs with, for example:
PUBLIC "+//IETF RFC 2046::Multipurpose Internet Mail Extensions//NOTATION
FPIs are a great idea because they do not have to correspond to
anything in a fixed location: they can be descriptive.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)