Re: [metaDataInURI-31]: Initial draft finding for public review/comment.

In a message dated 7/9/2003 2:13:28 AM US Mountain Standard Time, 
Patrick.Stickler@nokia.com writes:

> What if the metadata changes? Then you have a different URI, and things 
> break.
> 
I answered this in the previous email; however, I think an example
makes the point better.  Let's say, I love my car and want to publish
information about it.  I can identify it in many different ways.  One way to
refer to the car is with the unique vin # (let's say it is zb33322231s7).  

<A HREF="http://www.cars.com/zb33322231s7.html">http://www.cars.com/zb33322231s7.html</A>

or a better way to separate the identity of the thing from the identity of 
the resource about the thing would be:

<A HREF="http://www.cars.com/zb33322231s7.html">http://www.cars.com/zb33322231s7/mycar.html</A>

That way I could also have an RDF document that refers to the 
same unique thing like this:

<rdf:Description about="<A HREF="http://www.cars.com/zb33322231s7.html">http://www.cars.com/zb33322231s7/</A>">

But while this refers uniquely to a resource about my car, it is not
the common way that my car is identified in conversation.  The best 
identification would be (make/model/year/vin#):

<A HREF="http://www.cars.com/toyota/celica/2002/zb33322231s7/mycar.html">http://www.cars.com/toyota/celica/2002/zb33322231s7/mycar.html</A>

To me, the above URL is superior to our first version.

 - Mike
---------------------------------------------------
Michael C. Daconta
Chief Scientist, APG, McDonald Bradley, Inc.
www.daconta.net