Re: Extending Entry Collections [Long]

[James M Snell <jasnell@xxxxxxxxx>]

Joe Gregorio wrote:

> On 7/26/05, James M Snell <jasnell@xxxxxxxxx> wrote:
>  
>
> > I think this is fine so long as it's not limited to HTML content.  The
> > definition of the @class value should determine the @type of content.
> > For instance, I should be able create a class that requires XML content,
> > or binary content, etc.
> >    
>
> We'll for binary, or any application/*+xml you could put them in a 
> subclass of the 'generic' collection which you then restrict via
> the 'mediatype' attribute. 
>
>  
Nah, doesn't work for me.  If the collection contains a bunch of entries 
whose content is XML contained within the atom:content element, it's an 
entry collection.  Entry collections should support entries with all of 
the content forms defined by the Atom format spec.  The only case where 
this starts to get vague is in referenced content (ala @src)

For me, entry collections are specializations of generic collections 
restricted to contain only Atom Entry Documents.  entry collections can 
be further refined using the @class mechanism you describe to restrict 
content @type. 

>  
>
> > As is the case with the @rel values, would it be possible to use
> > non-IANA registered fully qualified URI's?
> >    
>
> Yes.
>  
Cool.

- James