Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Towards collaborative Blender design through annotation sharing
Thierry Jacquin, Jean-Pierre ChanodDocument Structure
Xerox Research Centre Europe
Presentation Overview
Introduction
Creative intent in project lifecycle
Three steps towards sustainable intent expression
Blender perspective
XRCE, Document Structure
Nothing like Blender : documents, document collections, Web pages
Research directions
The Document as a trace of social relations reconstructed by computer systems*
Document understanding and processing • Methods and technologies to analyse document collections and
compute information relevant to domain-specific contexts of use
Document network understanding• Methods and technologies to discover interactions, patterns and
trends involving actors and communities. within large collections of inter-linked documents
Qualification• Methods and technologies to qualify XML resources in
distributed/collective ecosystems
* Form, Sign and Medium, as Reformulated for Electronic Documents http://archivesic.ccsd.cnrs.fr/docs/00/06/22/28/PDF/sic_00000594.pdf
Visualizing large features sets (3)
)( 96 NNO −α
A
Dimension reduction View optimisationInitial visualisation
Wikipedix : Wikipedia links graph
Similarity GraphPredictions True labels
Links-TFIDFcontent+0.5 Links+TFIDFContent+0.2 , zoom 2
Digital Preservation
Ensuring future accessibility and usability of data and information
Preserving high volumes of digital content over time
Keeping track of evolving semantics and usage context
Safeguarding integrity, authenticity and long term accessibility over time
Integrated Project co-financed by the European Union Duration 4 years, started 1Q08, 18 partners Three prototypical applications
• digital libraries• industrial design and engineering• e-Science
http://shaman-ip.eu/shaman/
Creative intent in project lifecycle
Ideas, Domain knowledge, Creativity
Environment, Cost & time, Technologies
Creative intent in project lifecycle
Ideas, Domain knowledge, Creativity
Creative intent
Environment, Cost & time, Technologies
Design
Andy Goralczyk
Creative intent in project lifecycle
Ideas, Domain knowledge, Creativity
Creative intent
Environment, Cost & time, Technologies
Design
Negotiation
Andy Goralczyk
Creative intent in project lifecycle
Project outcome
Ideas, Domain knowledge, Creativity
Creative intent
Environment, Cost & time, Technologies
Design
Negotiation
Andy Goralczyk
Creative intent in project lifecycle
Towards expressing the creative intent beyond processes and projects
The value of sustainable intent expression grows as agility becomes critical For project efficiency
For organizations • Asset management (competence, knowledge and processes)
• Interactions with external bodies, partnerships
Environment, Cost & time, Technologies
Three steps towards sustainable intent expression
STEP 0: Traditional IT development outcome Preserve digital objects produced at a given point in time
Hard to keep up and running or reuse because of technology evolution (hw/sw)
Hard to interpret• formats and codes,
• implicit knowledge,
• unmotivated or untraceable decisions,
• evolving and lost semantics,
• lost skills
Struggle to reuse, revive, migrate, emulate, reproduce
Three steps towards sustainable intent expression
STEP 0: Traditional IT development outcome Preserve digital objects produced at a given point in time
Hard to keep up and running or reuse because of technology evolution (hw/sw)
Hard to interpret• formats and codes,
• implicit knowledge,
• unmotivated or untraceable decisions,
• evolving and lost semantics,
• lost skills
Struggle to reuse, revive, migrate, emulate, reproduce
STEP 1: Abstract development through modeled design
Three steps towards sustainable intent expression
STEP 0: Traditional IT development outcome Preserve digital objects produced at a given point in time
Hard to keep up and running or reuse because of technology evolution (hw/sw)
Hard to interpret• formats and codes,
• implicit knowledge,
• unmotivated or untraceable decisions,
• evolving and lost semantics,
• lost skills
Struggle to reuse, revive, migrate, emulate, reproduce
STEP 1: Abstract development through modeled design
STEP 2: Intent expression through project task management
STEP 1: Abstract development through modeled design
Model-based design Symbolic description of objects, irrespective of their specific implementation
Customized for specific domains, enabling domain-relevant concept descriptions
Well adapted to SOA Efficiency,
Task distribution,
Readability
Provides some basic expression of intent through abstraction Less dependency on computing infrastructure/implementation
Abstract development through modeled design: our experience
XeProc, a model for a very focused domain: document understanding through XML processing
XeProc designer to create domain objects XML pipes, doc processing with features and relations
… as Blender enables one to create meshes with their attributes
Abstract development through modeled design: our experience
XeProc, a model for a very focused domain: document understanding through XML processing
XeProc designer to create domain objects XML pipes, doc processing with features and relations
… as Blender enables one to create meshes with their attributes
The XeProc designer• provides means to graphically manipulate abstract
representations of objects relevant to the application domain
• provides immediate design feedback
– interpretation (player/builder) over reference collections
– validation
– visual error feedback
• Generated through EMF/GMF in Eclipse
Abstract development through modeled design: our experience
XeProc, a model for a very focused domain: document understanding through XML processing
XeProc designer to create domain objects XML pipes, doc processing with features and relations
… as Blender enables one to create meshes with their attributes
The XeProc designer• provides means to graphically manipulate abstract
representations of objects relevant to the application domain
• provides immediate design feedback
– interpretation (player/builder) over reference collections
– validation
– visual error feedback
• Generated through EMF/GMF in Eclipse
At this stage, one preserves the designer results but not the design process
STEP 2: Intent expression through project task management
Intent is reflected by interactions between actors across their different roles
Proposed approach: Traditional task management as a means to track interactions Interactions captured through selected tasks
Tasks are instances of an agreed task model• Objectives
• Requirements
• Project development
• Q/A
Task descriptions anchored to objects under development Anchoring makes tasks interpretation more explicit
… and facilitates project navigation in task context
Task instantiated as annotations of objects under development A natural medium for content creators and designers
Annotations must support anchoring compatibility with all viewpoints of the project lifecycle
TASK MODELING SPACE
MDA from the task model
Task models are created via a task model editor
Modeling is based on a DSL dedicated to tasks and relations
Task model
TASK MODELING SPACE
MDA from the task model
Annotation tools
Annotation renderer
Design viewpoint
Creator viewpoint
GENERATORS
Task models are created via a task model editor
Modeling is based on a DSL dedicated to tasks and relations
Task model
TASK MODELING SPACE
MDA from the task model
Annotation tools
Annotation renderer
Design viewpoint
Creator viewpoint
ANNOTATION SPACE
GENERATORS
Contributors can create, visualize, update and manage annotations from their viewpoints
Task models are created via a task model editor
Modeling is based on a DSL dedicated to tasks and relations
Task model
Task model, reference viewpoints and mappings
Domain objects are described by a sustainable reference viewpoint• Using an Object Description Language (XML) and an anchoring language (à la XPath)
The task model links to the reference viewpoint : Anchoring methods are associated to tasks as behaviors
Import/export towards multiple viewpoints generated from task/behavior pairs• Annotation edition/rendering/navigation in context: creator/design/target viewpoints
Design viewpoint
Creator viewpoint
Reference viewpoint
Import/export
Import/export
Research directions
A reference Viewpoint for 3D objects Place holders, Groups, Zoning
Animation/interactivity• Temporal dimension in the model
• Actions, triggers, sensors
Attributes, (material, color, size, light, …)
A negotiated task model for Blender projects
Import/export from anchoring behaviors towards project viewpoints Blender designer
External viewers
From storyboard to initial project settings
Backup
Digital preservation
High risk but still little awareness outside focused sectors (libraries, archives, e-science)
The 1086 Domesday Book, instigated by William the Conqueror, is still intact and available to be read by qualified researchers in the Public Record Office. In 1986 the BBC created a new Domesday Book about the state of the nation, costing £2.5 million. It is now unreadable. It contained 25,000 maps, 50,000 pictures, 60 minutes of footage, and millions of words
Julian Jackson, Digital Preservation Coalition
Analogy between the document and 3D worlds
Design domain vs. target usage (visualise, read, play)
Internal structure (source, XML , Bender) vs. external representations (PDFs, 3D scenes)
Technical (designers) vs. content producers (creators, annotators)
source data vs. intent and semantics
Project dev (support requests) vs. persistent intent
Interaction between the two domains: tests involving both communities
The document / 3D parallel
Design (source) Target usage
Doc structure Visu, read docs
Blender struct. Play 3D
Designers, technical content creators,
Support dev., support requests Persistent intent
TESTS
The XeProc metamodelThe XeProc metamodel is described by a UML class diagram
XeProc models specify logical XML document processing pipelines
A scenario towards semantic annotation
3) Extended service:
Demo
SEMANTICMODEL
Doc. ProcessingDSL
Human annotation Automated annotation
1) Research:- Provides document processing through DSL
2) Additional requirements from customer: semantic annotation- Human interface for manual annotation- Automated semantic annotation of XML documents
- Design the semantic model with the customer
- Augment XML processing with semantic models - Generate the annotation interface