request for review: text/mizar
jesse.alama at gmail.com
Fri Jul 1 14:06:21 CEST 2011
Paul Libbrecht wrote:
> - I think you should refer to the RFC template you use, please see
> the mailing list archive
OK, thanks. I'll take a look.
> - I think the change controller should be the association of Mizar
> users', as an institution with an address, and not the name of a
> person; an email can complement it for sure!
This wasn't clear to me when I was filling out the form at
Item 13 in the form says
"Person to contact for further information"
with a link to RFC 4288, section 4.9. The Association of Mizar Users is
definitely the best entity to put here. It is in charge of maintaining
the mizar language and its suite of tools, and has, moreover, an email
address (which is what I actually included when I filled out the form).
I named Adam Naumowicz, a long-time member of the Association of Mizar
Users and one of the core developers of Mizar, only because I was
literally interpreting the request of the form. In fact, when I came to
this part of the form, I was puzzled, so I asked Adam which of the core
developers of Mizar (i.e., which person) would be suitable, he named a
few candidates (he listed himself), so I put him down.
> - type and subtypes are commonly lowercase... why not continue so?
You're right that they should be lowercase ("text", "mizar"). This
again is a consequence of the form
You can see for yourself that "Text" is one of the options, not "text".
I suppose I put down "Mizar" just for the sake of parallelism, but in
any case it should be "mizar".
> - 8bit... is there a charset there?
I'm not sure I understand; can you say more? Valid mizar texts, these
days, are pure ASCII, but they weren't always so and there's no
guarantee that they will always be so. I put down 8-bit just to be on
the safe side. Perhaps I'm getting something wrong here; let me know.
> - can the specification be indicated with a publicly accessible URL?
One candidate might be
which gives some information about the language. Adam, do you have a
better suggestion here?
> - and finally the personal suggestion: I know Mizar is intended to be
> manipulated by text editors. Could you add two lines in the
> additional information that say something such as: - Window clipboard
> flavor: "Mizar" - Macintosh Uniform Type Identifier: "org.mizar"
> conforms to "public.text" this way applications can offer fragments
> in multiple formats on the clipboard, one of them, say, being RTF and
> the other Mizar, for different objectives.
Nice spot. Your suggestions look fine to me.
More information about the Ietf-types