ISSUE-97 (Core SAFETY): Shoudl Core safeness be restricted to Eiter-Schindlauer safeness [Core] from Rule Interchange Format Working Group Issue Tracker on 2009-04-01 (public-rif-wg@w3.org from April 2009)

From: Rule Interchange Format Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 1 Apr 2009 14:22:33 +0000 (GMT)
To: public-rif-wg@w3.org
Message-Id: <20090401142233.D9F226B62B@kent.w3.org>

ISSUE-97 (Core SAFETY): Shoudl Core safeness be restricted to Eiter-Schindlauer safeness [Core]

http://www.w3.org/2005/rules/wg/track/issues/97

Raised by: Christopher Welty
On product: Core

At the 10 Mar 09 telecon, the WG resolved that Core will be Eiter-Schindlauer-safe, but that restriction will be at risk (not putting in question simple safeness as defined in http://www.w3.org/2005/rules/wiki/Core#Safeness).  This degree of safeness restricts rulesets to a syntactically checkable set of features such that the ruleset is guaranteed to terminate in a forward-chaining engine.

This issue is intended to track that at-risk feature, to be closed when the WG has implementation feedback on whether this degree of safeness is considered necessary for any implementors.

See [http://lists.w3.org/Archives/Public/public-rif-wg/2009Mar/att-0051/2009-03-10-rif-minutes.html]

Received on Wednesday, 1 April 2009 14:22:43 UTC