[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Objects at REST...

• From: "Peter Hunsberger" <peter.hunsberger@g...>
• To: "Rick Jelliffe" <rjelliffe@a...>
• Date: Thu, 13 Mar 2008 09:25:25 -0500

On Thu, Mar 13, 2008 at 4:16 AM, Rick Jelliffe <rjelliffe@a...> wrote:

<snip/>

>  > I think this is the real issue; you can't just go around exposing all
>  > objects, you are going to have to make some conscious decision on what
>  > to expose and pick some way of controlling that. Whether this is via a
>  >  facade, annotations or something as simple as hacking package names
>  > won't really matter, but the work will still need to be done if such
>  > an approach is to be successful.
>  >
>  The issue is not whether you can expose all objects, it is how to have
>  URLs for everything important in the information, regardless of its
>  availability at optimal grain or format, and how to manage this.

Sure, but the question then becomes; how do you define "important"?
Again it comes down to the fact that someone somewhere has to define
the metadata.  If PRESTO does nothing more than allow you to aggregate
the metadata from different sources (types of objects?) it's providing
a valuable service, but I'd also tend toward calling that resource
discovery and not object discovery just to keep expectations in line
with what you're doing?  It seems that the term "object" is simply too
ambiguous regardless of whether your talking to a Web oriented crowd
or not.

</snip>

-- 
Peter Hunsberger

• Follow-Ups:
  • Re: Objects at REST...
    • From: Rick Jelliffe <rjelliffe@a...>

• References:
  • Objects at REST...
    • From: "Andrzej Jan Taramina" <andrzej@c...>
  • Re: Objects at REST...
    • From: "Peter Hunsberger" <peter.hunsberger@g...>
  • Re: Objects at REST...
    • From: Rick Jelliffe <rjelliffe@a...>