RE: Attributes in Prelim DAV Spec

>The case I'm pointing to is where one attribute itself has attributes.
>Maybe the syntax here is just http://foo/bar<Abstract><Author>, where
><Author> identifies the person who wrote the <Abstract> attribute of the bar
>resource.
>
>[Yaron Goland]  This is illegal with the current syntax. It should really be
>done with Abstract.Author. Still that is not a clean solution. I have no
>problem extending the syntax to handle this case. Thoughts?
>
>
>OK, we need to think about the implications of this.  Now if I GET an
>attribute that turns out to be composite, what I get back might be a
>SiteMap.  Then I would have to follow each node in a separate GET to find
>the values of all the component attributes?  We need a shortcut for this
>process, to get that whole attribute value in one step.
>
>[Yaron Goland]  Jim and I are starting to dance around this now. Stay tuned.
>
>Also, we should understand (but not specify) what it would take to process a
>query against some component of a compound attribute.  (Find all the
>resources with print instructions that require stapling.)
>
>[Yaron Goland]  That is search and I won't get in the same zip code as it. If
>anyone else wants it fine, Vios Con Dios.
>
>[Yaron Goland]  			Yaron