Re: 8.3.4: comma separated?! app:accept

[James M Snell <jasnell@xxxxxxxxx>]

-1. A comma separated list is sufficient.

- James

Elliotte Harold wrote:
> 
> Section 8.3.4 states:
> 
> 8.3.4 The "app:accept" Element
> 
> The "app:accept" element value specifies a comma-separated list of
> media-ranges (see [RFC2616]).
> 
> Examples include:
> 
> 
>   <app:accept>image/png,image/*</app:accept>
>   <app:accept>image/*, image/png</app:accept>
>   <app:accept> image/* </app:accept>
> 
> This sets my teeth on edge. Why have we allowed *commas* to intrude into
> our clean XML markup? I'm guessing this just mirrors the HTTP headers,
> but they can't use XML. Furthermore because "app:accept has no notion of
> preference. As a result, the value syntax of app:accept does not use
> 'accept-params' or 'q' arguments as specified in [RFC2616], section
> 14.1." we can't naively copy from one to the other.
> 
> I propose allowing multiple app:accept elements, rather than just a
> single one. each app:accept element would contain exactly one media
> type. This would mean in 8.3.3 we change
> 
> 
> appCollection =
>    element app:collection {
>       appCommonAttributes,
>       attribute href { atomURI  },
>       ( atomTitle
>         & appAccept?
>         & appCategories*
>         & extensionSansTitleElement* )
>    }
> 
> 
> to
> 
> 
> appCollection =
>    element app:collection {
>       appCommonAttributes,
>       attribute href { atomURI  },
>       ( atomTitle
>         & appAccept*
>         & appCategories*
>         & extensionSansTitleElement* )
>    }
> 
> We'd also need to change the RELAX NG declaration regex of appAccept in
> 8.3.4.
>