ISSUE-47
define extension interface for content-scanning tools (public comment)
- State:
- CLOSED
- Product:
- wsc-usecases
- Raised by:
- Bill Doyle
- Opened on:
- 2007-04-16
- Description:
- From public comments
raised by: Al Gilman Alfred.S.Gilman@ieee.org
http://lists.w3.org/Archives/Public/public-usable-
authentication/2007Apr/0000.html
define extension interface for content-scanning tools
where it says, in 5.5 Content based detection
The Working Group will not recommend any checks on
the content served by web sites.
please consider
I don\'t think that you mean people shouldn\'t check signatures on signed
content. What I think that you mean is that the filter queries or trip
thresholds
for statistical techniques such as you discuss will not be published by the
group.
You should consider providing a programmatic interface (perhaps a hypothesis
lattice compatible with what a voice recognizer looks like in EMMA) for such
tools to contribute to rational decision making about when to raise a warning,
and in addition an interface where they can contribute message-content to the
security infoset.
Why?
The free-content areas drive trust. Confidence schemes work in this domain.
So there is an enduring value-added niche for such techniques. The group
should seek to define interfaces whereby third-party software can contribute
its findings to the rollup summarized by your recommended presentation.
Otherwise we will continue with the plethora of security helpers waving
plackards in our faces.
- Related Actions Items:
- No related actions
- Related emails:
- RE: ISSUE-47: define extension interface for content-scanning tools (public comment) (from wdoyle@mitre.org on 2007-04-20)
- Re: ISSUE-47: define extension interface for content-scanning tools (public comment) (from Mary_Ellen_Zurko@notesdev.ibm.com on 2007-04-18)
- ISSUE-47: define extension interface for content-scanning tools (public comment) (from dean+cgi@w3.org on 2007-04-16)
Related notes:
No additional notes.
Display change log
