DOCSLIB.ORG

SVG) Tiny 1.2 Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Scalable Vector Graphics (SVG) Tiny 1.2 Specification W3C Working Draft 08 December 2005 This version: http://www.w3.org/TR/2005/WD-SVGMobile12-20051207/ Previous version: http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/ Latest version: http://www.w3.org/TR/SVGMobile12/ Editors: Ola Andersson (Ikivo) <[email protected]> Robin Berjon (Expway) <[email protected]> Jon Ferraiolo (Adobe Systems) <[email protected]> Vincent Hardy (Sun Microsystems, Inc.) <[email protected]> Scott Hayman (Research In Motion Limited) Dean Jackson (W3C) <[email protected]> Chris Lilley (W3C) <[email protected]> Craig Northway (Canon, Inc.) <[email protected]> Antoine Quint (Invited Expert) <[email protected]> Authors: See author list Copyright ©2005 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract This specification defines the features and syntax for Scalable Vector Graphics (SVG) Tiny, Version 1.2, a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML. SVG Tiny 1.2 is the baseline profile of SVG, implementable on a range of devices from cellphones and PDAs to desktop and laptop computers, and is the core of SVG 1.2. Other SVG 1.2 specifications will extend this functionality to form supersets (for example, SVG 1.2 Full). Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This is a W3C Last Call Working Draft. If the feedback is positive, the SVG Working Group plans to submit this specification for consideration as a W3C Candidate Recommendation. This is the third Last Call Working Draft for this specification. The second Last Call resulted in a number of comments which all have been addressed by the SVG Working Group, a list of all comments can be found in the Last Call Comments List. The purpose of this third Last Call is to allow reviewers to verify that their comments have been included as agreed by the SVG Working Group, it is not intended as a new, general review period. Comments for this specification should have a subject starting with the prefix '[SVGMobile12]' followed by the number of the comment from the Last Call Comments List. E.g. "[SVGMobile12], SVGT12-4, subject here". Please send them to [email protected], the public email list for issues related to SVG. This list is archived and acceptance of this archiving policy is requested automatically upon first post. To subscribe to this list send an email to [email protected] with the word subscribe in the subject line. Comments are accepted until 28 December 2005. This document has been produced by the SVG Working Group as part of the W3C Graphics Activity, following the procedures set out for the W3C Process. The authors of this document are listed at the end in the Author List section. The patent policy for this document is the 5 February 2004 W3C Patent Policy. Patent disclosures relevant to this specification may be found on the SVG Working Group's patent disclosure page. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy. Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. Available languages The English version of this specification is the only normative version. However, for translations in other languages see http://www.w3.org/Graphics/SVG/svg-updates/translations.html. Table of Contents ● 1 Introduction ● 2 Concepts ● 3 Rendering Model ● 4 Basic Data Types and Color Keywords ● 5 Document Structure ● 6 Styling ● 7 Coordinate Systems, Transformations and Units ● 8 Paths ● 9 Basic Shapes ● 10 Text ● 11 Painting: Filling, Stroking, Colors and Paint Servers ● 12 Multimedia ● 13 Interactivity ● 14 Linking ● 15 Scripting ● 16 Animation ● 17 Fonts ● 18 Metadata ● 19 Extensibility ● Appendix A The SVG Micro DOM (uDOM) ● Appendix B IDL Definitions ● Appendix C Implementation Requirements ● Appendix D Conformance Criteria ● Appendix E Conformance to QA Framework Specification Guidelines ● Appendix F Accessibility Support ● Appendix G Internationalization Support ● Appendix H JPEG Support ● Appendix I Minimizing SVG File Sizes ● Appendix J Feature strings ● Appendix K Element Table ● Appendix L Attribute and Property Tables ● Appendix M Media Type registration for image/svg+xml ● Appendix N RelaxNG Schema for SVG Tiny 1.2 ● Appendix O References ● Appendix P Change History Full Table of Contents The authors of the SVG Tiny 1.2 specification are the people who participated in the SVG Working Group as members or alternates. Authors: ❍ Ola Andersson, Ikivo ❍ Phil Armstrong, Corel Corporation ❍ Henric Axelsson, Ericsson AB ❍ Selim Balcısoy, Nokia ❍ Robin Berjon, Expway ❍ Benoît Bézaire, Itedo (formerly Corel Corporation) ❍ John Bowler, Microsoft Corporation ❍ Gordon Bowman, Corel Corporation ❍ Craig Brown, Canon Information Systems Research Australia ❍ Mike Bultrowicz, Savage Software ❍ Tolga Çapin, Nokia ❍ Milt Capsimalis, Autodesk Inc. ❍ Mathias Larsson Carlander, Ericsson AB ❍ Jakob Cederquist, Ikivo ❍ Suresh Chitturi, Nokia ❍ Charilaos Christopoulos, Ericsson AB ❍ Richard Cohn, Adobe Systems Inc. ❍ Lee Cole, Quark ❍ Cyril Concolato, Groupe des Ecoles des Télécommunications (GET) ❍ Don Cone, America Online Inc. ❍ Alex Danilo, Canon Information Systems Research Australia ❍ Thomas DeWeese, Eastman Kodak ❍ David Dodds, Lexica ❍ Andrew Donoho, IBM ❍ David Duce, Oxford Brookes University ❍ Jean-Claude Dufourd, Streamezzo (formerly GET) ❍ Jerry Evans, Sun Microsystems ❍ Jon Ferraiolo, Adobe Systems Inc. ❍ Darryl Fuller, Schema Software ❍ 藤沢 淳 (FUJISAWA Jun), Canon ❍ Scott Furman, Netscape Communications Corporation ❍ Brent Getlin, Macromedia ❍ Christophe Gillette, Motorola (formerly BitFlash) ❍ Peter Graffagnino, Apple ❍ Rick Graham, BitFlash ❍ Vincent Hardy, Sun Microsystems Inc. ❍ 端山 貴也 (HAYAMA Takanari), KDDI Research Labs ❍ Scott Hayman, Research In Motion Limited ❍ Stephane Heintz, BitFlash ❍ Lofton Henderson, OASIS ❍ Ivan Herman, W3C ❍ Jan Christian Herlitz, Excosoft ❍ Alan Hester, Xerox Corporation ❍ Bob Hopgood, RAL (CCLRC) ❍ Bin Hu, Motorola ❍ Michael Ingrassia, Nokia ❍ 石川 雅康 (ISHIKAWA Masayasu), W3C ❍ Dean Jackson, W3C (W3C Team Contact) ❍ Christophe Jolif, ILOG S.A. ❍ Lee Klosterman, Hewlett-Packard ❍ 小林 亜令 (KOBAYASHI Arei), KDDI Research Labs ❍ Thierry Kormann, ILOG S.A. ❍ Yuri Khramov, Schema Software ❍ Kelvin Lawrence, IBM ❍ Håkon Lie, Opera ❍ Chris Lilley, W3C (Working Group Chair) ❍ Vincent Mahe, France Telecom ❍ Philip Mansfield, Schema Software ❍ Kevin McCluskey, Netscape Communications Corporation ❍ 水口 充 (MINAKUCHI Mitsuru), Sharp Corporation ❍ Luc Minnebo, Agfa-Gevaert N.V. ❍ Jean-Claude Moissinac, Groupe des Ecoles des Télécommunications (GET) ❍ Craig Northway, Canon Information Systems Research Australia ❍ Tuan Nguyen, Microsoft Corporation ❍ 小野 修一郎 (ONO Shuichiro), Sharp Corporation ❍ Lars Piepel, Vodafone ❍ Antoine Quint, Fuchsia Design (formerly of ILOG) ❍ ••••••• •••• (Nandini Ramani), Sun Microsystems ❍ Bruno David Simões Rodrigues, Vodafone ❍ 相良 毅 (SAGARA Takeshi), KDDI Research Labs ❍ Troy Sandal, Visio Corporation ❍ Peter Santangeli, Macromedia ❍ Sebastian Schnitzenbaumer, SAP AG ❍ Haroon Sheikh, Corel Corporation ❍ Brad Sipes, Ikivo ❍ Andrew Sledd, Ikivo ❍ Пётр Соротокин (Peter Sorotokin), Adobe Systems Inc. ❍ Gavriel State, Corel Corporation ❍ Robert Stevahn, Hewlett-Packard ❍ Timothy Thompson, Eastman Kodak ❍ 上田 宏高 (UEDA Hirotaka), Sharp Corporation ❍ Rick Yardumian, Canon Development Americas ❍ Charles Ying, Openwave Systems Inc. ❍ Shenxue Zhou, Quark Acknowledgments The SVG Working Group would like to acknowledge the many people outside of the SVG Working Group who help with the process of developing the SVG specification. These people are too numerous to list individually. They include but are not limited to the early implementers of the SVG languages (including viewers, authoring tools, and server-side transcoders), developers of SVG content, people who have contributed on the [email protected] and svg- [email protected] email lists, other Working Groups at the W3C, and the W3C Team. SVG is truly a cooperative effort between the SVG Working Group, the rest of the W3C, and the public and benefits greatly from the pioneering work of early implementers and content developers, feedback from the public. SVG Tiny 1.2 - 20051208 TopContentsNextElementsAttributes 1 Introduction Contents ● 1.1 About SVG ● 1.2 SVG Tiny 1.2 ❍ 1.2.1 Modularization ❍ 1.2.2 Element and Attribute collections ❍ 1.2.3 Profiling the SVG specification ● 1.3 Defining an SVG Tiny 1.2 document ● 1.4 SVG MIME type, file name extension and Macintosh file type ● 1.5 Compatibility with Other Standards Efforts ● 1.6 Definitions 1.1 About SVG SVG is a language for describing two-dimensional graphics in XML [XML11]. SVG allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), multimedia (such as raster images and video) and text. Graphical objects can be grouped, styled, transformed
Recommended publications
  • The Origins of the Underline As Visual Representation of the Hyperlink on the Web: a Case Study in Skeuomorphism

    The Origins of the Underline As Visual Representation of the Hyperlink on the Web: a Case Study in Skeuomorphism

    The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism The Harvard community has made this article openly available. Please share how this access benefits you. Your story matters Citation Romano, John J. 2016. The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism. Master's thesis, Harvard Extension School. Citable link http://nrs.harvard.edu/urn-3:HUL.InstRepos:33797379 Terms of Use This article was downloaded from Harvard University’s DASH repository, and is made available under the terms and conditions applicable to Other Posted Material, as set forth at http:// nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of- use#LAA The Origins of the Underline as Visual Representation of the Hyperlink on the Web: A Case Study in Skeuomorphism John J Romano A Thesis in the Field of Visual Arts for the Degree of Master of Liberal Arts in Extension Studies Harvard University November 2016 Abstract This thesis investigates the process by which the underline came to be used as the default signifier of hyperlinks on the World Wide Web. Created in 1990 by Tim Berners- Lee, the web quickly became the most used hypertext system in the world, and most browsers default to indicating hyperlinks with an underline. To answer the question of why the underline was chosen over competing demarcation techniques, the thesis applies the methods of history of technology and sociology of technology. Before the invention of the web, the underline–also known as the vinculum–was used in many contexts in writing systems; collecting entities together to form a whole and ascribing additional meaning to the content.
  • Designing and Deploying an Information Awareness Interface

    Designing and Deploying an Information Awareness Interface

    Designing and Deploying an Information Awareness Interface JJ Cadiz, Gina Venolia, Gavin Jancke, Anoop Gupta Collaboration & Multimedia Systems Team Microsoft Research One Microsoft Way, Redmond, WA 98052 {jjcadiz; ginav; gavinj; anoop} @microsoft.com ABSTRACT appeal to a broader audience. Although the ideas and The concept of awareness has received increasing attention lessons generated by such prototypes are valuable, they over the past several CSCW conferences. Although many leave a critical question: Why did these prototypes fail to awareness interfaces have been designed and studied, most provide users with substantial value relative to cost? What have been limited deployments of research prototypes. In combination of features, design, and process will help an this paper we describe Sideshow, a peripheral awareness application succeed in establishing a healthy user interface that was rapidly adopted by thousands of people in population? our company. Sideshow provides regularly updated Sideshow started as one more idea for an interface designed peripheral awareness of a broad range of information from to provide users with peripheral awareness of important virtually any accessible web site or database. We discuss information. Rather than concentrate on a specific Sideshow’s design and the experience of refining and awareness issue, the research team set out to incorporate a redesigning the interface based on feedback from a rapidly range of features into a versatile and extensible system for expanding user community. dynamic information awareness that could be easily Keywords deployed, extended by third parties, and quickly evolved in Situational awareness, peripheral awareness, awareness, response to users’ experiences. computer mediated communication, information overload What happened was something akin to an epidemic within 1 INTRODUCTION our company.
  • Bforartists UI Redesign Design Document Part 2 - Theming

    Bforartists UI Redesign Design Document Part 2 - Theming

    Bforartists UI redesign Design document part 2 - Theming Content Preface...........................................................................................................................6 The editor and window types......................................................................................7 Python console.............................................................................................................8 Layout:................................................................................................................................................................8 The Console Window.........................................................................................................................................8 Menu bar with a menu........................................................................................................................................8 Dropdown box with icon....................................................................................................................................9 RMB menu for menu bar....................................................................................................................................9 Toolbar................................................................................................................................................................9 Button Textform..................................................................................................................................................9
  • Bibliography of Erik Wilde

    Bibliography of Erik Wilde

    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
  • Predicting Search Task Difficulty

    Predicting Search Task Difficulty

    Predicting Search Task Difficulty Jaime Arguello University of North Carolina at Chapel Hill [email protected] Abstract. Search task difficulty refers to a user's assessment about the amount of effort required to complete a search task. Our goal in this work is to learn predictive models of search task difficulty. We evaluate features derived from the user's interaction with the search engine as well as features derived from the user's level of interest in the task and level of prior knowledge in the task domain. In addition to user-interaction fea- tures used in prior work, we evaluate features generated from scroll and mouse-movement events on the SERP. In some situations, we may prefer a system that can predict search task difficulty early in the search session. To this end, we evaluate features in terms of whole-session evidence and first-round evidence, which excludes all interactions starting with the second query. Our results found that the most predictive features were different for whole-session vs. first-round prediction, that mouseover fea- tures were effective for first-round prediction, and that level of interest and prior knowledge features did not improve performance. 1 Introduction Search engine users engage in a wide variety of search tasks. A large body of prior research focused on characterizing different types of search tasks (see Li and Belkin [10]). The motivation behind this prior work is to understand how task characteristics influence search behavior and how search systems can provide customized interactions for different task types. One important search task characteristic is search task difficulty.
  • Veyon User Manual Release 4.1.91

    Veyon User Manual Release 4.1.91

    Veyon User Manual Release 4.1.91 Veyon Community Mar 21, 2019 Contents 1 Introduction 1 1.1 Program start and login.........................................1 1.2 User interface...............................................2 1.3 Status bar.................................................2 1.4 Toolbar..................................................3 1.5 Computer select panel..........................................3 1.6 Screenshots panel............................................4 2 Program features 7 2.1 Using functions on individual computers................................7 2.2 Monitoring mode.............................................8 2.3 Demonstration mode...........................................8 2.4 Lock screens...............................................9 2.5 Remote access..............................................9 2.6 Power on, restart and shutdown computers............................... 11 2.7 Log off users............................................... 12 2.8 Send text message............................................ 12 2.9 Run program............................................... 13 2.10 Open website............................................... 13 2.11 Screenshot................................................ 14 3 FAQ - Frequently Asked Questions 15 3.1 Can other users see my screen?..................................... 15 3.2 How frequently are the computer thumbnails updated?......................... 15 3.3 What happens if I accidentally close the Veyon Master application window?.............. 15 3.4
  • Bluebeam Revu Kansas Department of Transportation 700 SW Harrison Topeka, KS 66612

    Bluebeam Revu Kansas Department of Transportation 700 SW Harrison Topeka, KS 66612

    Kansas Department of Transportation-Bureau of Local Projects http://www.ksdot.org/burLocalProj/BLPDocuments/KDOTBLPEplans.pdf July 1, 2014 i Bluebeam Revu Kansas Department of Transportation 700 SW Harrison Topeka, KS 66612 For additional KDOT training sources, please visit KDOT’s CADD Support channel located at www.youtube.com/kdotcaddsupport Helpful web links: https://studio.bluebeam.com Credit for a majority of this manual goes to: Mike Dillner, KDOT CADD Support Scott Marquis, KDOT CADD Support Jonathan Mushock, KDOT Traffic Safety and Technology Misty Rodriguez, KDOT KCTC Trainer Megan Murray, KDOT KCTC Trainer Ingrid Vandevort, KDOT KCTC Training Coordinator Chapters 1-4 and Appendix A were written by these people and they deserve the credit for the quality of the document they have produced. Revision date: July 2014 ii Bluebeam Revu Kansas Department of Transportation Introduction to Bluebeam Revu This is a guide for how to use Bluebeam Revu for your PDF markup and collaboration needs. Bluebeam Revu provides powerful and easy to use features for marking up Architecture, Engineering, and Construction (AEC) plan PDF documents. The Studio Session feature allows users from any location to participate in a collaborative review. Bluebeam makes use of Amazon Web Services (AWS), commonly referred to as the Amazon Cloud. This service will host the documents for the Studio Session. There are two roles within a Bluebeam Studio Session. That of an initiator, and that of a participant. If you are going to initiate a Studio Session you need to have any tier of Bluebeam Revu installed on your pc. However, to be a participant all that is required is Bluebeam Vu (a free PDF reader), though Bluebeam Revu can be used as well.
  • Line 6 POD Go Owner's Manual

    Line 6 POD Go Owner's Manual

    ® 16C Two–Plus Decades ACTION 1 VIEW Heir Stereo FX Cali Q Apparent Loop Graphic Twin Transistor Particle WAH EXP 1 PAGE PAGE Harmony Tape Verb VOL EXP 2 Time Feedback Wow/Fluttr Scale Spread C D MODE EDIT / EXIT TAP A B TUNER 1.10 OWNER'S MANUAL 40-00-0568 Rev B (For use with POD Go Firmware 1.10) ©2020 Yamaha Guitar Group, Inc. All rights reserved. 0•1 Contents Welcome to POD Go 3 The Blocks 13 Global EQ 31 Common Terminology 3 Input and Output 13 Resetting Global EQ 31 Updating POD Go to the Latest Firmware 3 Amp/Preamp 13 Global Settings 32 Top Panel 4 Cab/IR 15 Rear Panel 6 Effects 17 Restoring All Global Settings 32 Global Settings > Ins/Outs 32 Quick Start 7 Looper 22 Preset EQ 23 Global Settings > Preferences 33 Hooking It All Up 7 Wah/Volume 24 Global Settings > Switches/Pedals 33 Play View 8 FX Loop 24 Global Settings > MIDI/Tempo 34 Edit View 9 U.S. Registered Trademarks 25 USB Audio/MIDI 35 Selecting Blocks/Adjusting Parameters 9 Choosing a Block's Model 10 Snapshots 26 Hardware Monitoring vs. DAW Software Monitoring 35 Moving Blocks 10 Using Snapshots 26 DI Recording and Re-amping 35 Copying/Pasting a Block 10 Saving Snapshots 27 Core Audio Driver Settings (macOS only) 37 Preset List 11 Tips for Creative Snapshot Use 27 ASIO Driver Settings (Windows only) 37 Setlist and Preset Recall via MIDI 38 Saving/Naming a Preset 11 Bypass/Control 28 TAP Tempo 12 Snapshot Recall via MIDI 38 The Tuner 12 Quick Bypass Assign 28 MIDI CC 39 Quick Controller Assign 28 Additional Resources 40 Manual Bypass/Control Assignment 29 Clearing a Block's Assignments 29 Clearing All Assignments 30 Swapping Stomp Footswitches 30 ©2020 Yamaha Guitar Group, Inc.
  • The Fancytooltips Package∗†

    The Fancytooltips Package∗†

    The fancytooltips package∗y Robert Maˇr´ık [email protected] May 4, 2009 1 Introduction The package fancytooltips is a package for LATEX. The pdf can be created by pdflatex or by latex + dvips + AdobeDistiller1 + Adobe Acrobat2. It allows to create tooltips in a similar way like cooltooltips package, but the tooltip is a page from another PDF file. In this way you can use mathematics, pictures and animations in your tooltips. The resulting PDF file can be used also with free Abobe Reader. The tooltips are activated by clicking the active area on the screen and deac- tivated after closing page or by moving mouse outside the link. You can try the links here (Einstein's formula) and also here (animation { numbers from 1 to 6). You have to use the free Adobe Reader or nonfree Adobe Acrobat to see the effect (xpdf, evince and others fail to work with JavaScripts). For more examples how the presentation may look like see the example.pdf and example-min.pdf files in the examples subdirectory. The buttons are created using eforms.sty which is a part of AcroTeX bundle. 2 Usage 2.1 The file with tooltips The file with tooltips is an ordinary pdf file, one tooltip per page, tooltips should be in the top right corner at the page, in a colored box and the rest of the page should be transparent. If you consider to use movetips option (see below), then every page should have the dimensions equal to the dimen- sions of the colored box with tooltip3.
  • Summary of March 12, 2013 FTC Guide, “Dot Com Disclosures” by Susan D

    Summary of March 12, 2013 FTC Guide, “Dot Com Disclosures” by Susan D

    Originally published in the American Advertising Federation Phoenix Chapter Newsletter (June 2013) Summary of March 12, 2013 FTC Guide, “Dot Com Disclosures” By Susan D. Brienza, Attorney at Ryley Carlock & Applewhite “Although online commerce (including mobile and social media marketing) is booming, deception can dampen consumer confidence in the online marketplace.” Conclusion of new FTC Guide on Disclosures The Federal Trade Commission (“FTC”) has broad powers to regulate and monitor all advertisements for goods and services (with the exception of a few industries such as banking and aviation)— advertisements in any medium whatsoever, including Internet and social media promotions. Under long-standing FTC statutes, regulations and policy, all marketing claims must be true, accurate, not misleading or deceptive, and supported by sound scientific or factual research. Often, in order to “cure” a potentially deceptive claim, a disclaimer or a disclosure is required, e.g., “The following blogs are paid reviews.” Recently, on March 12, 2013, the Federal Trade Commission published a revised version of its 2000 guide known as Dot Com Disclosures, after a two-year process. The new FTC staff guidance, .com Disclosures: How to Make Effective Disclosures in Digital Advertising, “takes into account the expanding use of smartphones with small screens and the rise of social media marketing. It also contains mock ads that illustrate the updated principles.” See the FTC’s press release regarding its Dot Com Disclosures guidance: http://www.ftc.gov/opa/2013/03/dotcom.shtm and the 53-page guide itself at http://ftc.gov/os/2013/03/130312dotcomdisclosures.pdf . I noted with some amusement that the FTC ends this press release and others with: “Like the FTC on Facebook, follow us on Twitter.
  • Feature-Rich Components & Tools That Boost the Productivity for You & Your

    Feature-Rich Components & Tools That Boost the Productivity for You & Your

    Feature-rich components & tools that boost the productivity for you & your development team! Overview tmssoftware.com products Contents VCL Components for Windows application development ........................................................................................... 5 TMS Component Pack............................................................................................................................................... 6 Grid Components .................................................................................................................................................. 6 HTML ENABLED COMPONENTS .......................................................................................................................... 10 Edit controls ........................................................................................................................................................ 13 Planner components ........................................................................................................................................... 17 Outlook / inspector bar components ................................................................................................................. 19 Web connectivity components ........................................................................................................................... 20 Memo components ............................................................................................................................................ 22 System
  • Insert a Hyperlink OPEN the Research on First Ladies Update1 Document from the Lesson Folder

    Insert a Hyperlink OPEN the Research on First Ladies Update1 Document from the Lesson Folder

    Step by Step: Insert a Hyperlink Step by Step: Insert a Hyperlink OPEN the Research on First Ladies Update1 document from the lesson folder. 1. Go to page four and select the Nancy Reagan picture. 2. On the Insert tab, in the Links group, click the Hyperlink button to open the Insert Hyperlink dialog box. The Insert Hyperlink dialog box opens. By default, the Existing File or Web Page is selected. There are additional options on where to place the link. 3. Key http://www.firstladies.org/biographies/ in the Address box; then click OK. Hypertext Transfer Protocol (HTTP) is how the data is transfer to the external site through the servers. The picture is now linked to the external site. 4. To test the link, press Ctrl then click the left mouse button. When you hover over the link, a screen tip automatically appears with instructions on what to do. 5. Select Hilary Clinton and repeat steps 2 and 3. Word recalls the last address, and the full address will appear once you start typing. You have now linked two pictures to an external site. 6. It is recommended that you always test your links before posting or sharing. You can add links to text or phrases and use the same process that you just completed. 7. Step by Step: Insert a Hyperlink 8. Insert hyperlinks with the same Web address to both First Ladies names. Both names are now underlined, showing that they are linked. 9. Hover over Nancy Reagan’s picture and you should see the full address that you keyed.