0001
`
`Twitter
`Ex. 1001
`IPR1 of U.S. Pat. No. 6,895,557
`
`

`
`U.S. Patent
`
`US 6,895,557 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`oeom§..._2__.3macaw:5%.82:m2_xm3:3.8untouux_.._EoxiflHm..E_.m__.3»3m2o.Eo=_2.<$3BEafiuonm«Boamauve»Accunomfimc_:_3cou._32_E85%so3282:232E2..58m:..:.§_oaMedozsm.3=.o._...._%,2.:Emm._3oE¥_.%bfii * _.ofigom.:o_Bmoxoa2.:.35E2:Eu55occ.m2oz.n32uE96_._..M.u...&w<
`
`
`
`2_...__%_:%.=E..:nI[E
`
`
`
`8%sono?»3%ago;eaHBa:Ba:.$Eo_._3uEoo_...§M2259539.“.was
`ucmm.9:xo__o55En.Songmenu5..cosacu..,mxm0UCDOuE9mzacuuao..mBo§
`
`
`
`
`rfl.fi...F__.fl_E.__,,o.EDEsa523as...
`
`
`
`|_.EE..Ell_f__|_i1i..fJii§_n__§._
`
`0002
`0002
`
`E
`
`K.63
`
`
`
`
`
`Tea:9___m:2.8.09:Box8oEo_._
`
`
`
`
`
`3.02.:__oE|o3...2303.
`
`
`
`5.5:m:_mo_oa.5:0mc_o:oc_.._moss:msocmucomumtnam9.58
`
`
`
`
`
`aootcow._2_u2.._
`
`m®:._OI
`
`
`
`

`
`U.S. Patent
`
`May 17,2005
`
`Sl1cct20f5
`
`US 6,895,557 B1
`
`
`
`._..o_§couoau$oE_cu525vucBE83___gmozfi2:.322.mafia
`
`2:o:__msofix_m39.9%55E6.m3o:..._5%9___._3._8..3.=aEou5%5
`
`
`
`
`
`
`,_o_u_£2:BaasE2.amenm:.:o5u::E..=mo2.....EB_So»to;o_._m3.8me_.o.sowAuE.3;2>_.==o.:=mO9__%<
`
`m:_mmouEn_3.25_£_ma
`
`
`
`
`
`
`
`
`2:35.22...o3...E5E6.mB2E52_.E_:_3=ou.=§ca523.£2_Eoo
`
`
`
`
`
`
`
`2:382.3,know9:.8303om.__2__2__EmE3_S2.3.E32...»$33tom._a...,uw.._uu_.._.3.E3_5%33o.._..._omc_3<€_.§§._&.E_.235
`
`
`
`€553?m_E_omain.Ba~.u5..uE
`
`
`
`%8_a3?Bo.._ooo_~3n_wzosucaotzm
`
`
`
`
`
`
`
` .n.umoE_“Bum3So:325@
`
`.3o_B.8;
`
`0003
`0003
`
`
`
`
`
`
`

`
`U.S. Patent
`
`May 17,2005
`
`Sl1cct30f5
`
`US 6,895,557 B1
`
`
`
`umofimfiuum. 5552.§t......£Vmmufiauaoum2..umufi.cummuuumcohucé
`
`
`
`
`
`
`
`
`
`
`
`83..5mam:o._m:m_E5om:ucu«.3.__cEoQEo..
`
`§__.£mmo25.:a....u....cm_u.uu2B.u..§.Q
`
`
`
`
`
`52.2.53.&.ca_E.u..uzuugu.cumcoom.we‘uEu:umm~:o...aou~Emcm.
`
`
`
`@919€25.atb..§.o_._§.
`
`652%3,..:§..$.§...n
`
`83a3£.o&:....ob
`
`Qufiqfiubfin
`
`bEoqE.3mmumfiq
`
`....§§§
`
`3.5%anuEc2uE
`
`am...macs...E§_2...n
`
`
`
`5......nfluuuu3....
`
`mm..3.0562
`
`m.uE.§6u.m.
`
`3.5mmu«E52535.
`
`E8»on‘?m=._E.m.
`
`
`
`xoocnstuuu.uE...
`
`.35%.as58..
`
`
`
`_cumuET.8_G59.5..asmLo&U
`
`
`
`«.5§\u.§m....uP.baa
`
`.33.uco....r...E_.m:..
`
`useown...
`
`MUOENLUEU
`
`0004
`0004
`
`
`
`.m:.$m.mu._o..oo_o§E9_ccnmom..Eu..um.o...x....I3.5%uogooncaoumxuun
`
`
`
`
`
`
`
`m..0?‘
`
`
`
`9.._.$.wweko..OQ~.x3
`
`
`
`S.usfi.3%5.355..
`
`
`
`mum...§._....%......£%..c..m§§.§
`
`,§.§.._
`
`_E&.:I.E..§E&
`
`
`
`. .LO
`
`.2...«E??....__m
`busqoh.
`
`
`
`..uuu._tm..c.~.B.c§.uumuEu=q
`
`
`
`
`
`
`

`
`U.S. Patent
`
`May 17,2005
`
`Sl1cct40f5
`
`US 6,895,557 B1
`
`
`
`.$3m.%..B__2..E§m Eu:....8.§=..»..mm3o.w§._oo\._._...En:..wfl£....=E.~usages»mm.oE.._
`
`
`
`
`
`
`
`
`
`
`
`
`been8aka..m=.£matMEUQEE
`
`Am.‘«.593:_£.Se3numb..E.%ata~o.=o._Gu..fiu:_
`....35.mmu.a%8._xm......8:
`
`
`
`
`
`
`beaomnm.omhsnwmmo_E.F...c&_..__.£atasQua:
`
`
`
`
`
`33$.~U@k.H®..©.3.c.§..:..<me.ubovabmabum
`
`.e.._.§.uns.._._2s..,.~523.83.5.Q%8&
`
`
`
`
`
`mmflobuonco..._uc.__.§oq.axsmat§.s.¢
`
`
`
`..%m.E:...6Lmom....mc.5.w3.238.5%
`
`
`
`
`buoammun.suntan..mc_Emfixbuchmmum
`
`
`
`
`
`
`Q3.B5..6A.m&._am..awGhana5uE_.......c.36
`
`E46u...whenE39.
`
`
`
`me.5..Sxmmuuoam
`
`
`
`M...coauu
`
`
`
`_.C3~.P..Emuacoc
`
`9§mn.....c9:....m
`
`.c._um_ou...O3..
`
`
`
`mE..Euxuoboe
`
`
`
`Emfibou...§u..m
`
`
`
`muucumum..__um.........¢.an?&..__.Enon..._...uumu.i
`
`§....._mawEmma
`
`
`
`
`
`Ebenhaw..mu.:..,...atNumuo.
`
`
`
`u....%_.£mtE:>a.ucma?umo.._fiu.....
`
`9.2.6mum.9.3m3._%....o.
`
`0005
`0005
`
`
`
`Eohm§6.._...t£u.<
`
`
`
`
`
`mc.$.m.mum£.£m..u~.c...Eu.m.mc.t.mwe.wc§hm
`
`aim
`
`3.».9...
`
`nouhufiauuE.~mmaom.mu....om_..._.~..En:.m.
`
`.£5.m.»_E_umSo:
`
`
`
`.3...m£o_:Bum=._s_a
`
`ta9%ex:
`
`bunqeq
`
`
`
`..uuu.t__££.§8%8ma....8§m
`
`
`
`
`
`

`
`U.S. Patent
`
`May 17,2005
`
`Sl1cct50f5
`
`US 6,895,557 B1
`
`...&uE§,§_.um._R_o$58..2:Qbuw.3.mm_Gww.aN.QmmoE~.£oum..BmbE~mogQHmEc2£EqE£$AtomQC&QEnxm
`
`
`Baum»bus.3&Em:E..hmmao.u.<u..fio§..Eaa.m....fl\UCD+§Qb...I..w\2hm..___
`
`
`
`tuna:
`
`
`
`
`
`E3.uEvatm»GE
`
`
`
`mm.‘&Eu..«.5mumxmb.m\.QQR..mhUQH.mmD2..m.mDuQ
`
`
`
`.m.n5uumsaum.
`
`figoimmum
`
`.Q~...mmb
`
`._..
`
`.0
`
`.mEu2$.QqE.£
`
`
`
`.m§_§.E:2m..E
`
`.wm_.....finE...
`
`.~§oum.mnE...
`
`.o.nouQ...~
`
`.N.....mob
`
`.nummAb
`
`__
`
`.....§
`
`0006
`0006
`
`

`
`US 6,895,557 B1
`
`1
`WEB-BASED MEDIA SUBMISSION TOOL
`
`The present application is related by subject matter to
`U.S. application Ser. No. (l9t44=0,46l, now U.S. Pat. No.
`6,732,162.
`BACKGROUNI) 01-" 'I‘lIE INVI_-'.N'I"I()N
`
`1. liield of the Invention
`The present invention relates to the handling, manipula-
`tion and processing of digital content and more particularly
`to the transportation and Internet publishing of digital
`content, particularly image media objects and rich media.
`2. State of the Art
`
`Much of the phenomenal success of the web is attribut-
`able to its graphical nature. Literally, a picture is worth a
`thousand words. The capture of digital images has become
`routine. using digital cameras and scanners. Nevertheless.
`although the handling of images by website creators has
`achieved a high degree of automation,
`for the average
`technology user (the “imaging civilian”), manipulating and
`sharing digital images over the Internet remains a cumber-
`some and daunting process. Piecemeal solutions that have
`been devised for handling digital images require a level of
`sophistication that is beyond that of the ordinary user. For
`example,
`transferring a digital
`image may require first
`downloading a FTPprogram, then installing it, then running
`it and connectting to an FTP server by typing the server
`name in the connection dialog, then navigating to the proper
`subdirectory, selecting the files to be uploaded, making sure
`that the program is in binary transfer mode, then sending the
`files. For the imaging civilian, such an involved process. can
`be daunting to say the least.
`Additionally, as technologies advance and casual users
`begin to experiment with other media objects, such as
`streaming video, 3D objects, slide shows, graphics, movies,
`and even sound files that accorrtpany imaging data,
`the
`processes required to share these rich media types on the
`Internet becomes exponentially more complicated and pro-
`hibitive. As the realization of the Internet as an interactive,
`content rich medium becomes more and more a reality, the
`need for enabling the use and distribution of rich content and
`media on the Internet will become the gating factor to its
`long term success.
`A broad-based solution to the foregoing problem requires
`a web—bascd media submission tool that allows for submis-
`
`‘Jl
`
`IU
`
`1U
`
`3U
`
`40
`
`sion of media objects in a convenient, intuitive manner. A
`company named Caught in the Web, has attempted to create
`a broad-based media submission tool known as “ActiveU-
`
`45
`
`plead“. ActiveUpload allows an arbitrary file to be dragged
`and dropped onto a web page control for upload to the web
`Server. An /\ctiveUpload control allows users to, without
`leaving a web page, transfer files to a server (Internet or
`intranet) by selecting the files on the user’s desktop that the
`user wants to transfer, then dragging them onto the web
`page. For example, a user, having visited a web page, can
`contribute pictures, documents, zip files, etc., without hav-
`ing to leave the web page and use an FTP program. Standard
`web authoring tools can be used to integrate ActiveUpload
`into web pages and change the behavior of the control.
`Although Caught in the Web’s ActiveUpload tool simpli-
`lies the user experience,
`it does little toward furthering
`“backend” automation in the handling and distribution of
`media objects and has no built in "intelligence" to streamline
`the process of handling and transporting rich media objects
`from the front end.
`
`SUMMARY OI’ 'l'lIl5.-L INVl.£N'l'lON
`
`50
`
`55
`
`an
`
`65
`
`The present invention, generally speaking, provides an
`improved web-based media submission tool. As with some
`
`2
`existing tools, operation of the tool is drag and drop or the
`user can “click” to browse a directory to select media
`objects. Unlike existing tools,
`the tool provides several
`unique and valuable functions. For example, the tool pro-
`vides the user an opportunity to conlirm the submission with
`a visual representation, for example by generating a thumb-
`nail image of the rich media lile that has been selected.
`Additionally, batch submission is provided to allow a user to
`drag and drop or select a plurality of images or other media
`objects. Submission from a web page to a web page is also
`provided for. Even more importantly, the submission tool is
`configurable to perform a variable amount of intelligent
`preprocessing on media objects prior to upload. In the case
`of digital images, the tool can perform sizing and formatting,
`for example. Information capture is performed with infor-
`mation being uploaded together with the media objects. In
`an exemplary embodiment,
`information capture is both
`user-transparent (e.g., user ID andfor password) and user-
`visible (e.g.,
`the user can provide captions for media
`objects). The submission of information about the user and
`the media objects facilitates automatic integration of the
`media objects within existing databases.
`
`BRIEF DESCRIPTION OF Tl-IE DRAWING
`
`The present invention may be further understood from the
`following description in conjunction with the appended
`drawing. In the drawing:
`FIG. 1 is a diagram of an exemplary web page providing
`media object acquisition functions;
`FIG. 2 is a diagram of another exemplary web page
`providing image acquisition functions;
`FIG. 3 is a table pertaining to a first portion of the Prepare
`and Post component design; and
`FIG. 4 is a table pertaining to a second portion of the
`Prepare and Post component design.
`
`'l‘I-ll:‘. PR1-‘ERRED
`D].-'.'I'AiLE.l) l)l3S(_‘RlP’l‘tON OI-'
`EMBODIMENTS
`
`The following describes the Prepare and Post“ tools,
`which prepares and submits media objects from inside a
`standard browser, referred to as the lirst location, to a second
`location or server. The media objects may be pictures
`(images), movies, videos, graphics, sound clips, etc.
`Although in the following description the submission of
`images is described in greatest detail, the same principles
`apply equally to media obejcts of all descriptions.
`The Prepare and Post tools refers to browser—side com-
`ponents which together provide the ability to submit and
`transport media objects over the web to be stored and served.
`Using the Prepare and Post tools, end users can submit
`images in an immediate,
`intuitive manner. No technical
`sophistication is required. In particular, understanding tech-
`nical terms such as JPEG, resolution, pixel, kilobyte, trans-
`fer protocol, IP address, FTP ctc., is not required, since the
`Prepare and Post tools handles all of these tasks for the user.
`The benefits of the Prepare and Post tool are:
`a) to the image submitter,
`the ability to submit media
`objects to web pages immediately without needing to
`overcome technical obstacles;
`b) to the image submitter,
`the ability to submit media
`objects to web pages “as is” without making modifi-
`cations to the media objects prior to sending.
`c) to Pictureworks web site partner, access to a uniform,
`standardized, reliable and secure channel for media
`acquisition;
`
`0007
`0007
`
`

`
`US 6,895,557 B1
`
`immediately according to the configuration of the Prepare
`and Post tools.
`
`4
`
`3
`cl) to PictureWork.s web site partner, access to contributed
`media “made to order", it meets their imaging speci-
`fications every time without human intervention;
`e} to Pictureworks web site partner, the ability to provide
`web site visitors with an easy, error free way to
`contribute media;
`f) to PictureWorks web site partner, access to contributed
`media in “real time" with no time delays.
`The two primary components used in the Prepare and Post
`tools which carry out these functions are 1) the media object
`identifier and 2) the media sender.
`In general, the media object identifier functions to provide
`a graphical interface for placing and associating a media
`object from a user’s desktop onto a web page. The media
`sender carriers out the function of transmitting media objects
`to a second location.
`
`There are two ways media objects on the first location
`become associated with a media object identifier. The first is
`through a "drag and drop" behavior where the user clicks on
`a media object to select the one they want to submit. The
`media object is then dragged to the media object identifier.
`Releasing the mouse button associates the media object with
`the media object identifier. This behavior is allowed in web
`browsers that support drag and drop functionality. The
`Prepare and Post
`tools enable these browsers to accept
`media objects via drag and drop by providing the media
`object identifier as an ActiveX component.
`The second way to associate a media object on the first
`location with the media object identifier is to click on the
`media object identifier to browse for media objects,
`then
`select the media object of choice. This method is made
`available for web browsers where the media object identifier
`needs to be a pure Java component. (Such “signed applet
`browers” like Netscape Navigator) In this instance, the user
`maybe asked to choose a media object in a similar manner
`as when choosing a file to be opened, either by graphical
`navigation or by specifying a path name. For example, a
`prompt associated with the media object identifier may be
`displayed prompting the user to click within the media
`object identifier. Clicking within the media object identifier
`brings up a browse dialog. Using the browse dialog, the user
`selects the desired media object, which is then placed in the
`media object
`identifier. The Prepare and Post
`tools will
`generate a visual representation or thumbnail of the media
`object, a feature currently ‘Not available in signed applet
`browsers.
`
`Real estate is an example of a prime application of the
`Prepare and Post tools. "Curb appeal" is of great importance
`in the realty industry and can only be judged by “drive-bys,”
`which are time-consuming and laborious, or by the avail-
`ability of images. The Prepare and Post lools make real
`estate images readily available with a minimal amount of
`effort.
`
`Referring to FIG. 1, an example is shown of a realty web
`page featuring the described Prepare and Post tools func-
`tionality. The user associates images with a media object
`identifier via the methods described above and selects appro-
`priate captions for the images, e.g., living room, family
`room, etc. The captions may be typed in or selected from
`menus. The user also supplies identifying information, in
`this instance the MLS listing number. When the user clicks
`the Send button,
`the images are uploaded and processed
`
`‘Jl
`
`IU
`
`1U
`
`The Prepare and Post tools also support a batch interface,
`allowing a plurality of images to be submitted simulta-
`neously as in the case of a professional photographer, for
`example. The opportunity for user confinrlatiori
`is again
`provided, e.g., by displaying a visual representation of the
`images in the batch.
`If a mistake is made such that the wrong image is placed
`in a media object identifier. the correct image may be placed
`in the media object identifier. The correct image will replace
`the mistaken image. Alternatively, the user may remove an
`image from a media object identifier by rigltt-clicking on the
`media object
`identifier and selecting Remove within a
`resulting pop-up menu.
`Note that any number of media object identifiers may be
`provided on a web page and that the media object identifiers
`may be separate or grouped. This is evident in FIG. 2. The
`number of media object identifiers provided on a page can
`be pre-configured and fixed, allowing no user intervention,
`or the media object identifiers can be generated dynamically,
`allowing the user to determine how many media object
`identifiers they need for media submission. FIG. 2 shows a
`web page with various sizes of media object identifiers. If a
`media object identifier is separate, its image will be trans-
`mitted separately to the second location. If an media object
`identifier is part of a group, its image will be transmitted to
`the second location as part of a group of images that are
`stored together and cataloged together. Media object iden-
`tillers that are associated together as a group are noted as
`such in the web page interface and transparently in the media
`object identifier Object code. Moreover, a web page may
`have multiple groups of media object identifiers. or "groups
`of groups."
`The usefulness of images is greatly enhanced by capturing
`and identifying information about the images and submitting
`the identifying information with the images. Information
`may be image-specific, user-specific or both. The submis-
`sion of information about
`the user and the media objects
`facilitates automatic integration of the media objects within
`existing databases. Information capture may be oven or
`covert or both. This unique automatic database integration
`enables the images to be served with the proper web page
`data. Overt information capture relies upon the user to make
`menu selections of appropriate captions as illustrated in FIG.
`1, or to make text entries within text fields, or both. The
`Prepare and Post tools are easily customized to accept menu
`selections and text fields for different applications. Covert
`information capture occurs by having the web browser
`automatically pass to the Prepare and Post
`tools known
`information such as a user ID or, password used to access the
`web page.
`A key differentiator of the Prepare and Post tools is the
`browser, or client-side intelligence built into the tools. This
`intelligence directly provides features including those
`already outlined such as associating data with media objects,
`generating a visual representation of the media objects and
`generating media object
`identifiers dynamically or
`in a
`pre-set manner. Other features are also provided via this
`intelligence, specifically, the ability to control the width and
`height of the media object
`identifier and the ability to
`0008
`0008
`
`3U
`
`.
`
`40
`
`45
`
`50
`
`55
`
`till
`
`

`
`5
`
`US 6,895,557 B1
`
`preprocess the media objects in any number of ways prior to
`transporting to a second location. In the case of an image
`media object for example, the Prepare and Post tools may
`resize the image, (i .e., increase or decrease its size as defined
`by either physical dimensions, pixel count, or kilobytes).
`Compression, for example, is a type of sizing. The Prepare
`and Post tools may also change the image’s file format (a
`way of a media object being identified as to a “type" or
`“kind" of media), change the quality setting of the image,
`crop the image or change the aspect ratio, add text or
`annotations, encode or combine (including stitching) the
`media object, or enhance the media object by changing
`image values, for example, relating to contrast or saturation.
`This intelligence may be executed in a manner that
`is
`transparent to the end user. This transparency allows the end
`user to submit media to the Prepare and Post tools "as is,"
`since the tools will automatically prepare it to meet
`the
`requirements of the second location. Note that, although
`image submission may involve client-side processing, image
`processing is not required.
`The Prepare and Post tools are available for customers to
`integrate into their own web pages. The Prepare and Post
`tools are easily integrated into web sites (customers) to
`allows those sites to accept media objects from web site
`visitors (users). Appendix A is a generic HTMI. Ilost'l'em-
`plate illustrating how Prepare and Post components are
`integrated into a web page. The HTML template file (which
`is a complete working example) contains instmctions and a
`few small code snippets that
`the customer pastes into the
`web page.
`integrating the Prepare and Post components
`requires an Initialization Section, a Configuration Section,
`an lmagewell {media object identifier) Section, at Submis-
`sion Section and an ImageUpLoad Control Section. To .
`include the Prepare and Post tools media object identifiers
`on a web page, the customer cuts and pastes code snippets
`for these sections from the template into the web page.
`The Initialization Section consists of a
`few lines of
`
`‘Jl
`
`IU
`
`1U
`
`3U
`
`40
`
`45
`
`50
`
`55
`
`no
`
`6
`image have a unique name to prevent one image from
`overwriting another. Key2 is an optional secondary key that
`is appended to Keyl before the image’s filename and URL
`are created. While default values for Key] and Keyi can be
`specified in the configuration section, more likely this value
`will be supplied from a field in the web form. If the web page
`form contains a control named “Key i,” then its value will be
`used for this key. For example, the field Keyl might be
`labeled as “MLS Number" on the web page. Similarly, the
`field Key2-m ight be labeled "Zip Code" on the web page. A
`sequence number is appended to the Key1,r‘Key2 combina-
`tion. When there are multiple media object identifiers on a
`page, this will ensure that each image has a unique key.
`All media object
`identifiers on a web page must be
`contained within an I-l’l‘Ml. form. A single line of .lavaSeript
`code is inserted into the web page (within the HTML form)
`in each place where a media object identifier is desired. The
`Media object identifier Section can specify the width and
`height for each media object identifier. If the width and
`height are omitted, then the default width and heigth from
`the Configuration Section are used.
`The Submission Code Section contains HTML code that
`creates the button that submits both the images to the second
`locations and the form to the customer’s server. Within the
`
`Submission Code Section, an HTML "hrel” parameter is
`required for the Send Button that causes the images to be
`sent. After the images have been sent, the web page l'tJtTI1
`will be submitted in the standard manner. The form must
`
`define two hidden fields named “url” and imagecount.” The
`imagecount field will contain the number of images actually
`transmitted.
`In an exemplary embodiment,
`the URL for
`images 2 through “n” are generated by replacing the initial
`sequence number at the end of the returned URL with the
`desired image number.
`The ImageUpload Control Section holds a small piece of
`Javascript code that is placed at the very end of the body
`section of the web page. This code creates the non-visible
`Image Upload control, or media sender, that performs the
`transfer of images from the user's machine to the second
`location.
`
`The Prepare and Post components support multiple
`browsers and dynamically adjust their behavior according to
`the type of browser that is currently running. For example,
`under supported versions of Microsoft’s browsers, media
`object
`identifiers are implemented as Activex controls,
`while under supported Netscape browsers, media object
`identifiers are implemented as Java Applets. This multiple
`browser support is completely automatic.
`FIGS. 3 and 4 present further details of the media object
`identifier and media sender components, respectively.
`From the foregoing description, it will be appreciated that
`the present media submission tool, besides offering conve-
`nience to the end user, ofi'ets convenience and flexibility to
`technology partners. In particular, web page integration is
`designed to facilitate automatic server—side integration of
`media content.
`It will be apparent to those of ordinary skill in the art that
`the present
`invention can be embodied in other specific
`forms without departing from the spirit or essential character
`thereof. The presently disclosed embodiments are therefore
`considered in all respects to be illustrative and not restric-
`tive. The scope of the invention is indicated by the appended
`claims rather than the foregoing description, and all changes
`which come within the meaning and range of equivalents
`thereof are intended to be embraced therein.
`
`JavaScript code that will download all of the needed Prepare
`and Post submission components.
`The Configuration Section overrides various configurable
`default settings that the customer can control. In the Con-
`figuration Section, the media objeet identifier component is
`sized and configured to perfonn any preprocessing of the
`image that may be desired prior to upload. Configurable
`parameters include both fixed values for all submissions (per
`submission values) and fixed values for all images within a
`submission (per image values), as will be explained pres-
`ently.
`Fixed values for all submissions include DefauItImage-
`Width and Defaultlmagel-leight, as well as include Default-
`Controlwidth and DefaultControll-Ieight. The former
`specify the default width and height of the images after they
`have been compressed for transmission. The latter specify
`the default width and height of all media object identifiers.
`To create media object identifiers having different sizes, the
`customer specifies the desired size when creating the media
`object identifier. Another fixed value for all submissions is
`Quality. This determines the quality level ofthe images after
`they have been compressed for transmission (0 is the lowest
`qualityfhighest compression and M30 is the highest quality!
`lowest compression).
`Fixed values for all media objects within a submission
`include Keyl and Key2. Keyl
`is the primary value that
`determines the Illename of the resulting image file and,
`consequently, its URL. It is important that each submitted
`
`0009
`0009
`
`

`
`US 6,895,557 B1
`
`APPENDIX A
`
`HostTemp1ate gene ric.htm
`
`cl-lTl\'lL:»
`<H'EAD>
`(!__txmitt:tin:txxttan:tuttixzstnzxxsztt-tttattxtatt Begin ;n;l;a|izatiDn Sccliun __,)
`4!--"‘"" This section of code must appear at
`—->
`<!——"""" the beginng of the <1-IEAD; section of
`———>
`<!——""""' your web page. Copy this code and
`——>
`-:1-—""" paste it directly into your web page.
`--5
`<SCR_ll’l‘ type-=“textr’javascript" src="http:.-’.n'15T.22.134.49;"companyipwtcontp-onents.js"> <.'SCRIl'I‘>
`«:SCRIPT type-"textfjavascripl" sic-"lillp:.I’.I'1S?.22.134.49.u’comparIyfcon1pany.js"> <.n’SC.‘RIPT>
`_d__.x..xx.x...nuxx-zu......x...u..-nux-"nu End inmafizmion Section __,
`<n'HIEAD>
`(BODY:
`(!_____sxnxxxnxxnagxxnesxnnnzxszagnxxxxxnsnxnnnnuattxmagtt Begin Cunfiguralion Sccfion __,
`c!--’‘’‘'‘’‘ This section of code must appear
`—->
`<!——""""' anywhere after the initialization
`——>
`-c!——“"’ section {above}, and before the
`--3
`-cl-—"""" the <FORl\-I: that contains the image
`-->
`<!——"""""" wells.
`——>
`<1——----*
`——;.
`<1-—-—"""" This section defines data values
`-->
`<!-—-—"""‘ needed by the image wells. You can
`---->
`.:!—w“‘"' modify these values to suit ——;»
`<1--“"" your needs.
`<SCRlP']‘ l_artguage="Javascripl">
`PWT.Key1 -= “mtrne—your—image here":
`PWT.K.ey2 - “ ":
`PW"[‘.Qua1ily = 93;
`PWT.I)cfauIt[n1ageVVIdlh - I540;
`P\\-"'T.I)cfaullIn1agel-Ieighl u 480;
`PW'T.DefaultContro|Width = 326:
`PW"l‘.lI)cfauItGtanlroI[-Iei,ghl = 246:
`<.I'SCRIPT>
`4!--""""'“"“"""""‘“""""““""“"‘""“‘ End Configuration Section -->
`(FORM:
`This sample displays a working image well.
`<BR>
`<!____--mununu-ax-I-sunsumautumnxx:-in-as-n-c--upturn-nrxunuu Begin imagewcll Section ___>
`<!--'"" This code creates an image well on
`--:-
`<!—-—-""" the web page. While this template
`-->
`4!--"""‘ only contains a single image well,
`-->
`<!——"“"‘ you can use as many as you like.
`——>
`cl--"""" Copy this code into your web page
`--3
`<!——"""' anywhere within your <FORM:- where
`——>
`<l——"""" you want an image well to appear.
`——>
`¢SC'RIPT Language-“Javascript">
`PWT.addimagecontrol( ):
`
`—->
`
`If If the (FORM: contains fields named 'K;:y1'
`if
`S‘. ‘K.ey2' lheir values will be used.
`
`it’ includes a 3 pixel border
`If Include: a 3 pixel border
`
`it’ or “PWT.add1'.rnagecontro|(640,480):" to override
`If the default width and height.
`
`<.n'SCRlPT>
`<!__txxxttrtxxntunatttIrlrttxxxxlxxx-xxtrlxttttllatzlu End Iniagewell section __b
`(BR)
`This text is after the image well.
`(P:
`(!__I1I1llCull:Inna:lull):Illa:lluolluoullilnilliallrrxluonlnr Begin submission Code Seclion __.’
`4!--"""" You can use any lypc of button you
`--3
`<1-———"""' wish, but rather than it being a
`—-—->
`<l--—"""" standard SUBMIT button, it must
`--—>
`-:!~~"""" instead contain lhu parameter:
`-——:-
`c!__a<x-v-t
`__b
`<!——“'‘'‘'
`——>
`_d__nmnnu
`__)
`4!--"“"“ (as shown in the example below}.
`--5
`<!——"""" After the images have been sent,
`——:
`4!-—""“ your web page FORM will be submilted
`-->
`4!--"""‘ in the standard manner.
`-->
`<!____---nu-x
`____’
`-:5-v-v""" Your FORM rnusl define two hidden
`~->
`-:!——"““' fields named "url" st ‘irnagccounl"
`——:—
`cl--"""‘ (see examples below). The "url"
`--3
`<!——"""" field will be populated with the
`——>
`cl--*""" resulting URL ofthe first (or only}
`-->
`-cl-—"""" image submitted, and the "im:Igecount"
`-->
`<l——“"""" field will contain the number of
`——>
`-1!--""“"‘ images aclually lrunsmitled. The URL
`-->
`c!--—-’"‘''‘''' for images 2 thru n can be generated
`——>
`<!-—-—‘'‘''’‘ by replacing the initial sequence
`-:!—-——"‘"“‘ number (which will always be ‘I"]
`4!--"""‘ at the end of the returned URL with
`
`onclick=“PW"l".Submit( }“
`
`——:-
`-->
`
`0010
`0010
`
`

`
`10
`
`US 6,895,557 B1
`
`9 A
`
`PPENDIX A-continued
`
`HostTemplate gene ric.htm
`
`—>
`
`c!——""‘ the desired intagc nuniber.
`-:[NPl.'l“ lype=“hiddcn" t1ame-——“uri">
`c[NPL'T t_vpe=“hidden" name:-=“i.n1ngecount">
`-:[NPL"l' type:-"t:tutton“ value:-“Submit Images“ onclick="P\\-'”I‘.Submit( '}“>
`git-‘(JRl\-1:
`4!--““'“ """ ““ “““““““ '”“"'”"‘ “““ "‘ End Submission Code Section -->
`d_ one-4--an-u-sous-roanuon-ueaouuua-ca-use-one-neon-vuanca Begin Imflgcupload C-onlrol Section __)
`45- ‘"' This section of code must appear at
`-->
`
`«:E-
`'"‘ the end of the <[50l)‘r":- section of
`-->
`
`<t——-‘”""' your web page. Copy this code and
`<!——‘‘‘‘'“ pasts: it directly into your wet’) page.
`-:S(.‘Rl1’I' languagc=“.lavaseript">
`PWT.ndduptoadcontrol( ]:
`<,rSCR1l"l">
`(!__axxxxxxxxxxxxx:taxtn!X:zuxxxxx-nxzxx-xxxaztxzzx-x End mmgeuplond Comm] Scum“ __=_
`<.-"l3ODY>
`<.-il-ITM L>
`
`What is claimed is:
`
`1. A method comprising the steps of:
`accessing at least one media object identifier, the media
`object identifier being embedded within a third-party
`web site, the media object identifier including a graphi-
`cal user interface for acquiring media objects;
`associating a media object with the media object identi-
`fier; and
`pre-processing the media object by the media object
`identifier for the requirements of the third-party web
`site, the pre-processing being done without additional
`user selection of the pre-processing.
`2. The method of claim 1 wherein the pre—proccssing
`includes one of the following steps:
`reducing the file sitee of the media object,
`compressing the media object
`for purposes of
`transportation.
`changing the tile fonnat of the media object,
`changing the aspect ratio or otherwise cropping the media
`object,
`adding text or other annotation to the media object,
`encoding or otherwise converting the media object,
`processing the media object in a manner that completely
`fills the media object identifier or maintains the aspect
`ratio of the media object within the media object
`identifier,
`changing the orientation or otherwise rotating the media
`object,
`combining (including stitching) of multiple media
`objects, or
`enhancing the image by changing its contrast or saturation
`values.
`3. The methods of claims 1 or 2 wherein the media object
`is associated with the media object identifier by dragging a
`visual representation of the media object to the graphical
`user interface of the media object identifier.
`4. The methods of claims 1 or 2 wherein the media object
`is associated with the media object identifier by browsing
`and selecting tiles.
`5. The methods of claims I or 2 wherein more than one
`
`media object is associated or processed simultaneously.
`IS. The methods of claims I or 2 wherein more than one
`media object identifier is generated dynamically or gener-
`ated from pre-set instructions.
`
`3U
`
`40
`
`45
`
`50
`
`55
`
`no
`
`7. The method of claim 1 wherein the pre—proccssing
`includes reducing the size of the media object.
`8. The method of claim 1 wherein the pre-processing
`includes modifying the fonnat of the media object.
`9. The method of claim 1 wherein the media object
`identifier allows display of the media object in oontext on the
`web page.
`10. The method of claim 1 wherein the media object is a
`digital image.
`11. The method of claim 1, wherein the media object
`identifier is configurable to control the pre-processing.
`12. The method of claim 11, wherein the media object
`identifier is configurable by operators of the third party web
`site to control the pre-processing.
`13. The method of claim 1, wherein requirements relate to
`presentation requirements of the third party web site.
`14. The method of claim 1, wherein the pre-processed
`media object is uploaded to a remote server which enables
`the media object to be displayed on the web site.
`15. A method comprising the steps of:
`accessing a web site containing a media object identifier.
`the media object identifier including a graphical user
`interface for acquiring media objects;
`associating a media object with the media object identi-
`fier; and
`pre-processing the media object by the media object
`identifier for the requirements of a web site, the pre-
`processing including checking a tile size of the media
`object an