There are a couple of significant problems with that option: 1. We need to roundtrip the data. I.e. We have a middleware platform with an embedded Jess engine. We need to be able to not only be able to asserts facts based on data entering our platform, but also be able to regenerate data based on existing facts. If I change periods to underscores then I have no way of knowing what is a valid underscore and what is a stand-in for a period. 2. For a minor release of Jess (minor in the notation/release standpoint, not in its importance!), we need to change fundamentally how our platform operates, tooling surrounding our platform and potentially every existing application built on our platform that makes use of the embedded rules engine. This seems a little onerous.
Ideally, minor releases of any software package should be backwards compatible with existing releases within the same major release. (e.g. 7.1 should be backwards compatible with 7.0, but no guarantees on 6.x). - Alan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Lin Sent: Monday, July 14, 2008 12:43 PM To: [email protected] Subject: Re: JESS: Slot name restrictions I could be wrong, but the restriction is needed because of the java dot notation functionality. http://www.jessrules.com/jess/docs/71/rules.html#patterns_simple Jess> (defrule two-same-age-different-name ?person1 <- (person) ?person2 <- (person {age == person1.age &&lastName != person1.lastName}) =>(printout t "Found two different " ?person1.age "-year-old people." crlf)) JESS tries to get the age from person object in the example from 6.2.1. If slot names didn't have the restriction, it would be harder to automatically resolve the slot. In the past, I've replaced "." with "_" underline for things like URL's. peter On Mon, Jul 14, 2008 at 12:14 PM, Greenblatt, Alan <[EMAIL PROTECTED]> wrote: > I see there is a new restriction with 7.1 that slot names may not > contain a period ('.'). We will not be able to upgrade our platform > to 7.1 as long as this restriction is in place. We use URI's as slot > names, where periods are accepted and common (e.g. > "http://en.wikipedia.org/wiki/URI";) . What was the reason around > putting in this restriction? Is there a possibility of removing this > restriction or at least providing a runtime option removing the restriction? > > Thanks very much, > > Alan > > > Alan Greenblatt > VP, Semantic Technologies > Metatomix, Inc. > 3 Allied Drive, Ste 210 > Dedham, MA 02026 > (781.907.6766 work > (617.519.5583 cell > [EMAIL PROTECTED] > > -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] -------------------------------------------------------------------- -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
