ODF and SVG: Evolving Standards for the Future and SVG: Evolving Standards for the Future Joseph Pally ZCubes, Inc. © 2009 ZCubes, Inc. 2 WWW – The Revolution •1991- • Tim Berners-Lee

ODF and SVG: ODF and SVG: ODF and SVG: ODF and SVG: ODF and SVG: ODF and SVG: ODF and SVG: ODF and SVG:

Evolving Standards Evolving Standards Evolving Standards Evolving Standards Evolving Standards Evolving Standards Evolving Standards Evolving Standards

for the Futurefor the Futurefor the Futurefor the Futurefor the Futurefor the Futurefor the Futurefor the Future

Joseph Pally

ZCubes, Inc.

2© 2009 ZCubes, Inc.

WWW – The Revolution

• 1991- http://info.cern.ch/hypertext/WWW/TheProject.html• Tim Berners-Lee

Charles Goldfarb

Steve Jobs

Vint Cerf




Generations of the web

Web 3.2 - Immersive Web

Web 3.5 - Learning Web

Web 4.0 - Knowledge Web

Intelligent Immersive Imagion

2011-2015

2014-2020

2020-2025III

Web 3.0Semantic Web/Omni-Functional Web

Giant Global Graph

2006-2011

GGG

Web 2.0Community Web

Constellations of Connected Communities

2001-2007

CCC

Web 1.0Commerce Web

World Wide Web

1997-2002

Web 0.0Library of Information

1991-1996

WWW


Web 3.0

• "People keep asking what Web 3.0 is," Berners-Lee said. "I think maybe when you've got

an overlay of scalable vector graphics –everything rippling and folding and looking misty - on Web 2.0 and access to a semantic Web integrated across a huge space of data, you'll have access to an unbelievable data resource."

A 'more revolutionary' Web, New York Times, Tuesday, May 23,

2006


First Vector Graphics System

• Semi-Automatic

Ground

Environment

(SAGE)

• 1950s


Vector Graphics formats

• Markup Languages

– VML – 1998, Microsoft, Macromedia, etc.

– PGML (Precision Graphics Markup Language) from

Adobe Systems and Sun Microsystems.

– SVG (Scalable Vector Graphics)

• evolved out of from a common W3C workgroup.


VML vs. SVG

• VML

– <v:oval style="left:0;top:0;width:100;height:50"

fillcolor="blue"

stroked="f"/>

• More DOM/CSS oriented

• In SVG, this may look like:

– <ellipse cx="50" cy="25" rx="50" ry="25" fill="blue"

stroke="none" />

• Different style than DOM


Office Formats

• OOXML (Office Open XML) – from 2000

– When Microsoft started to provide Excel files in XML format.

– It was accepted by ECMA as a standard in 2006, followed by

international acceptance as ISO/IEC 29500:2008.

– Finalized 2006

• ODF (OpenDocument Format) – 2002

– Developed under the OASIS industry consortium

– Based on Star Office XML format from 1999

– Given to Open Source community in 2000.

– Finalized in ~2006 (Sun, IBM, etc.)


Comparison

Draw/SVGDrawingML/VMLVector

PNGJPEGRaster

Fully Compliant

Implementations

Conforming

Implementations

Patent Licenses

covers

odt, ods, odp,

odg, odf

docx, xlsx, pptxExtensions

ODFOOXML


Packaging – OOXML

• ZIP

– Open Packaging Convention

• Rename file as .zip and open in Zip Programs to view


Packaging – ODF

• ZIP

– ODF Package


Packages

• Both OOXML and ODF

structure:

– Simple Mini–Websites

• Future consolidation

into .htz ?• Expansion of

HTML/CSS/etc. standards

to accommodate DOC

structures?

• HTML5/CSS3?


Vision: 1999

• 1989, Age of Intelligent Machines, Ray Kurzweil

accurately forecast that:

“By the end of the 1990s, many documents

would exist solely in computers and on the

Internet, and that they would commonly be

embedded with sounds, animations, and videos

that would inhibit their transfer to paper

format.”


Vision: 2009

• 1999, Age of Spiritual Machines, Ray Kurzweil

predicted that:

– In 2009, “The majority of reading is done on displays,

although the ‘installed base’ of paper documents is

still formidable.

– The generation of paper documents is dwindling,

however, as the books and other papers of largely

twentieth-century vintage are being rapidly scanned

and stored. Documents circa 2009 routinely include

embedded moving images and sounds”


Vision: 2019

• 1999, Age of Spiritual Machines, Ray Kurzweil

predicts that:

In 2019, “Thin, lightweight, handheld displays

with very high resolutions are the preferred

means for viewing documents.The aforementioned computer eyeglasses and contact lenses are also used

for this same purpose, and all download the information wirelessly.

• Computers have made paper books and

documents almost completely obsolete.


What is a Document?

– A document (noun) is a bounded physical representation of body of information designed with the capacity (and usually intent) to communicate. A document may manifest symbolic, diagrammatic or sensory-representational information. To document (verb) is to produce a document

artifact by collecting and representing information. In prototypical usage, a document is understood as a paper artifact, containing information in the form of ink marks. Increasingly documents are also understood as digital artifacts.

• Expressions!


Forms of Documents

• Albums

• Paintings

• Forms

• CAD Drawings

• Flowcharts

• Audio

• Video

• Reports

• Word Processing

Documents

• Presentations

• Spreadsheets

• Bitmaps

• Web Pages


Actions in a Doc

• Collecting

• Representing

• Sharing

• Storing

• Printing

• Designing

• Constructing

• Thinking

• Immersing

• Analyzing

• Experiencing

• Expressing

• Calculating

• Immersive Interactive

Analysis & Viewing


Today’s Applications

• Segmented Interfaces

– Separate pieces with shallow integration

• Generally Mono–functional

– Clunky Interaction

– Copy/Paste, OLE, etc.


Omni-Functionality

• Omni-functionality introduces the concept of

the availability of any functionality that the

users require – without regard to the sequence

of creation or complexity.

– The nature of a software platform to provide all

functionalities to a user

• No specific entry point

• No specialization

– Infinite depth

– Extensible


Omni-Functionality

– Creates:

• Interactive

Intelligent

Documents

Immense Functionality Provided by

Web Delivery and

Seamless FunctionalityOmni

Functional

Platform


Intelligent Documents

• (a) active,

• (b) immersive,

• (c) interactive,

• (d) web-compliant,

• (e) seamless,

• (f) application-agnostic,

• (g) data-agnostic,

• (h) omni-functional,

• (i) shareable,

• (j) viewable,

• (k) editable,

• (l) function-agnostic,

• (m) feature-deep,

• (n) calculation-aware,

• (o) graphic-aware,

• (p) standards-based and

• (q) infinitely extensible.

““It is just as important It is just as important to be able to edit the Web to be able to edit the Web

as browse it.as browse it.””

- Weaving the Web, Tim Berners-Lee, The inventor of the World Wide Web.


DocumentContent Categories

• Each element in a document falls into:

– Flow content

– Phrasing content

– Embedded content

– Sectioning content

– Heading content

– Metadata content

– Interactive content

– Other – Recursive/Transparent

• Conventional and Web documents

•Needs are same


Content Categories: that can contain SVG

• Flow Content– Most elements that are used in the body of documents and applications.

• Phrasing Content– Text of the document (paragraphs), as well as elements that mark up that text at the intra-paragraph level

• Embedded Content– Content that imports another resource into the document, or content from another vocabulary that is inserted into the document.


Two roles of Vector Graphics in documents

• The overall design of vector graphics standards

must keep these several uses of elements and

their scope and role in the total document

rendering and object model.

– Need to work with the global object model in the

Flow and Phrasing Content scenarios.

• For example, filters, z–index layering, transitions,

animations, SMIL, etc.

– But these can be treated independent in the case of

embedded content.

• Helper applications


Browser Support

• SVG

– IE does not support

• Compatibility Solutions for IE

– SVG in IE

• SVG to VML conversion in IE

• SVG embedding in Flash/Shockwave (SVGWeb)

– Raphael and other Javascript Libraries


Bigger problem

– SVG not supported in text/html

• Firefox (in some others too)

– Supports only in XHTML mode

» Serious issue that simple HTML does not support SVG

» Inline SVG

» Creates unwanted issues for implementers

» Embedded Content is handled well by other

formats/techniques


Stifling standards

• Web site designers

are opting en masse

for less restrictive

standards!

0.01ISO/IEC 15445:2000 ("ISO

HTML")

0.04XHTML Basic 1.0

0.012HTML 2.0

0.049HTML 4.0 Frameset

0.187HTML 4.0 Strict

0.1101XHTML 1.0 Frameset

0.4351HTML 3.2

0.4379XHTML 1.1

0.4399HTML 4.01 Frameset

0.5511HTML 4.01 Strict

1.51,467XHTML 1.0 Strict

5.95,885HTML 4.0 Transitional

17.617,557HTML 4.01 Transitional

22.022,043No DOCTYPE

51.251,163XHTML 1.0 Transitional

(text/html)

%Web sitesDocument type

Table 2. Document types found on the top 100,000 Web sites.*

*Is HTML in a Race to the Bottom? A Large-

Scale Survey and Analysis of Conformance

to W3C Standards

by Patricia Beatty, Scott Dick, and James

Miller • University of Alberta

Mar./Apr. 2008http://dsonline.computer.org/portal/site/dsonline/

menuitem.3a529f3832e8f1e13587e0606bcd45f3/inde

x.jsp?&pName=dso_print_only&TheCat=&path=dsonlin

e/2008/04&file=w2std.xml


DO NOT USE SVG

Hello HTML WG,

While it is encouraging that SVG in text/html is being discussed[1], we feel that the proposal tries to change the SVG syntax in a way that is incompatible with all implementations to date. We feel that such change is outside of the HTML Working Group's charter and request that it be removed from the text/html specification pending further research into proposed solutions, in order to avoid premature implementation.

We are happy to make rapid progress on allowing SVG in text/html while maximizing compatibility with the wide range of deployed SVG authoring tools and renderers.

On behalf of the SVG Working Group,

XXXXX

Architect and Manager, SVG Technologies

XXXX, W3C SVG Working Group

Tue, 15 Apr 2008 06:06:36 -0500


Ok, we will not!

• Reply:

– “I have removed SVG support from the HTML parser

specification as per your request. (I have left MathML support in

the specification.) ….Proposals should be written in terms of

the HTML parser model if at all possible. Please also note that

we are heavily constrained by existing legacy markup and

implementations, as well as by the somewhat unintuitive

behaviour of Web authors. In developing the current text I

considered a great deal of possible options, and could not find

one more compatible with existing SVG UAs that still fit in the

aforementioned constraints.” – 15 April 2008


HTML DOM is paramount

• SVG on the web should not be at the mercy of

embedded or isolated systems

– Result: No SVG in 97% of pages

• Needs are different!

– Keep issues separate for different platforms and

content category.

• Build compatibility from the base platform of intended use


ODF and SVG

• <office:drawing><draw:page draw:name="page1" draw:style-name="dp1"

draw:master-page-name="Default"><draw:rect draw:style-name="gr1" draw:text-style-name="P1"draw:layer="layout"svg:width="9.525cm" svg:height="8.89cm" svg:x="4.175cm"

svg:y="4.81cm"><text:p/>

</draw:rect><draw:ellipse draw:style-name="gr1" draw:text-style-name="P1" draw:layer="layout"svg:width="9.525cm" svg:height="10.16cm" svg:x="7.985cm"svg:y="9.89cm"><text:p/>

</draw:ellipse></draw:page>

</office:drawing>


Issues in full integraton into ODF

• Only the following used in a secondary way (svg:xxx)– accent-height,alphabetic,ascent,bbox,cap-height, cx,cy,d,definition-src,desc,descent,fill-rule,font-face-format, font-face-name,font-face-src,font-face-uri,font-family, font-size,font-stretch,font-style, font-variant,font-weight, fx,fy,gradientTransform, gradientUnits,hanging,height,ideographic,linearGradient,mathematical, name,offset,origin, overline-position,overline-thickness, panose-1,path,r,radialGradient,rx,ry, slope,spreadMethod,stemh, stemv,stop,stop-color, stop-opacity, strikethrough-position,strikethrough-thickness,string, stroke-color,stroke-linecap,stroke-opacity, stroke-width, title,type,underline-position, underline-thickness, unicode-range,units-per-em, v-alphabetic,v-hanging, v-ideographic,viewBox, v-mathematical,width,widths, x,x1,x2,x-height,y,y1, and y2.

• Unavailability of key items– Many parameters in ODF Draw

• Z–index

– Unavailability of advanced features such as 3D elements


ODF z–Index

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

18.234 draw:z-indexThe draw:z-index attribute defines a rendering order for shapes

in a document instance. Shapes are rendered in the order in which they appear in the document in the absence of this attribute.

The draw:z-indexattribute is usable with the following elements: <dr3d:cube>9.5.3, <dr3d:extrude>9.5.5, <dr3d:rotate>9.5.6, <dr3d:scene>9.5.1, <dr3d:sphere>9.5.4, <draw:caption>9.3.11, <draw:circle>9.3.8, <draw:connector>9.3.10, <draw:control>9.3.13, <draw:custom-shape>9.6.1, <draw:ellipse>9.3.9, <draw:frame>9.4.2, <draw:g>9.3.15, <draw:line>9.3.3, <draw:measure>9.3.12, <draw:page-thumbnail>9.3.14, <draw:path>9.3.7, <draw:polygon>9.3.5, <draw:polyline>9.3.4, <draw:rect>9.3.2, <draw:regular-polygon>9.3.6 and <office:annotation>13.1.

The draw:z-indexattribute has the data type nonNegativeInteger

OpenDocument-v1.2-part1-cd03.odt 30 July 2009 Copyright © OASIS Open 2002 - 2009. All Rights Reserved. Page 391 of 801: OpenDocument-v1.2-part1-cd03.pdf

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––


Missing Pieces

• z–index

– A major issue from an editing and interaction point of

view

• Prevents full friction-free native interaction with the DOM.

• Intra–group z–index still need to be with SVG,

though the rest of the DOM can work separately

– Not having z–Index is a major defect in the standards

• Solutions like Copy/Paste, DOM movements etc. are clunky

and unacceptable solutions

– VML, AutoCAD, etc. does it!


Double standards

Please use SVG

–Our goal is to convince the OpenDocument TC to mandate full native support for

SVG 1.1 and SVG Tiny 1.2 in ODF-Next. Important things for us to note include:

–we are not challenging the existing support for Draw/Impress; SVG would

supplement that

–we are not proposing that SVG replace the whole format

–we are willing to adapt SVG to meet their needs

–there are substantial network effect benefits to SVG

–there are people inside and outside the dedicated SVG community who want to see

this happen and who would benefit

• 06:14, 26 March 2009


Future proofing

• Documents are no longer about page layouts in 2D!

• Need to move into 3D aspects

– Lighting, Extrusion, etc.

– DrawingML/VML have these

• Powerful expression possibilities

• Interfacing need to be considered with languages and

APIs like X3D, VRML, 3DMLW, O3D, OpenGL, U3D,

COLLADA, etc.

– Flash already does

– Why should people use SVG instead of Flash (with some script?)


Need to make deeper & powerful specification

– Creates competitiveness issues for adopters

– If the standard is not sufficient, people will embrace and then

replace it.

• Embrace and Extend

– Better than Embrace and Stifle

• Need to have feature to feature match with VML/DrawingML

– Otherwise OOXML+DrawingML and ODF+SVG

will drift in different directions

– Users will loose

– Need to be future oriented than just backward compatible

– Future interfaces 3D oriented

• SVG needs to transform to this

• Must become a entirely powerful substrate for further innovation


SVG Next

• “ODF Next”

– Comments are being invited to the next version of

ODF

• Need to consider an SVG Next revision

– Separate Embedded/Standalone vs.

“Within–an–External DOM” behavior

• More proactive, future–oriented approach is

needed

– Some of the comments gather dust over years with no

action


HTML + SVG

• Next version of HTML

– HTML5 has high expectation of SVG

• HTML5 Timeline• Starting 2003; First W3C Working Draft in October 2007; Last

Call Working Draft in October 2009; Call for contributions for

the test suite in 2011; Candidate Recommendation in 2012;

First draft of test suite in 2012; Second draft of test suite in

2015; Final version of test suite in 2019; Reissued Last Call

Working Draft in 2020; Proposed Recommendation in 2022 » IH, November 2006


MACHINE vs. Man


HTML5 Timeline

• In reality we can expect shorter timelines with

HTML5

– Human Genome Example

– Since browser wars are heating up again!!!

• Exciting!


Recommendations

• Focus on the web first– Everything else second

– Browser is the Editor

• Browser Pages and Documents– Needs are similar

• Make ODF+SVG and OOXML+DrawingML+VMLas close as possible in features– Should have no feature–gaps

• Avoid backward compatibility focus– Be very future oriented


• “Hold yourself responsible for a higher standard

than anyone else expects of you. Never excuse

yourself.”– Henry Ward Beecher

OMNIOMNI--FUNCTIONALITYFUNCTIONALITY


So what is an Omni–FunctionalSoftware?


Many Facets of ZCubes


Art – Kids to Professionals


Graphics


Advanced Text


Special Effects


Handwriting


Simple Construction and Simplicity

• Drag-Drop Enabled


Calculations

• 2000 Functions

– Other calculation

software does

not exceed

200–400

• Data can be of

ANY type

– Pictures

– Videos

– Complex Numbers

– Arrays


Slides & Images


Greeting Cards


Albums


Web Pages


Effects and URL Loops


Demo

• ZCubes Live Tutorials

– Watch and Learn:

– Contact [email protected]

– 832–858–2633

– Daily & Weekends

• 1 Hour Segments


Questions

• [email protected]

– http://www.zcubes.com

• Fail Fast, Move Faster– http://www.failfastmovefaster.com

• The Thinking Things

– www.TheThinkingThings.com

““Difficult to see, Difficult to see,

the future isthe future is…”…”

Yoda


• “Praise those of your critics for whom nothing is

up to standard.”– Dag Hammarskjold

(Swedish Statesman and United Nations official, 1905-1961)