IANA considerations for PIDF
Graham Klyne <[email protected]>
| Newsgroups | gmane.ietf.impp |
|---|---|
| Message-ID | <[email protected]> |
Here is some proposed PIDF text, as promised.
Note that the namespace URN registration (section 7.2) is based on
http://www.ietf.org/internet-drafts/draft-mealling-iana-xmlns-registry-03.txt,
which I understand is with the RFC-editor. Also note that, to conform with
this registration, the URN name in the rest of the document should be
changed from urn:ietf:params:cpim-presence to urn:ietf:params:xml:ns:cpim-pidf.
Michael: I've noticed the -xmlns- registration template doesn't have space
for a description.
Can you cast your eye over the registration template at 7.2 below to see if
it is
roughly what you intended for this registry. I've populated the XML field
with an XHTML document that (will) reference the specification - I think
that's consistent with your recommendation.
Section 7.3, below, is a place-holder for a status-type registry that I'm
really hoping will go away. If it doesn't then there will be a fair amount
of additional work to do on it.
---
7. IANA Considerations
This memo calls for IANA to:
- register a new MIME content-type application/cpim-pidf+XML, per [RFC
2048],
- register a new XML namespace URN per
[draft-mealling-iana-xmlns-registry-03].
The registration templates for these are below.
It also calls for the creation of a new registry for status type values,
and corresponding URN assignments per [draft-mealling-iana-urn-02]. The
new registry and initial registrations are described at section 7.3 below.
7.1 Content-type registration for application/cpim-pidf+xml
To: [email protected]
Subject: Registration of MIME media type application/cpim-pidf+xml
MIME media type name: application
MIME subtype name: cpim-pidf+xml
Required parameters: (none)
Optional parameters: charset
Indicates the character encoding of enclosed XML. Default is UTF-8.
Encoding considerations:
Uses XML, which can employ 8-bit characters, depending on the
character
encoding used.
See RFC 3023 [x], section 3.2
Security considerations:
This content type is designed to carry presence data, which may
be considered private information. Appropriate precautions should
be adopted to limit disclosure of this information.
Interoperability considerations:
This content type provides a common format for exchange of presence
information across different CPIM compliant protocols.
Published specification:
RFCXXXX (this document)
Applications which use this media type:
Presence and instant messaging systems.
Additional information:
Magic number(s):
File extension(s):
Macintosh File Type Code(s):
Person & email address to contact for further information:
Hiroyasu Sugano
E-mail: [email protected]
Intended usage:
LIMITED USE
Author/Change controller:
This specification is a work item of the IETF IMPP working group,
with mailing list address <[email protected]>.
Other information:
This media type is a specialization of application/xml [RFC 3023],
and many of the considerations described there also apply to
application/cpim-pidf+xml.
7.2 URN sub-namespace registration for urn:ietf:params:xml:ns:cpim-pidf
URI
urn:ietf:params:xml:ns:cpim-pidf
Description:
This is the XML namespace URI for XML elements defined by [RFCXXXX]
to describe CPIM presence information in application/cpim-pidf+xml
content type.
Registrant Contact
IETF, IMPP working group, <[email protected]>
Hiroyasu Sugano, <[email protected]>
XML
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<meta name="generator" content="Adobe GoLive 6"/>
<title>Welcome to Adobe GoLive 6</title>
</head>
<body>
<h1>Namespace for CPIM presence information</h1>
<h2>application/cpim-pidf+xml</h2>
<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
</body>
</html>
END
7.3 Registry for CPIM presence status type codes
[[[Place-holder -- hopefully this will go away.]]]
---
That's my offering.
#g
-------------------
Graham Klyne
<[email protected]>
[reminder: [email protected] for non-technical discussions, please]