Towards collaborative Blender design through annotation sharing

Size: px

Start display at page:

Download "Towards collaborative Blender design through annotation sharing"

Georgiana Hines
6 years ago
Views:

1 Towards collaborative Blender design through annotation sharing Thierry Jacquin, Jean-Pierre Chanod Document Structure Xerox Research Centre Europe

2 Presentation Overview Introduction Creative intent in project lifecycle Three steps towards sustainable intent expression Blender perspective

3 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

4 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

5 Visualizing large features sets (3) A α O ( N 6 N 9 ) Initial visualisation Dimension reduction View optimisation

6 Wikipedix : Wikipedia links graph Similarity Graph Predictions True labels Links-TFIDFcontent+0.5 Links+TFIDFContent+0.2, zoom 2

7 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

8 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

9 Creative intent in project lifecycle Ideas, Domain knowledge, Creativity Environment, Cost & time, Technologies

10 Creative intent in project lifecycle Creative intent Ideas, Domain knowledge, Creativity Andy Goralczyk Design Environment, Cost & time, Technologies

11 Creative intent in project lifecycle Creative intent Ideas, Domain knowledge, Creativity Andy Goralczyk Negotiation Design Environment, Cost & time, Technologies

12 Creative intent in project lifecycle Creative intent Ideas, Domain knowledge, Creativity Andy Goralczyk Negotiation Project outcome Design Environment, Cost & time, Technologies

Creative intent in project lifecycle Towards expressing the

sustainable intent expression grows as agility becomes

management (competence, knowledge and processes)

13 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

14 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

15 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

16 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

17 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

18 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

19 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

means to graphically manipulate abstract representations of objects relevant to the application domain provides immediate design feedback interpretation (player/builder)

20 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

21 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

22 MDA from the task model TASK MODELING SPACE Task model Task models are created via a task model editor Modeling is based on a DSL dedicated to tasks and relations

23 MDA from the task model TASK MODELING SPACE GENERATORS Design viewpoint Task model Annotation tools Annotation renderer Creator viewpoint Task models are created via a task model editor Modeling is based on a DSL dedicated to tasks and relations

MDA from the task model TASK MODELING SPACE ANNOTATION SPACE GENERATORS Design viewpoint Task model Annotation tools Annotation renderer Creator viewpoint Task models are

24 MDA from the task model TASK MODELING SPACE ANNOTATION SPACE GENERATORS Design viewpoint Task model Annotation tools Annotation renderer Creator viewpoint Task models are created via a task model editor Modeling is based on a DSL dedicated to tasks and relations Contributors can create, visualize, update and manage annotations from their viewpoints

25 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 Reference viewpoint Import/export Import/export Design viewpoint Creator viewpoint

26 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

27 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

28 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

29 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

30 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

31 The XeProc metamodel The XeProc metamodel is described by a UML class diagram XeProc models specify logical XML document processing pipelines

A scenario towards semantic annotation 1) Research: -

requirements from customer: semantic annotation - Human

annotation of XML documents 3) Extended service: - Design

annotation interface - Augment XML processing with

32 A scenario towards semantic 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 3) Extended service: - Design the semantic model with the customer - Generate the annotation interface - Augment XML processing with semantic models SEMANTIC MODEL Doc. Processing DSL Human annotation Automated annotation Demo

White Paper. EVERY THING CONNECTED How Web Object Technology Is Putting Every Physical Thing On The Web

White Paper. EVERY THING CONNECTED How Web Object Technology Is Putting Every Physical Thing On The Web White Paper EVERY THING CONNECTED Is Putting Every Physical Thing Every Thing Connected The Internet of Things a term first used by technology visionaries at the AUTO-ID Labs at MIT in the 90s 1 has received