Search results
Jump to navigation
Jump to search
Page title matches
- = Design Pattern Metadata = [[Trustmark Evolving Pattern]] shows how the [[Trustmark]] can be included in web pages without breaking24 KB (3,856 words) - 16:05, 16 December 2021
Page text matches
- Example is the Common Design pattern Privacy Section: https://wiki.idesg.org/wiki/index.php?title=Design_Pattern *Tom captured the issues in the design pattern pages on the wiki. The problem was around pseudonymity in the Definitions f6 KB (955 words) - 04:02, 28 June 2018
- = Design Pattern Metadata = [[Trustmark Evolving Pattern]] shows how the [[Trustmark]] can be included in web pages without breaking24 KB (3,856 words) - 16:05, 16 December 2021
- #REDIRECT [[Trustmark Evolving Design Pattern]]47 bytes (5 words) - 20:33, 15 January 2016
- ##Design Pattern and Anti-Pattern work (First two to be submitted to TFTM, Privacy and MC for information rev ### Common Design Pattern and fit with Reqs / Guidelines: https://wiki.idesg.org/wiki/index.php?title3 KB (417 words) - 23:15, 13 April 2016
- = Design Pattern Metadata = ...e case that discusses privacy enhancing technology, but the purpose of the pattern is limited to the attributes requested by the RP and the corresponding user17 KB (2,712 words) - 19:20, 28 November 2021
- = Design Pattern Metadata = User Intent Design Pattern is meant as a composable object that can be included in any entity.9 KB (1,467 words) - 20:46, 9 September 2018
- = Design Pattern Metadata = This pattern shows one possible registration ceremony that a user follows to establish o11 KB (1,838 words) - 16:48, 19 January 2016
- **Design Pattern work **Action: UXC to review pattern work standards to be used as a resource and point to some specific pages th2 KB (276 words) - 04:02, 28 June 2018
- *Much more detail is on the page [[Trustmark Evolving Design Pattern]], which may not be fully up-to-date.5 KB (862 words) - 02:40, 12 November 2018
- * This pattern is a sub-set of the [[User Choice Pattern]] which covers the general user choice issues. It contains the general cont These patient choices and their attendant liability are addressed in Design Principles/Goals for a Healthcare Identity Environment Architecture above,15 KB (2,350 words) - 01:41, 1 October 2021
- *Common Design Patterns – Tom Jones joined the UXC call to discuss Design Patterns. **Consider describing each design pattern with a description about what problem it is solving.3 KB (391 words) - 04:01, 28 June 2018
- ...y will integrate the trust mark into the wiki and Ellen will do the common pattern. *Mary had a call with Tom about doing three more design patterns. The team felt we needed to get feedback from others before commi3 KB (532 words) - 03:58, 28 June 2018
- *Design Pattern Changes **Ellen had a few concerns with the text of the Design Pattern pages so they were not sent out as previously discussed at last week’s me4 KB (682 words) - 03:58, 28 June 2018
- *Design Pattern Work ...ew (Privacy, TFTM and to the Board). Ellen also updated text on the Design Pattern: Common to any Internet Identity Ecosystem as well. The team reviewed the c5 KB (835 words) - 03:58, 28 June 2018
- *Trustmark Evolving Design Pattern **The team continued the review of updates submitted by Ellen on design pattern text. Discussion followed.5 KB (760 words) - 03:58, 28 June 2018
- ...lockouts are entangled (they use the same flag). This is a poor but common design. ...a prepaid mobile phone can allow the purchaser to remain anonymous until a pattern of use is established. Also see Pseudonym.845 KB (86,833 words) - 04:00, 28 June 2018
- = Design Pattern Metadata = ===Design Pattern Lifecycle Status===10 KB (1,596 words) - 20:11, 15 October 2019
- ...UXC). While other terminology could be more appropriate, the split between design patterns and user scenarios seemed helpful at this stage. ...ain and body change in a matter of weeks, but there is a continuity to the pattern that these particles make." So with the patterns of the id ecosystem. It is12 KB (1,958 words) - 17:45, 25 May 2019
- .../Model%E2%80%93view%E2%80%93controller Model–view–controller (MVC)] design pattern has been used by UX designers to give user control of data held on computer ...separate view-models for each user interaction page. While this allows the design of view models that the user should be able to understand, the separation i8 KB (1,351 words) - 21:37, 27 March 2020