Re: Wiki requirements and implementation alternatives update

>
> A bit off-topic, but the text right below the "implementation
> alternatives" also need some more generalization.
>
>  In particular where you say "a kind from the HTML5 kind table if the UA
> can determine the kind" as I'm not completely sure if there is always an
> obvious mapping between the various format and the "kind"s available in
> HTML5.
>
>  <Bob> You are right; there isn't always a mapping which is why the
> metadata is needed in the first place. I thought the sentence said "UA
> should set kind ..." I'll double check. </Bob>
>
>
This is also true but what I meant is different, that is: there may be a
mapping but may not be obvious or unambiguous or even unique. If you see
the OIPF contribution sent earlier on this list you will notice how the
value of kind there is related to the existence of certain other
fields/values in various places.

(regardless if the OIPF proposal is correct or not, the problem still exist)

/g