[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
Hi Tim,
This is the follow-up to our phone conversation last Friday about
merging the mime-props draft from the calendaring working group with the
mime-dir draft from the asid working group. The two drafts are not that
different, here are the key changes I think we need to make to
encapsulate the thoughts of mime-prop into mime-dir:
1. Add an optional datatype parameter. This will allow an application
to identify and handle data based on it's type. We talked about the
proto parameter being used to specify a way for an application to deal
with the data, so maybe we should collapse the proto paramater into the
datatype parameter. I think we can also collapse "valuetypeparam"
production into a url datatype. We'd also pre-define the data formats,
but not limited to that which we have in the MIME-PROPS draft. See the
suggested grammar below:
parameter := encodingparam / charsetparam
/ languageparam / datatypeparam / [paramtype "="]
paramvalues
datatypeparam := "datatype" "=" datatype
datatype := "text" / "boolean" / "datetime" / "time" / "date" / "float"
/ "long"
/ "binary" / "currency" / "url" / x-datatype /
iana-datatype
2. Efficiency in repeated properties. To increase efficiency, I
propose that we allow properties which have the same name to be repeated
without the name. In this scheme, the repeated property would inherit
the attributes from the previous property. For example:
CN: Frank Arthur
CN: Arthur Frank
CN: Frank
would become
CN: Frank Arthur
:Arthur Frank
:Frank
3. Grouping disjoint profiles. We need to be able to assign a profile
to groups of properties. For example, I am sending a meeting request,
identifying all the attendees and in the same message I am identifying
where the meeting is, what time it's at, etc. We thought about having a
base body part that had URLs to other parts, but that has a lot of
overhead, so instead we were thinking of a construct that looked more
like this, allowing multiple profiles within a single body-part:
begin: meetingdetails
Location; datatype=text: "At the boathose"
Date; datatype=date: 11 Aug 96
Time; datatype=time: 10:30:00
begin: meetingattendee
CN: Frank Arthur
SN: Jones
Status: Required
begin: meetingattendee
CN: James George
SN: Brown
Status: Optional
The grammer would be something like this:
body := section [ body ]
section := "begin" ":" profile CR content
content := contentline CR [ content ]
Thanks,
Alec.
>----------
>From: Internet-Drafts@ietf.org[SMTP:Internet-Drafts@ietf.org]
>Sent: Wednesday, July 31, 1996 6:18 AM
>To: The recipient's address is unknown.
>Cc: ietf-asid@umich.edu
>Subject: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
>
><<File: ATT00714.txt>><<File: draft-ietf-asid-mime-direct-02.txt.url>>
> A Revised Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Access, Searching and
> Indexing of Directories Working Group of the IETF.
>
> Title : A MIME Content-Type for Directory Information
> Author(s) : T. Howes, M. Smith
> Filename : draft-ietf-asid-mime-direct-02.txt
> Pages : 20
> Date : 07/30/1996
>
>This document defines a MIME Content-Type for holding directory
>information. The definition is independent of any particular directory
>service. The application/directory Content-Type is defined for holding a
>variety of directory information, for example, name, or email address.
>The application/directory Content-Type can also be used as the root body
>part in a multipart/related Content-Type for handling more complicated
>situations, especially those in which non-textual information that already
>has a natural MIME representation, for example, a photograph or sound, must
>be represented.
>
>The application/directory Content-Type defines a general framework and
>format for holding directory information in a simple "type: value" format.
>This format is compatible with the Versit Electronic Business Card
>Specification text encoding. Mechanisms are defined to specify alternate
>character sets, languages, encodings and other meta-information.
>
>Internet-Drafts are available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
> "get draft-ietf-asid-mime-direct-02.txt".
>A URL for the Internet-Draft is:
>ftp://ds.internic.net/internet-drafts/draft-ietf-asid-mime-direct-02.txt
>
>Internet-Drafts directories are located at:
>
> o Africa
> Address: ftp.is.co.za (196.4.160.8)
>
> o Europe
> Address: nic.nordu.net (192.36.148.17)
> Address: ftp.nis.garr.it (193.205.245.10)
>
> o Pacific Rim
> Address: munnari.oz.au (128.250.1.21)
>
> o US East Coast
> Address: ds.internic.net (198.49.45.10)
>
> o US West Coast
> Address: ftp.isi.edu (128.9.0.32)
>
>Internet-Drafts are also available by mail.
>
>Send a message to: mailserv@ds.internic.net. In the body type:
> "FILE /internet-drafts/draft-ietf-asid-mime-direct-02.txt".
>
>NOTE: The mail server at ds.internic.net can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e., documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>For questions, please mail to Internet-Drafts@ietf.org
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version
>of the Internet-Draft.
>
>