1. Capturing
Design
Intents
DIO:
A
content
ontology
design
pa7ern
h7p://purl.org/dio
Monika
Solanki
University
of
Oxford,
UK
monika.solanki@cs.ox.ac.uk
h7p://www.monikasolanki.uk
WOP2015
at
ISWC2015
2. Capturing
Design
Intents
DIO:
A
content
ontology
design
pa7ern
MoMvaMon
• Most
current
approaches
for
design
documenta<on
focus
on
the
“what”
and
“not”
on
the
“why”.
• CollaboraMve
design
à
communica<on
intensive
à
need
to
preserve
design
decision
ra<onales
for
posterity.
• Legacy
methodologies
lack
the
conceptualisa<ons
needed
to
relate
designed
arMfacts
to
their
origina<ng
requirements.
3. Source:
Wikipedia
A
specifica<on
of
an
object,
manifested
by
an
agent,
intended
to
accomplish
goals,
in
a
par<cular
environment,
using
a
set
of
primi<ve
components,
sa<sfying
a
set
of
requirements,
subject
to
constraints
What
is
a
Design?
4. Capturing
Design
Intents
DIO:
A
content
ontology
design
pa7ern
Intent
DIO
provides
a
minimalisMc
abstrac<on
and
defines
conceptual,
generic
en<<es
for
the
modelling
of
seman<cally
enriched
knowledge
required
to
capture
the
intents
or
raMonale
behind
the
design
of
an
arMfact.
The
pa7ern
can
be
specialised
to
define
domain
specific
design
intents.
5. Capturing
Design
Intents
DIO:
A
content
ontology
design
pa7ern
Typical
Competency
QuesMons
• What
are
the
solu<on
choices
for
a
design
goal?
• Which
requirements
are
being
fulfilled
by
the
accepted
design
solu<on?
• What
are
the
jus<fica<ons
for
a
proposed
solu<on?
• What
are
the
arguments
against
a
proposed
solu<on?
• What
is
the
status
of
a
design
issue?
• Which
agents
have
supported
a
solu<on?