[gcs-pcs-list] big day in #code4lib

[Daniel Chudnov]

Y'all are going to have to gang up something fierce to convince me  
that the unAPI spec itself should say *anything* about the meaning of  
URIs or the meaning of patterns of URIs and specific unAPI servers.

unAPI services and clients should not be forced into a mode of  
operating on objects anywhere that is mandated to be at any specific  
node/level in the FRBR work-expression-manifestation-item model.  Or  
that any fetched object with any kind of URI from any unAPI server  
should be expected to remain identical over time or space.  Or that  
the only "correct" dissemination for some URI and FORMAT is from some  
specific server.

My premise behind wanting to work on this and related efforts is to  
simplify movement of information across applications... not to make  
moved information more rigorous, or more verifiable, or more  
trustworthy, or more authoritative, or any of that, just simpler.   
It's up to implementors to make their own choices about expectations  
and assumptions, including whether URIs have constructable meaning or  
not, or whether objects should be expected to stay the same or not.

If this is what you meant, cool.

Mess is lore!

   -Dan


p.s. not that this isn't a perfect discussion for one or more FAQs... :)