Scope
An uxiverse.com typeScopes are Structural Elements that define the range of operation for their sub-elements. E.g. each user gets their own user-scope when they access their profile at example.com/myprofile, so the application will return different users when it accesses the 'currentUser' profile. To avoid confusion: In project management, this term is understood as the scope of work needed to finish a project. It can also mean different viewing instruments, microscope etc.
| Property | Expected Type | Description |
|---|---|---|
| ContextProperty | Element | A property that holds the context a UI element is in |
| DescriptionFlag | Element | Flags to express that a UI element describes something, e.g. isHelp, isContent, isProgress |
| HierarchyFlag | https://schema.org/Boolean | Flags that express a hierarchical position on an element |
| NavigationProperty | Element | A property that holds the navigation on a UI element, e.g. menu, settings |
| OutcomeProperty | A property that holds a result, output or status | |
| a11y | Element | Properties related to accessibility |
| input | Input is the value/parameter/prop that gets passed to an element in the UX, and can be empty. This applies to visual as well as non-visual elements. | |
| isInUseBy | When people collaboratively work, the property isInUseBy can be used to make an element non-editable until it is set free. Showing where other users are can also prevent conflicting edits. | |
| isUsableBy | To handle which User, Role or Group can use an Element of the UI, the property isUsableBy can be used to grey out parts of the interface, or hide them entirely. |