RE: I-D ACTION:draft-ietf-asid-mime-direct-02.txt

[Alec Dun <AlecDu@xxxxxxxxxxxxxxxxxxxxxx>]

Your point is good.  It's more powerful if we make the datatype
parameter mandatory.  The pushback against doing this is v-card, which
doesn't type its data.  Perhaps it should be mandatory/optional on a
per/profile basis.  That would close some of the gaps on other profiles,
and keep the v-card profile reasonably similar to v-card.

If the type is missing we would do a (profile, property) -> type lookup.
 If the type is present we don't do the lookup.  The lookup tables may
be out-of-date in which case if the entry is missing, it would be
treated as text.  Even when datatype is optional, we save in two ways:
(i) if the table is out-of-date but the type is present we can still
figure things out, (ii) if the type is present, we don't need do the
lookup.

Thanks,
- Alec.

>----------
>From: 	Harald.T.Alvestrand@uninett.no[SMTP:Harald.T.Alvestrand@uninett.no]
>Sent: 	Tuesday, August 27, 1996 12:12 AM
>To: 	Alec Dun (Exchange)
>Cc: 	'Frank Dawson'; 'Tim Howes'; 'ietf-asid@umich.edu';
>'ietf-calendar@imc.org'
>Subject: 	Re: I-D ACTION:draft-ietf-asid-mime-direct-02.txt
>
>Making the datatype parameter optional makes it useless.
>If it's optional, your "generic tool" must be able to handle
>data both with and without it, meaning that you have to handle
>the special case of no datatype, so why would you bother to do
>anything with the type except to check it?
>
>I must have misunderstood.....
>
>         Harald A
>