Re: Reviving the features draft?

[Aristotle Pagaltzis <pagaltzis@xxxxxx>]

* Bill de hOra <bill@xxxxxxxxxx> [2008-04-27 20:25]:
> Brian Smith wrote:
>>
>> <link rel='http://example.org/orderProcessor'
>>       href='http://example.org/collection'/>
>>
>> This way you can link directly to the collection instead of
>> linking to a service document that links to the collection. It
>> works inside of service documents too:
>>
>>   <app:collection href='http://example.org/collection'>
>>       <link rel='http://example.org/orderProcessor'
>>             href='http://example.org/collection'/>   </app:collection>
>
> Link is the wrong markup for this. Use atom:category to
> categorize resources. If you need something more formal, then
> use RDF.

I agree.

However, note that RFC 5023 does not specify a meaning for
atom:category within app:collection, only within app:categories,
but using atom:category within app:categories would convey the
wrong semantics for this application. (Namely, it would mean that
the enclosed categories apply to entries of the collection, when
what we want to say is which categories the collection itself
belongs to.)

With the caveat, therefore, that we need to be aware that putting
atom:category directly inside app:collection is an extension of
RFC 5023, I would agree that this is the right approach.


* James M Snell <jasnell@xxxxxxxxx> [2008-04-21 16:40]:
> However, given:
>
>  <collection href="...">
>    <a:title>foo</a:title>
>    <accept>...</accept>
>    <f:feature ref="http://.../a"; />
>    <f:feature ref="http://.../b"; />
>    <e:f />
>  </collection>
>
> I know exactly what the two f:feature elements indicates
> without having to know exactly what feature the ref is
> identifying. This allows me to me explicitly whether there are
> any features supported by the collection that I do not support,
> which is an important use case. This is not possible using the
> other approach.

I would cast this as

    <collection href="...">
      <a:title>foo</a:title>
      <accept>...</accept>
      <a:category scheme="http://example.org/feature"; term="http://.../a"; />
      <a:category scheme="http://example.org/feature"; term="http://.../b"; />
      <e:f />
    </collection>

Then you can look for categories of collections in a certain
scheme if you want to enumerate the features of a collection, but
you can also express different classes of collection properties
by associating each class with a scheme. This seems like it
should cover uses of Atompub in non-publishing context; an issue
that also came up recently.

Regards,
-- 
Aristotle Pagaltzis // <http://plasmasturm.org/>