Re: [Scrollkeeper-devel] Simple URI's

[Laszlo K. <las...@su...>]

> > 2) Mapping the names.  The OMF file should specify the name by which the
> > document should be referred.  This seems to require yet another OMF
> > attribute to be created, perhaps IDENTIFIER.URINAME?  We will not have
> > complete uniqueness here.  However ideally we will have a 1-1
> > correspondence between NUID's and URINAME's.  We could keep a database on
> > the web so people can register names and find out if a name is taken.
> > This creates even more administrative overhead, but I think it is well
> > worth the trouble it would take to set up a simple php/mysql site on
> > SourceForge.
> 
> Not sure this is a good idea...you will have to have a 'URINAME' if you
> are typing the URI manually.
> 
> BUT:
> 
> I think that applications should give scrollkeeper a "title", locale
> (optional), and version # (optional), format (default would be Docbook).
> Scrollkeeper would then search its database and return the unique IDs
> (possible there will be more than one doc matching the criteria, so the
> client would either pick the first one, or try to do some other
> processing (e.g: See Also)).
> 
> You could also have another function that would return the "first found
> match" of the document directly (so you don't have to search for UUID,
> and then tell scrollkeeper to return this document - you just tell it
> "return the first document that matches this criteria").
> 
> Anyway, this approach would only work if you have a list of documents to
> choose from.
> 
> So, maybe URINAME's are the way to go.

Are you suggesting to try to partially match the string from the
Scrollkeeper URI with the "title" that you described above? 

Laszlo