Ann> 2) Domain name [ is* | contains | begins with | doesn't contain] JBeck> I don't think that "contains" or "begins with" or "doesn't JBeck> contain" would be useful (though who knows? others might), but JBeck> I think "ends with" would be good, or "is contained in". E.g., JBeck> "d-mpk17-229-131.SFBay.Sun.COM" is contained in "sun.com".
Ann> Hmm, I don't know about this last suggestion since "is contained in" is Ann> no longer used in the same sense as the other verb phrases that refer to Ann> string matching versus containment w/in a domain. For your example, I Ann> think that the rule the user would create is Ann> Domain name contains "sun.com" Ann> If the Domain name fed to the selection engine is Ann> "d-mpk17-229-131.SFBay.Sun.COM", then this rule would be true. Yes, I think we're on the same page; we just need to agree on terminology. I don't care what term we use, as long as we agree and it is clear to the user. The only point I wanted to make about "contains" in this context is that "foo.sun.com" contains sun.com for any value of foo, but that e.g. "twinsun.com" does not contain sun.com . In regular expression terms: *...@.]sun.com is what I meant. -- John http://blogs.sun.com/jbeck
