A couple of real-world usage problems

On Jul 11, 2006, at 8:43 PM, Tantek Çelik wrote:
> On 7/11/06 2:07 PM, "Ryan King"
<ryantechnorati.com> wrote:
>> ...
>> Your instincts are right. UID is a universal
identifier for an event.
>> Two events with the same UID should be considered
the same event
>> (assuming there are no trust issues).
>
> Agreed.  Though we will have to figure out how to treat
two events  
> with the
> same UID but found on different URLs.
>
> Which content is authoritative if the two conflict?

I'm not sure it really matters which one is
*authoritative*- we just  
know that they likely represent different events.

Now, how we go about determining trust is a different
matter, which,  
I suspect, is going to be application dependent.

> I believe the short answer is to use class="url
uid", that is, use  
> an actual
> URL to a definitive version of the event as its UID,
and then you  
> can always
> resolve conflicts between two sites posting the same
UID by actually
> *loading* that UID (since it is also a URL) and getting
the definitive
> details there.

That's what I was going in my previous comment  in this
thread. I was  
suggesting also using rel-bookmark (not class-bookmark) to
signify  
that not only is this a *a URL* for this event, but *the URL
for the  
canonical version of this event*.

-ryan

_______________________________________________
microformats-discuss mailing list
microformats-discussmicroformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss