Stable ID problem [earlier Binding proposal]

[Svante Schubert <Svante.Schubert@Sun.COM>]

Bruce D'Arcus wrote:
>
> On Mar 20, 2007, at 6:19 AM, Svante Schubert wrote:
>
>>> But you're not solving the problem: you're avoiding it. Using 
>>> "odf:.." as you propose is functionally the same as using "file:///..."
>> The odf: would only refer into the same ODF package, it is not 
>> relative to the document location, by this different to file://
>
> But what's the identity of "the package"? That's what we need to 
> define, and it needs to be stable and globally unique.
>
I fear the stable criteria is problematic.

If someone is referencing to a part of a remote ODF document (e.g. on a 
server) using the concept earlier offered:

    <rdf:Description 
rdf:about="tag:odf:550e8400-e29b-41d4-a716-446655440000:6B29FC40-CA47-1067-B31D-00DD010662DA/content.xml#foo">

       <!-- "rdf:about" similar to 
tag:odf:[uuid-base]:[uuid-version]/content.xml#foo -->
        ...
    </rdf:Description>

The relation will broke irrevocably when the first character / style / 
anything has been changed in the remote ODF document, as the reversion 
ID will change.

The simple solution avoiding document identification seems safer.

If you disagree, we should compare the two solutions with the problem 
scenarios we have:

- metadata relation in document
- metadata relation among documents

Svante