OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: rewrite entries processed in document order


/ Rob Lugt <roblugt@elcel.com> was heard to say:
| Paul Grosso wrote
| >
| > In general, the concept of almost all entries is first match.
| > Only in the case of delegate--where exact matches don't (usually)
| > exist--is the concept of longest introduced.
| 
| Right, but exact matches (usually) won't exist for rewrite entries either.
| So if the concept of longest match is appropriate for delegate entries,
| shouldn't the same concept apply to rewrite entries?

I don't think it's the partial matching that motivates the
longest-first behavior in delegate; it's the fact that multiple
delegated catalogs may apply. I see longest-first as a mechanism for
prioritizing the search order on this delegated list. Since rewrite
rules can have at most one match, I'm not naturally inclined to think
in terms of priority.

Do you have use-cases in mind that can only be satisfied by
longest-first rewrite rules?

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | Birds are taken with pipes that imitate their
XML Standards Engineer | own voices, and men with those sayings that
XML Technology Center  | are most agreeable to their own
Sun Microsystems, Inc. | opinions.--Samuel Butler


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC