Published
design
vr.tr.design · thing-q82604
Let an agent handle design by field, brief, process, evaluation and rights.
Thing Registry Activities and processes ACT.ACT
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Brief Goals.
Goals
Requirements.
Goals
Brief.
- What must the design achieve, for whom? definition
- Under which constraints? boundary
Field
Discipline.
Field
Design field.
- Which design field applies? definition
- Which specific entry fits? action
Process How design works.
Methods
Research and prototyping.
Methods
Methods.
- Which methods are used: research, sketching, prototyping? definition
- How many iterations? measurement
Collaboration
Stakeholders.
Collaboration
Collaboration.
- Who is involved in design decisions? provenance
- Are users included? boundary
Evaluation Testing.
Usability
User testing.
Usability
Usability.
- How was the design tested with users? provenance
- What did it find? provenance
Accessibility
Inclusion.
Accessibility
Accessibility.
- Does the design meet accessibility standards? boundary
- Who checked? provenance
Rights Protection.
Protection
Design rights.
Protection
Design rights.
- Is the design registered or protected? provenance
- In which territories? provenance
Credit
Attribution.
Credit
Attribution.
- Who designed it? provenance
- Is credit given? boundary
Classifiers Filled
- Family
- Thing Registry
- Category
- Activities and processes
- Entry kind
- thing
- Plane
- ACT
- Domain
- ACT.ACT
- Other names and narrower kinds
- garden room, borrowed scenery, Hilltowns in Italy, sonification, acoustic monitoring, data sonification, lighting design, strategic design, computational design, lofting, medical device design, processor design
What it is Filled
The planned process of conceiving and specifying objects, systems, spaces, interactions or services to meet goals within constraints, across fields such as product, graphic, architectural, landscape, interaction and sound design.
Why it exists Filled
Let an agent handle design by field, brief, process, evaluation and rights.
Distinguishing features Filled
- Planned, goal-directed process
- Iterative
- Balances constraints
- Protected by design rights
What robots and AI may and may not do Filled
Must not
- Copy another designer's protected work and present it as original.
- Design deceptive interfaces that trick people into choices they would not make.
- Sign off a design that bears safety responsibilities without a qualified person.
- Ignore accessibility requirements that exclude disabled users.
Only with a human decision
- Approving a design for construction, manufacture or release.
May
- Help draft, critique and document designs within a brief.
- Check a design against stated requirements, accessibility and safety standards.
Moral aspects Filled
- Design decides who can use a thing and who is left out.
- Designers are owed credit for their work.
Who is affected
- Users, including disabled users
- Designers
- People affected by what is built
Owners Filled
Steward
The designer or design team, with the client who commissions it.
Master systems
- Design right and registered design registers
Links to other meta-models Filled
parent
- Q104637332 - registry parent class
- Q1519454 - registry parent class
- Q1914636 - registry parent class
related
- planned process - category
- artefact and specification - outputs
- usability testing - method
- design right - law
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.design
- Wikidata: Q82604 (https://www.wikidata.org/wiki/Q82604)
Direct properties not applicable Not applicable
Not applicable
Plane ACT: no invented physical properties.
Recognition optional Filled
- Design briefs and specifications
- Fields such as garden design or sonification
- Design as the resulting pattern is a related sense
- Sketches, models, prototypes, specifications and finished artefacts.
Capabilities and actions required Filled
- write a design brief
- prototype and test
- evaluate with users
- protect designs legally
Hazards and failure modes required Filled
- Ignoring users and accessibility
- Unclear briefs
- Copying protected designs
Standards and interfaces required Filled
- ISO 9241-210 human-centred design
- EU design law
- Accessibility standards
Context of use required Filled
- Shaping how things work, look and are experienced.
- product and industrial design
- graphic and communication design
- architectural and landscape design
- interaction and service design
- sound and data sonification design
Sources Filled
- Wikidata item Q82604: design - identity and sense of the item
- Wikipedia: Design - general description of the item
Open questions
- Should design fields be separate entries?
- How should design methods be linked?
- How should design as pattern be split off?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q82604/spec.json