Phase II IDEF Registry: Difference between revisions
Jump to navigation
Jump to search
Mary Hodder (talk | contribs) (Beginning page for IDEF Registry project Phase II) |
m (34 revisions imported: Initial Upload of old pages from IDESG Wiki) |
||
(33 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
[[Phase II priority list]] | [[Phase II priority list]] | ||
==Requirements Documents for Phase II== | |||
* Interop [[file:Interop_Requirements_Update.docx]] | |||
* Privacy [[file:Privacy_Requirements_Update.docx]] | |||
* Security [[file:Secure_Requirements_Update.docx]] | |||
* Usable [[file:Usable_Requirments_Update.docx]] | |||
===Archive of Files provided by Noreen=== | |||
* IDEF Registry Interviews - [[Post-Alpha_User_Research_Report.docx]] | |||
* IDEF Registry Final Analysis [[IDEF_Registry_Interviews-Requirements-Analysis.xlsx]] | |||
* [[File%3AEvaluation_of_Requirements-User_Research_Requirements_and_Scope.docx]] | |||
* [[File%3ANoreen-UX_Guidelines-w_Requirements.pdf]] | |||
===Open Issues=== | |||
after discussions with the team here are a few more thoughts: | |||
# There will be multiple identifier frameworks which have their own set of identity requirements. | |||
# Some of the frameworks will be IDEF compliant. | |||
# All IDESG compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework | |||
# Especially at the start most frameworks will not be IDEF compliant. | |||
# How should an IDEF compliant entity deal with identifiers that are: | |||
## from within their own framework, ie within Healthcare or within the education internet 2 framework, | |||
## from an external framework that is still IDEF compliant, ie a student being transfer from a school client to the healthcare hospital or from a VA hospital with a PIV card to a public hospital that cannot read it | |||
## from an external framework is is not IDEF compliant, ie from a social network site like Google, FB, Microsoft, etc. | |||
# There is no advice available for entities that do not normally interact with the user on recovery and redress | |||
# No standard has been found that helps to describe how a site with no user connectivity can meet any privacy or security guideline. |
Revision as of 04:02, 28 June 2018
Project details for Phase II should go here.. more to come.
Requirements Documents for Phase II
- Interop File:Interop Requirements Update.docx
- Privacy File:Privacy Requirements Update.docx
- Security File:Secure Requirements Update.docx
- Usable File:Usable Requirments Update.docx
Archive of Files provided by Noreen
- IDEF Registry Interviews - Post-Alpha_User_Research_Report.docx
- IDEF Registry Final Analysis IDEF_Registry_Interviews-Requirements-Analysis.xlsx
- File:Evaluation of Requirements-User Research Requirements and Scope.docx
- File:Noreen-UX Guidelines-w Requirements.pdf
Open Issues
after discussions with the team here are a few more thoughts:
- There will be multiple identifier frameworks which have their own set of identity requirements.
- Some of the frameworks will be IDEF compliant.
- All IDESG compliant frameworks will provide a machine-readable method to determine if a web site is a member of the framework
- Especially at the start most frameworks will not be IDEF compliant.
- How should an IDEF compliant entity deal with identifiers that are:
- from within their own framework, ie within Healthcare or within the education internet 2 framework,
- from an external framework that is still IDEF compliant, ie a student being transfer from a school client to the healthcare hospital or from a VA hospital with a PIV card to a public hospital that cannot read it
- from an external framework is is not IDEF compliant, ie from a social network site like Google, FB, Microsoft, etc.
- There is no advice available for entities that do not normally interact with the user on recovery and redress
- No standard has been found that helps to describe how a site with no user connectivity can meet any privacy or security guideline.