Metadata representation for outdoor AR services

Woontack Woo, Ph.D.
KAIST UVR Lab.
Daejeon, Korea
ISO SC24 WG9, [Jan. 14, 2016]
ISO SC24 WG9 & Web3D Meeting 2016 Jan. 11~14, 2016 1

 Based on Two Domestic Standards
◦ TTAK.KO-10.0434 (Dec. 2010): Representation for AR: POI, Content, Link
◦ TTAK.KO-10.0851 (Dec. 2015): Metadata for AR content visualization & sharing
 Proposal on “Metadata: data about data”
◦ Metadata modeling for context-aware MAR services,
 what::Status, (physical/virtual object ID)
 who::Role, (author profile)
 when::Time, (created, modified)
 where::Location, (geographical/relative position)
 how::Action, (link/interaction/response method)
 why::Goal,
◦ Meta-tagging: the process of adding metadata with 5W1H
to various physical/virtual assets/entities
ISO SC24 WG9 & Web3D Meeting 2016Jan. 11~14, 2016 2

 Milgram's Reality-Virtuality Continuum [94]
 Azuma's definition on AR [97]
◦ combines real and virtual
◦ is interactive in real time
◦ is registered in real 3D world

 UVR: MAR for DigiLog Life (Woo)
◦ 3D Link between dual (real & virtual) spaces with
additional information
◦ CoI (Context-of-Interest) Augmentation, not just
sight: sound, haptics, smell, taste, etc.
◦ Bidirectional Interaction/collaboration (UX) in dual
spaces
SPACES
Private (3rd skin)
Social
General/Public
Real space
Social Networks
Seamless
Augmentation btw
dual spaces
How
to
Link
Seam
lessly? CoI
LINK
AR‐Content
Virtual space

 Holistic Layers of Spaces
.
.
.
.
.
.
Real/Physical
Virtual/Cyber
Information/
Knowledge
SPACE
TIME
Layers Social/wisidom

 MAR as Metaverse
Modeling
Interaction
Networking
SensingMetaverse
Measured
Space
Physical
Space
Virtual
Space
SensingModeling
Anchoring
(Augmentation)

 Enhance Experience, Engage, Edutainment
UVR Simulator Augmented Room

 Application Demo

 Increased Interest and Demands on MAR
◦ Popularized since the advent of so-called “AR Browsers”
◦ Ubiquitous VR, Extended R, Cross R, co-existence R, etc.
 However, Incompatible MAR Contents
◦ Most AR contents are not re-usable in other applications
◦ Different “processes, data structure/format, etc.”
◦ More importantly, differences in linking approach
 The key of MAR services is
◦ Metadata for Anchoring between “Real” + “Virtual”
 However,
◦ No Standardized “metadata” Format for MAR content

 Support MAR Use Cases: Augmenting
◦ Location with Virtual Content (VC)
◦ Fixed/Movable Real Object (RO) with VC
◦ One’s own VC over Other User’s RO
◦ Multiple VC onto a RO from Multiple Users

 Goal: Representation of Metadata Should
◦ Be platform independent and interoperable
◦ Enable searching, filtering, and sharing of MAR content with
 structured fields 5W1H: (Who, When, Where, What, How) + Why
◦ Be concise, compact, yet flexible, extensible to use
 Support various MAR use cases
 Scope: Be able to refer
◦ PoI: real entity (person/object/space/location) or content
◦ VoI: MAR content (image, text, video, audio, 3D model)
◦ AR Anchor: Link between RC & VC:– contains the
instructions for MAR visualization

 ISO/IEC CD 18039

External
Services
User profile
(Experience,
Knowledge,
Behavior)
Simulator
(Event, Space)
Renderer
MAR Execution Engine
Conceptualized PoIs
Personal Device Display
User
Interface
MAR Scene
(Events, Targets, …)
Environment (or
wearable) Sensors
for Real World
Capturer
Internet of Thing
(IoT)
Sensors
Sensors
GPS
Compass
Gyro sensor
Personal Device
Embedded
Camera
Media
Assets
MAR Content
Virtual
Object
Information
Physical
World
Related MAR Contents
Open API
Physical World
User
User
Input
User
Command
Enhanced
Experience
MAR
Visualization
Recognition Data
MAR Anchor
Selected PoI
Context Analyzer
PoI Analyzer
User Localization
View Point Setting
PoI Analyzing
Context Processor
Context Integration
Context Inference
Context Management
Recognized
PoIs
User Context
Sensor Data
PoI Recognition
Data

5W1H Metadata Schema
who MAR Contents.{Owner, Creator}
when
MAR Contents.{Created Time, Modified Time, Accessed Time,
Duration}, CHE Information.{Begin Time, End Time}
where CHE Information.{Location}
what
MAR Contents.{ID, Name, Type, Tag, Reference, MAR
Anchor.ID}, CHE Information.{Type, Description}, VO.{Type,
String, Data File}, Media Asset.{Type, Data File}
how CHE Information.{Condition state}
Anchor
PoI: Metadata1
3 MAR Content:
Metadata
who MAR Anchor.{Owner, Author}
when MAR Anchor.{Authored time, Modified time}
where
MAR Anchor.{PoI Coordinate, Contents Coordinate, Coordinate
Type}
what MAR Anchor.{ID, Tag, PoI.ID, MAR Contents.ID}
how MAR Anchor.{Scale, Interaction, Animation, Accessibility}
MAR Anchor:
Metadata2
Anchor
Real
Object
Virtual
Contents
Anchor
who Recognition Data.{Owner, Creator}
when Recognition Data.{Created Time, Modified Time}
where
PoI.{Location, Front Direction}, Recognition Data.{Personal
Device Location, PoI 3D Position}
what
PoI.{ID, Name, Tag, Recognition Data.ID, MAR Anchor.ID},
Recognition Data.{ID, Data Set ID, Sub‐Data Set ID, Current Sub
Data, Candidate Sub Data}
how
Recognition Data.{Scale, Gyroscope, Compass, Intrinsic
Parameter}

 Eiffel Tower Augmentation
VID: Virtual bird
VID: Virtual Eiffel
Virtual map
http:.//Geovid.org

 Meta-tagging
WHO WHEN WHERE WHAT HOW
+Virtual
Bird.{Owner,
Creator}
+Virtual
Eiffel_Tower.
{Owner,
Creator}
+Virtual Bird.{Created Time,
Modified Time, Accessed Time,
Duration}
+Virtual Eiffel_Tower.{Created
Time, Modified Time, Accessed
Time, Duration}
+Virtual Eiffel_Tower
Info.{Begin Time, End Time}
+Virtual
Eiffel_Tower
Info.{Location}
+Virtual Bird.{ID, Name,
Type, Tag, Reference,
Eiffel_Tower Anchor.ID}
Info.{Type, Description}
VO.{Type, String, Data
File}
+Virtual
Eiffel_Tower
Info.{Condition
state}
+Eiffel_Tower
Anchor.{Own
er, Author}
+Eiffel_Tower
Anchor.{Authored
time, Modified
Time}
+Eiffel_Tower
Anchor.{PoI Coord.,
Contents Coord., Coord.
Type}
+Eiffel_Tower
Anchor.{ID, Tag,
PoI.ID, MAR
Contents.ID}
+Eiffel_Tower
Anchor.{Scale,
Interaction, Animation,
Accessibility}
2
1
3
+Eiffel_Tower
Recognition.{
Owner, Creator}
+Eiffel_Tower
Recognition.{
Created Time,
Modified Time}
+Eiffel_Tower PoI.{Location,
Front Direction}
+Eiffel_Tower
Recognition.{Personal Device
Location, PoI 3D Position}
+Eiffel_Tower PoI.{ID,
Name, Tag, Rec. Data,
MAR Anchor.ID}
+Eiffel_Tower
Recognition.{ID, Data Set
ID, Candidate Sub Data}
+Eiffel_Tower
Recognition.{S
cale, Gyroscope,
Compass,
Intrinsic
Parameter}
http:.//Geovid.org

 Korean Palace Augmentation
MAR Content
PoI
http:.//Geovid.org

 Meta-tagging
2
1
3
+Virtual
Palace.{Own
er, Creator}
+Virtual Palace.{Created Time,
Modified Time, Accessed Time,
Duration}
+Virtual Palace Info.{Begin
Time, End Time}
+Virtual
Palace
Information.{L
ocation}
+Virtual Palace
Information.{Type,
Description}
+Virtual Palace VO.{Type,
String, Data File}
+Virtual
Palace
Info.{Condi
tion state}
+Palace
Anchor.{Ow
ner, Author}
+Palace
Anchor.{Authored
time, Modified Time}
+Palace Anchor.{PoI
Coord., Contents
Coord., Coord. Type}
+Palace Anchor.{ID,
Tag, PoI.ID, MAR
Contents.ID}
+Palace Anchor.{Scale,
Interaction, Animation,
Accessibility}
+Palace
Recognition.
{Owner,
Creator}
+Palace
Recognition.{Create
d Time, Modified
Time}
+Palace PoI.{Location,
Front Direction}
+Palace
Recognition.{Personal
Device Location, PoI 3D
Position}
+Palace PoI.{ID, Name,
Tag, Rec. Data, MAR
Anchor.ID}
+Palace Recognition.{ID,
Data Set ID, Candidate Sub
Data}
+Palace
Recognition.{Sc
ale, Gyroscope,
Compass,
Intrinsic
Parameter}
http:.//Geovid.org

Metadata Structure MAR Contents Sharing

 Now, do you think …
◦ It is useful?
◦ It is worthy of standard?
◦ Which parts?
 Possible MAR Services in
◦ Tour guide services in Cultural Heritage

Metadata Type Definition
.ID
String or
Number
Identification of PoI instance
.Name String Name of PoI
.Tag String[] Information marking for the content searching
.Recognition
Data.ID
String or
Number
ID of Recognition Data instance called in PoI Class
.MAR Anchor
.ID
String or
Number[]
ID of MAR Anchor instance called in PoI Class
• Contains metadata fo
r the PoI
• Inherit Class:: Recogni
tion Data
• Legend
• Who
• When
• Where
• What
• How
• Call other class
• ID: CD_Palace_001
• Name: Injung-Jun
• Tag : {Palace, King, … }
MAR Anchor.ID:
{Injung_Txt, Injung_Img}
Recognition Data.ID:
Recog_Injung

.Location GPS GPS coordinate of PoI.
.Front Direction
Float (-1 or
[0,360])
Direction of front of the PoI measured by
Compass. If the PoI is view-point
invariant(i.e. symmetric) then the value is -
1(NULL)
• Contains metadata fo
r the PoI
• Inherit Class:: Recogni
tion Data
• Legend
• Who
• When
• Where
• What
• How
• Location : (126.9910827,37.5794506,0)
• Front Direction : 180 (Due South)

.Personal Device Locat
ion
GPS GPS coordinate of personal device
.Compass Float
User view direction on Digital Compass in
Personal Device
.Scale
Float (x, y,
z)
Real Scale of the PoI
• Point, Target image a
nd any type of data fo
r PoI recognition
• Legend
• Who
• When
• Where
• What
• How • Scale : (16.43, 10.21, 5.67) (meter)
• Compass : 76.325 (degree, North is 0)
• Personal Device Location :
(126.9910827, 37.5794506, 0.125)

.PoI 3D Position
Float (x, y,
z)
3D position of the PoI in vision-based
Local Coordinate captured by personal
device. (Center of Local Coordinate is GPS
location of PoI)
r PoI recognition
• Legend
• Who
• When
• Where
• What
• How
• Location : (126.9910827,37.5794506,0)
• Front Direction : 180 (Due South)
Local
Coordinate
xy
z
• PoI 3D Position:
(47.64, 12.53, 69.64)
• Location of PoI (126.9910827,37.5794506,0) become (0,0,0)

.Gyroscope
Float (x, y,
z)
3-Dim value of Camera Pose measured by
Gyroscope
.Intrinsic Parameter
Float (fx,fy
,cx,cy,k1,k
2,k3,r)
Intrinsic parameter of the embedded lens. f
x, fy are focal length of the lens. cx, cy are
principal point of the lens. (c.f. Skewness of
the cell array is 0.) k1,k2,k3,r are distortion
parameters of lens acquired by camera calib
ration. Those parameters can be converted
with respect to camera model. (In this case,
Pin-hole model)
r PoI recognition
• Legend
• Who
• When
• Where
• What
• How
• Intrinsic Parameter :
(3200.35, 1046.24, 1047.453, 876.23,
0.076, -0.101, -0.001, -0.001)
• Gyroscope : (28.462, 129.693, 15.23)

.ID
String or
Number
Identification of Recognition Data Instance
.Owner String
Person or group that have rights or custody
on Recognition Data
.Creator String
Person or group that create the Recognition
Data
.Created Time Time The time when recognition data was created
.Modified Time Time
The time when recognition data was
modified
r PoI recognition
• Legend
• Who
• When
• Where
• What
• How
• ID : Recog_Injung
• Owner : Culture Authorities
• Creator : KCTM Team
• Created Time : 2015.04.03, 17:24
• Modified Time : 2015.06.07, 14:13
Recognition
Data

nd any type of data f
or PoI recognition
• Legend
• Who
• When
• Where
• What
• How
.Data Set ID
String or
Number
Identification of Data file set for
recognition of certain PoI
.Sub-Data
Set ID
String or
Number
Identification of partial Data file set for
recognition of certain PoI
.Current
Sub Data
Binary file Currently utilized Sub-data file
.Candidate
Sub Data
Binary file
Possible Sub-data file utilized soon
according to the movement of User
• Data Set ID : Injung
• Sub-Data Set ID : Front 02
• Current Sub Data : Injung_Front_02.bin
• Candidate Sub Data :
Injung_Front_01.bin, Injung_Front_03.bin,
Recognition
Data
Sub-Data ID:Front 01
Injung_Front_01.bin
Injung_Front_02.bin
Injung_Front_03.bin

• Metadata for the
MAR visualization
• Legend
• Who
• When
• Where
• What
• How
.ID
String or
Number
Identification of MAR Anchor instance
.MAR Contents.ID
String or
Number
ID of MAR Contents instance called in MA
R Anchor Class
.PoI.
ID
String or
Number
ID of PoI instance called in MAR Anchor cl
ass
.Tag String[]
Information marking for the content searchi
ng
.Accessibility
Enum={
Public,
Private,
Custom}
Class that can access to the MAR Contents
Anchor
• PoI.ID: ID: CD_Palace_001
• MAR Contents.ID:
CD_Morning_Assembly
• Accessibility: Public
• ID: InJung_Morning_Assembly
• Tag: Palace, King, Music …

MAR visualization
• Legend
• Who
• When
• Where
• What
• How
.Owner String
on MAR visualization anchor
.Author String
Group of user that create MAR visualization
anchor
.Authored time Time
The time when MAR visualization anchor
was created
.Modified time Time
The time when MAR visualization anchor
was modified
• Owner: Culture Authorities
• Created Time : 2015.04.03, 17:24
• Modified Time : 2015.06.07, 14:13
Anchor
• PoI.ID: ID: CD_Palace_001
CD_Morning_Assembly
• Accessibility: Public

MAR visualization
• Legend
• Who
• When
• Where
• What
• How
.PoI Coordinate
Float (x, y,
z)
3-dim Position of PoI on Local Coordinate of
MAR scene
.Contents
Coordinate
Float (x, y
(or, z))
position of MAR Contents in MAR scene
.Coordinate
Type
Enum={Fi
xed,
Relative}
Type of Coordinate. If Fixed, fixed 2-dim
position in device display is utilized.
Otherwise, 3-dim relative position
determined by the PoI position in local
coordinate (Center of PoI becomes the center
(0) of local coordinate)
• PoI Coordinate: (25.436, 46.56, 12.4)
• Coordinate Type : Fixed
• Contents Coordinate : (4.25, 2.15)
or
• Coordinate Type : Relative
• Contents Coordinate : (-21.186, 0,-0.4)

MAR visualization
• Legend
• Who
• When
• Where
• What
• How
.Scale
Float (x, y
(or , z))
Size of the MAR contents in MAR scene.
(dimension of the scale depends on the
content)
.Interaction
Enum={
Touch,
Drag}
How MAR Contents interacts with the user
.Animation
{Motion,
Effect,
Transformati
on}
Animation Effects applied into the MAR
contents. Actual developments depends on
the platform. Multiple choice is enabled.
• Scale : (8.5, 92.5, 12.4)
• Interaction : Touch
• Animation : Null

• Contains the
metadata for MAR
Contents, include
• CHE(Cultural
Heritage Entity)
Information
• VO(Virtual
Object)
• Media asset
• MAR contents is subdivided into
cultural heritage entity(CHE)
information, virtual object, and
media asset
◦ CHE information covers the text-based
cultural heritage knowledge such as
museum document
◦ Virtual object handles 2D or 3D virtual
model augmented for PoI
◦ Media asset class contains the
multimedia data related with PoI

• Contains the
metadata for MAR
Contents, include
• CHE(Cultural
Heritage Entity)
Information
• VO(Virtual
Object)
• Media asset
• Legend
• Who
• When
• Where
• What
• How
.ID
String or
Number
Identification of MAR Contents instance
.Name String Name of the MAR contents instance
.Owner String
of MAR Contents
.Creator String
Person or group that perform create MAR
Contents
CD_Morning_Assembly
• Name: Morning Assembly

• Contains the
metadata for MAR
Contents, include
• CHE(Cultural
Heritage Entity)
Information
• VO(Virtual
Object)
• Media asset
• Legend
• Who
• When
• Where
• What
• How
.Created Time Time The time when MAR Contents was created
.Modified Time Time The time when MAR Contents was modified
.Accessed Time Time The last time when MAR Contents was accessed
.Duration Time Estimated time for the MAR Contents
• Created Time :
2015.04.03, 17:24
• Modified Time :
2015.06.07, 14:13
• Accessed Time :
2015.07.03, 10:48
• Duration : 38 (sec)
CD_Morning_Assembly
• Name: Morning Assembly

• Contains the
metadata for MAR
Contents, include
• CHE(Cultural
Heritage Entity)
Information
• VO(Virtual
Object)
• Media asset
• Legend
• Who
• When
• Where
• What
• How
.Type
Enum={CHE,
VO, MA}
Type of the MAR contents. Can be chosen
among Cultural heritage Entity(CHE),
Virtual Object(VO), Media Asset(MA)
.Reference String[]
References of MAR Contents. Include the
all references of CHE information, Media
Asset class
.Tag String[]
Information marking for the content
searching
.MAR Anchor.ID
(String or
Number)[]
IDs of MAR Anchor instances called in
MAR Contents class
• Type : MA (Media Asset)
• Reference : CultureContents.com
• Tag : Palace, King, …
• MAR Anchor.ID:
InJung_Morning_Assembly
Anchor

• Information about
CHE including PoI t
hat are virtually au
gmented
• Legend
• Who
• When
• Where
• What
• How
.Type
{Actor, Place, T
hing, Event, Tim
e}
Type of depicted cultural heritage entity. M
ultiple choice is enabled
.Description String
Piece of writing gives the details about the
cultural heritage entity in MAR Contents
.Location String
Name of place or address that cultural herit
age entity is located in over the certain time
-span
• Type: Event
• Description: Morning assembly
was…
• Location: Seoul-si, Jung-gu, …
Text Information

• Information about
CHE including PoI t
hat are virtually au
gmented
• Legend
• Who
• When
• Where
• What
• How
.Begin Time Time The time when PoI was brought into existence
.End Time Time
The time when PoI was took out of existence (for ins
tant event, Begin Time==End Time)
.Condition
state
String
the states of PoI characterized over the certain time-s
pan
• Begin Time: 1528-02-15
• End Time: 1528-02-15
• Condition State: Perished
Text Information

• Metadata for Virtu
al object represent
ed in MAR visualiza
tion excluding med
ia asset
• Cover all virtual obj
ect including UI obj
ect
• Legend
• Who
• When
• Where
• What
• How
.Type
Enum={
Text box, 2D
Model, 3D
Model}
Type of VO represented in MAR Contents
.Text String Text contained in Virtual Object
.Data File Binary Files
Data file for 3D model consists of polygon
model and textures
• Type: 3D Model
• String: Null
• Data File: Queen.bin
Queen.bin

• Multimedia data re
presented in MAR
visualization with r
eference such as i
mages, sound, mov
ie, etc.
• Legend
• Who
• When
• Where
• What
• How
.Type
Enum={
Image, Sound,
Movie}
Type of media asset
.Data File Binary File Data file for media asset
• Type: 3D Movie
• Data File: MorningAssebly.mp4 MorningAssembly.mp4

 “The future is already here. It is just not
uniformly distributed” by William Gibson (SF
writer)
 More Information
Woontack Woo, Ph.D.
Twitter: @wwoo_ct
Mail: wwoo@kaist.ac.kr
Web: http://uvr.kaist.ac.kr
ISO/IEC JTC1 SC24 Meeting (London, UK), Aug. 24-28, 2015

 Modified MAR reference model describes the
universal workflow for any MAR service
◦ Enhanced model of the MAR reference model, which is the
proposal of international standard(ISO ISO/IEC CD 18521-
3)
 to provide the generic framework for the MAR system
 to promotes the interoperability of individual MAR applications

 ISO/IEC CD 18039

External
Services
User profile
(Experience,
Knowledge,
Behavior)
Simulator
(Event, Space)
Renderer
Conceptualized PoIs
User
Interface
MAR Scene
(Events, Targets, …)
Environment (or
wearable) Sensors
for Real World
Capturer
Internet of Thing
(IoT)
Sensors
Sensors
GPS
Compass
Gyro sensor
Personal Device
Embedded
Camera
Media
Assets
MAR Content
Virtual
Object
CHE
Information
Physical
World
Related MAR Contents
Open API
Physical World
User
User
Input
User
Command
Enhanced
Experience
MAR
Visualization
Recognition Data
MAR Anchor
Selected PoI
Context Analyzer
PoI Analyzer
User Localization
View Point Setting
PoI Analyzing
Context Processor
Context Integration
Context Inference
Context Management
Recognized
PoIs
User Context
Sensor Data
PoI Recognition
Data

 Input : Physical World
 Output
◦ Sensor Data (To Context Analyzer)
◦ Physical World (Personal Device Display)
 Sub Module
◦ Environment Sensor: Sensors in real world
and Internet of Thing(IoT) capture the
status of the Real world that related with
user’s task that possesses potential
applicability
◦ Personal Device Embedded: capture the
information of user’s status such as
location, view point, heading direction
which can be directly exploited in PoI
recognition
Environment (or
wearable) Sensors
for Real world
capturer
Internet of Thing
(IoT)
Sensors
Sensors
GPS
Compass
Gyro sensor
Personal Device
Embedded
Camera
Context analyzer Personal
Device
Display
Physical World
Sensor Data
Physical
World

 User Profile: set of features of the
user such as experience, knowledge,
and behavior
 Input : User
 Output
◦ User Context : User’s information
related with MAR service that can be
extracted from the features of user,
i.e. user profile. User Context is
provided to the context analyzer for
adaptive service.
User profile
(experience,
knowledge,
behavior)
Context Analyzer
User
User
Context

 Context analyzer : the core component that
takes charge of background process for
MAR service
 Input
◦ For PoI Analyzer
 Sensor Data
 PoI Recognition Data : Instances of the PoI
Recognition class for recognizing candidate PoIs
◦ For Context Processor
 User Context
 Ongoing
◦ Recognized PoIs : Instances of PoI class that
are for PoIs recognized in PoI Analyzer
 Output
◦ Contextualized PoIs : Filtered Recognized PoIs
according to user context in Context Processor
MAR execution engine
Contextualized PoIs
Context Analyzer
PoI Analyzer
User Localization
View Point Setting
PoI Analyzing
Context Processor
Context Integration
Context Inference
Context Management
Recognized
PoIs
User profile
User
Context
Sensors
Sensor
Data
Recognition
Data
PoI Recognition
Data

 Input
◦ Contextualized PoIs : PoIs that are candidates to
visualize in MAR Execution Engine
◦ Related MAR content : Instances of MAR Content
class containing information of cultural heritage
entity, media asset and virtual object that is called by
MAR Anchor instance according to the instances of
Selected PoI
◦ User Commend: Commend to control MAR service
that is entered from the user interface on the
personal device display
 Output
◦ MAR visualization: Result of the rendering and
simulation process in MAR execution Engine.
◦ Open API: Enables the service to be utilized in
external services
External
Services
Simulator
(event, space)
Renderer
Open API
Personal
Device
Display
Contextualized PoIs
MAR ContentsMAR
Anchor
Selected
PoI
Related
MAR Contents
Context Analyzer
MAR
Visualization
User
Command

 Input
◦ Physical World: Background of the MAR Scene to
be augmented with MAR visualization
◦ MAR Visualization: Result of visualization process
of the PoI in MAR execution engine as response
of user’s input
◦ User input: Input of user to interact with the
MAR Scene
 Output
◦ Enhanced Experience: Terminal goal of the
whole MAR reference model that is provided to
user
◦ User Commend: Instruction converted from user
input through user interface to control MAR
visualization
User
Interface
MAR Scene
(events, targets, …)
Enhanced
Experience
Sensors
Physical
World
MAR Execution
Engine
User
User
Input
User
User
Commend
MAR
Execution
Engine
MAR
Visualization

• As implementation of the MAR re
ference model, we are developing
the MAR service in K‐Culture Tim
e Machine project that provide pe
rsonalized MAR storytelling of the
historical site in Korea

Contextualized PoIs
Context Analyzer
PoI Analyzer
User Localization
View Point Setting
PoI Analyzing
Context Processor
Context Integration
Context Inference
Context Management
Recognized
PoIs
User profile
User
Context
Sensors
Sensor
Data
Recognition
Data
PoI Recognition
Data
User
Recognized
PoIs

Contextualized PoIs
Context Analyzer
PoI Analyzer
User Localization
View Point Setting
PoI Analyzing
Context Processor
Context Integration
Context Inference
Context Management
Recognized
PoIs
User profile
User
Context
Sensors
Sensor
Data
Recognition
Data
PoI Recognition
Data
Time
Machine
Contextualized
PoIs

Simulator
(event, space)
Renderer
Selected
PoI
Related
MAR
Contents
Contextualized PoIs
MAR ContentsMAR
Anchor
Selected
PoI
Related
MAR Contents
Context Analyzer
External
Services
Open API
Personal
Device
Display
MAR
Visualization
User
Command

External
Services
Open API
Selected
Contents
Personal
Device
Display
MAR
Visualization
User
Command
MAR
Visualization
Simulator
(event, space)
Renderer
Contextualized PoIs
MAR ContentsMAR
Anchor
Selected
PoI
Related
MAR Contents
Context Analyzer

Metadata representation for outdoor AR services

Recommended

Recommended

More Related Content

Similar to Metadata representation for outdoor AR services

Similar to Metadata representation for outdoor AR services (20)

More from Woontack Woo

More from Woontack Woo (20)

Recently uploaded

Recently uploaded (20)

Metadata representation for outdoor AR services