ISSUE-97: Shoudl Core safeness be restricted to Eiter-Schindlauer safeness
Core SAFETY
Shoudl Core safeness be restricted to Eiter-Schindlauer safeness
- State:
- CLOSED
- Product:
- Core
- Raised by:
- Christopher Welty
- Opened on:
- 2009-04-01
- Description:
- 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] - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-97 (Core SAFETY): Shoudl Core safeness be restricted to Eiter-Schindlauer safeness [Core] (from sysbot+tracker@w3.org on 2009-04-01)
Related notes:
At F2F13, the WG resolved to close this issue by removing the at-risk normative comment about E-S (strong) safety and make it an informative note.
See http://www.w3.org/2005/rules/wg/meeting/2009-04-17#resolution_1 http://www.w3.org/2005/rules/wg/meeting/2009-04-16#resolution_2
Display change log
