> -----Original Message-----
> From: Robert Sanderson [mailto:[log in to unmask]]
> Sent: Tuesday, September 10, 2002 10:48 AM
> Because I don't want to end up in a situation where I can't
> predict the
> structure of the contents of an index because of different naming
This has absolutely nothing to do with nameing policies.
There will be a table somewhere which defines the type-1 attribute
combination for every index. That is the whole point of index sets: they
define the place where the indexes are specified. That specification is the
list of attributes.
> Hopefully everyone will support at least the Dublin Core
> index set, but if
> they don't specify it (for what ever reason) then they're at
> least more
> likely to call a title index 'foo.title' ...however when it comes to
> naming an exact title index, it could be titleString
> exactTitle, XTitle,
> title, etc. Same for titleWord titleKeyWord titleWords and so forth.
> This is why I'd like either one index, or a limited set of names to
> distinguish structure to append to the name given to the index.
But if I define index "pooh" as being use=1016, structure=6, ... is there
any problem? The name of the index is just a string. It has no implicit
You guys started that discussion while I was away. Is that the root of this