ISSUE-4: Should Compliance model Requirement support the Interoperability CSF?
Should Compliance model Requirement support the Interoperability CSF?
- State:
- CLOSED
- Product:
- (no longer used) Design Constraints (Goals, Requirements)
- Raised by:
- Deborah Nichols
- Opened on:
- 2006-08-15
- Description:
- Unknown. Posted to Issues by Deborah Nichols [DLN].
Should the Compliance Model requirement* also support the Interoperability
CSF**? (It was removed from diagram pending discussion.)
Issue: Does the group agree/disagree that the Compliance Model Requirement*
should be (re-) linked to the Interoperability CSF**?
* This is a Phase I Requirement:
Compliance model
RIF must define a compliance model that will identify required/optional
features.
(http://www.w3.org/2005/rules/wg/wiki/UCR/Requirements#req-compliance-model)
** See http://www.w3.org/2005/rules/wg/wiki/UCR/Goals#csf-interoperability .
[This was item 2 in:
http://www.w3.org/2005/rules/wg/wiki/UCR/Document_issues.]
- Related Actions Items:
- No related actions
- Related emails:
- Draft minutes: RIF telecon 25 March 2008 (from der@hplb.hpl.hp.com on 2008-03-25)
Related notes:
There was some discussion about this issue which I was not party to.
However, the reason that a compliance model supports interoperability is that a formal understanding of
what it means to comply to the RIF is *essential* to the succesful use of RIF, and hence to interoperability.
The alternative to a formal compliance model is an informal one: i.e., that defined by what popular tools
support.
The requirement was dropped, but I believe erroneously.
2006-09-26: WG in telecon resolved to accept the link between the Compliance
Model Requirement and the Interoperability CSF, as that link is described in
Frank\'s Notes posted above (and in the email archives:
http://lists.w3.org/Archives/Public/public-rif-wg/2006Sep/0068.html).
This issue should be closed once the telecon minutes are approved and the link
is restored in the UCR document.
Closed by consensus at the 10/10/06 telecon
10 Oct 2006, 00:00:00Display change log
