THE TERMS OF THE INVENTION:

DIGITAL E-CARD/POSTCARD TECHNOLOGY

AREA OF THE INVENTION:

The invention intends to use a way where metadata for pictures and documents can be integrated with pictures and documents respectively (XMP-technique) with no Java or other code being used.

DESCRIPTION:

THE BACKGROUND AND PURPOSE OF THE INVENTION

Picture archives tend to be very extensive for individuals by both quantity and content. Since computer programs that are known until now only can handle pictures and its metadata separated from each other, there is a large risk that the picture or document all of a sudden gets anonymously in case the metadata changes, get copied, moved or lost in another way. Many times it gets lost because the archive is not maintained or because it is too expensive and time- consuming for the owner to maintain. For this reason, there is a need for many picture- and document users to make the digital work in a more efficient way where the picture and its metadata always follows each other in order for the picture and document archive to work even though they are not well structured or "forgotten" if they become disorganized.

WELL KNOWN TECHNIQUE

The traditional technique for pictures and its cataloguing and indexes is commonly represented by computer programs that are very costly because of their complex construction and its limited market, but also because of the considerable requirement of education and training for the users. For the utilization of digital picture-museums, computer programs like Sofie, Primus, Disgen and Cumulus are used for example, but also more general computer based programs like FileMakerPro and Access are used. GoLife, Dreamweaver and Frontpage are worth to mention among the more applicable computer programs regarding production and development of web pages. The end result of using these programs is reached globally by Internet with web readers like Firefox, Safari, Opera, Netscape, Flock and Internet Explorer. One outstanding characteristic among all these programs is that the picture files and the specific information regarding every picture has to be saved in different files and usually in different places. The user needs to have a lot of discipline and organization in order to make it work; it also requires trained employees at a non neglected costs. Sooner or later the pictures will lose all the information of its content (herein called metadata). Pictures without any information usually have no value. In this description, the still used technique will be mentioned "homepage-technique" and "database-technique".

SHORT DESCRIPTION OF THE INVENTION

Some definitions of used abbreviations to begin with:

The new patent applied E-card technique is herein also called weSee or the weSee-technique.

- The types of files for pictures (usually jpeg- or tiff-), documents (usually pdf-) and folders (without suffix) are here summarized as BDF-files.

- Metadata is usually used to designate information regarding information.

The word is used for all XML/XMP-information regarding a Folder, Picture or Document saved in BDF-file respectively.

XMP is a variant of XML developed by Adobe, published in August of 2002.

UID = Unique identifier.

GUI = Graphic User Interface.

Object = Delimited and marked item in picture or document.

Satellite object = Object, for example a text-box or movie-box that belongs to an object .

By the given background there is a need for a technique that is able to meet the needs of present and future requirements of an easily used identification of pictures and its content without a requirement of pedantic organization. The needs are met since the invention contains a method, design and application of a computer program for the use of pictures, documents and folders as well as for saving and recycling of files with a reliable and lasting identification and information, at which data and files can be used internally or globally by the Internet and Intranet, characterized by the metadata for pictures, documents and folders saved in the BDF-files. Objects can be identified in pictures and documents and be linked together. The objects can even be searched globally by use of URL and UID since metadata in pictures and documents by means of a "watchman" or "janitor" (the word watchman will be used) can be structured in peripheral index files.

Metadata information/ text in BDF-files can be handle in multiple languages at the same time and the use of automatic translation on an object level is possible. The described weSee-method features versatile form technology which can be combined with multi language technique on object level. The technique allows for a "surf-possibility in synergism with the Homepage technique, but with the difference that weSee E-cards are intuitive useful (GUI) so that an extended training (Webmaster training) is not required.

The technique described here is mainly based on standard in agreement with "The World Wide Web Consortium (W3C)" (se http:/ /www.w3.org/ , http:/ /www.w3c.se/), respectively XML (Extensible Markup Language) and Dublin Core. The XML-technique is described at http:/ /www.xml.com .

This description of the invention is not fully complete in order to design a computer program for a group of programmers, graphic art designers and qualified users with diverse individual competences.

The part of the foundation that remains is fantasy, experience, hard work and the ability to see many and complex connections and with a timeframe on >100 years is barely possible to reproduce in paper. On top of that are people's different abilities, necessary for the E-card technology to work, not easy to describe.

A summary of the invention is described in Figure 1, where the programs necessary elements are shown as components. Part of the inventions does not only consist of these components, more like a cooperation of these components. The result is shown in Figure 5 and 6.

The Homepage technique we use nowadays based on the Mosaic- and Netscape-programs uses a fairly complicated, costly and sensitive technique in order to save, manage and reproduce meta-inf ormation for digital pictures and documents as well as for communication through the Internet. The technique that is used in the invention in this case is substantially easier to use and also less expensive than the Homepage technique. The weSee technique does not use traditional Homepages which includes an obvious simplification and lower costs; neither does it use the database technique to manage BDF-archives which also involves a simplification, reduced complexity and lower costs. The weSee technique is a different way of thinking and it can get an incorrect impression of some combined spade, rake, pitchfork, skewer and hammer in one and the same tool. A combination of the following types of programs: GoLive, MySQL, ftp-uploader, iLife, Sofie, Disgen and Preview would however be an expensive and difficult bastard that nevertheless can handle everything that can be accomplished by the weSee technique.

The essential requirement to identify an object in a picture (a house for example) and an object in another picture (a certain place on the map for example) as well as linking these together canbe obtained by the weSee-technique. Or by moving a pdf-file from Stockholm to Tokyo for example though the Internet, let the document change name and make existing links find the right object. The weSee-technique can handle information in twenty different languages in one single BDF-file. A regular Homepage technique requires at least twenty files to accomplish this. The main difference between the weSee-technique and old Homepages can be described in the following comparison.

Homepages are based on a main document, 'main.htm', which usually is designed by support from HTML and/ or JAVA or similar languages. The file usually uses the suffix htm. In the document, there could be other URL-addresses (i.e. links) to other files by the kind of files like pictures, sound, documents, videos and movies as well as other HTML- and/ or JAVA-documents. Special programs like GoLive, Frontpage and Dreamweaver as well as educated and well-trained individuals are required to accomplish HTML- and JAVA-documents.

An advanced and expensive database technique (such as Sofie, Cumulus and Primus as well as FiIe- MakerPro and Access) is necessary when you would like to work with a library that consists of several pictures and documents. Metadata for linked pictures and documents are saved in databases and /or in Homepage documents. The receiver is using a web reading-program by the type of Firef ox, Opera, Safari, Netscape and Internet Explorer. It is not possible to identify an object in a picture, like people in a wedding-picture or cities on a map, or pictures on an air crash with inquiry comments for example. Instead you make an empty space in the Homepage document and you putt the photography or map in that area and the belonging text in the Homepage document. This is very time-consuming and furthermore there is no guaranty that the text will belong to the correct picture or map or that the pictures or objects are by the right size. If the sizes change the picture or map will end up in the wrong place. If the picture file is moved, copied or the name is changed the meta-information is lost and prevented from working as a flow of information. This is exactly what will happen sooner or later.

The weSee-technique can be compared with digital postcards, where there is no HTML- JAVA or similar types of files with metadata. All the metadata is placed in the picture- or the document file (usually jpeg-, tiff- and pdf-files). Therefore, the picture and belonged metadata cannot fall apart and/ or get separated. The result is permanent and the long-term possibility of saving and maintaining it gets more or less timeless at no cost. It is possible to make a copy of the picture-file, change the size and resolution as well as giving the picture-file a new name and all the meta-information will come with it automatically, in the same way as a paper postcard can get copied, change size, be delivered /received and saved. This simplifies the work at makes it more cost-efficient.

The pioneer E-card technique according to preceding innovation consists of twelve steps or building components. The first step constitutes of an already famous technique for metadata; IPTC and XMP. The following three basic elements are described in the American patent application US 11/145,275, which

summarizes the used part of the inventions two to four in the weSee technique in the following ways: Identification of objects; the linking of objects together as well as the fourth step - the link with the operator.

The pioneer E-card technique according to preceding innovation consists of twelve steps or building components. The first step constitutes of an already famous technique for metadata; IPTC and XMP. The following three basic elements are described in the American patent application US 11/145,275, which summarizes the used part of the inventions two to four in the weSee technique in the following ways: Identification of objects; the linking of objects together as well as the fourth step - the link with the operator.

The following building components five to eleven enter into the new components in the preceding invention. The fifth component includes an advanced global working, UID-addressing. The sixth part of the component includes a special designed supervisor, the "Watchman". The seventh component constitutes a metadata deposit-technique for a fast search of information regarding documents and pictures. Step eight consists of a technique for multiple languages. The ninth consists of using automatic translation of languages. The tenth component consists of a technique that is used when working with forms. The eleventh component is necessary to finally make the technique simple to use and mange in a logical way and graphical interface. The twelfth component is a method of using weSee's unique characteristic of marketing itself.

None of these components are independent in a sense that it would have a value by itself. It only has a value together with the other components. This dependence of a relationship is symbolized in the figure as building component 0. One of two basic prerequisites for everything is that all the components of the invention are adjusted to each other and collaborate entirety and to the individual's ability of abstract understanding.

The second prerequisite is that the interface is simple to use, and described by itself, which is a difficult task since the correlation between the mutual building components and between the data and the different building components is a great anticipation. One detail in the steps of this invention is a platform for plug-in programs which has not been presented yet. This kind of plug-in program is able to handle family's traits. Other programs can handle animal or plant breeding, simple material-and-production, art collections, Interpol's query etc.

LIST OF FIGURES AND APPENDIX

Figure 1 is a summary and demonstrates the relations of the different components of the invention from zero to twelve.

Figure 2 demonstrates the principles to identify objects and how to link them together. Figure 3 demonstrates a link with the operator and hierarchic used vectors to information. Figure 4 demonstrates principles for a hierarchic links between folders. Figure 5 illustrates a practical use of objects and links. Figure 6 demonstrates a comparison of the weSee technique (at the bottom) and traditional websites (at the top).

Figure 7 demonstrates a meta-window for BIO and links.

Figure 8 demonstrates an example of a 'navigator '-picture with objects and links. Figure 9 demonstrates how the Homepage method is handling multiple languages. Figure 10 demonstrates how you insert and illustrate text in multiple languages in BDF-files. Figure 11 illustrates the new technique to use for tourist information. Figure 12 demonstrates a method of using automatic translation of text in a form. Figure 13 demonstrates a way of designing forms. Figure 14 demonstrates a picture display, objects as well as a tool-list. Figure 15 demonstrates a search by use of index files. Figure 16 demonstrates the use of cluster and Internet. Figure 17 demonstrates interface and the use of plug-in programs. Figure 18 demonstrates marketing and the avalanche method. Figure 19 and 20 demonstrates objects with three dimensions.

Figure 21 demonstrates GUI - technical and use oriented interfaces as well as marketing. Appendix 1: Description of how XMP- meta data are organized. Appendix 2: Principles of managing multiple languages.

DESCRIPTION OF APPLICATIONS AND RELATIONS

The application refers to a method of managing metadata for BDF-files.

The method's different steps (1) contain a metadata that belongs for example to a picture and its object is saved directly in the picture file in lasting way.

The method step (0) as well as (2-5) makes the identification of objects and satellite-objects possible as well as functions in addition to what can be accomplished by the web-page technique in a lasting way even though the picture get moved and /or name changed. The method step (0) and (6-7) replaces traditional database-technique.

The method step (0) and (8-12) together creates a self -instructed and intuitive interface so that an extensive training is avoided. This is a challenge and great invention because of the numerous functions, data quantities and structures are very great, and the correlation between them unnoticeable many with multiple dimensions. Based on principle reasons this cannot be accomplished by the web-page technique.

This invention consists of various part-inventions where the number of synergies and correlations is huge. The top of inventions are usually based on how the different building components are linked together and in the process of saving information, linking information, moving information, saving information in the long run, searching for information, and selectively demonstrate information as well as in the methods of demonstrating information. The freedom you have with computer programs and on the Internet and the possibility to work with 7 or more routes are in a result hard to reproduce in paper with two dimensions, see building component (12). The description of the invention is therefore to an extent indirect with help by examples and figures.

A detailed description of the new technique is best described by referring to the figures where figure 1 is a summary of the featured components of the invention as well as how these correlate. Figure 2 and 3 illustrates the new technique that is described in patent-application US 11/145,275. Figure 4 to 15 demonstrates the graphical design and the detailed building components that are included in preceding invention. Figure 16-18 illustrates the use of the Internet and its surface.

Figure 1 illustrates the invention's building components, where the first one is based on already known technique for meta-data, the IPTC and XMP.

Building components 2 (two) in figure 1 admits that objects in digital pictures and even in documents with multiple pages can be identified. See 2, 7, 11, 12 and figure 14 for an example. Pictures, documents and objects can be a of different kinds as:

• MULTI - many people in the same picture for example

• MAP - usually a map in graphic design of a picture; see the center of figure 5.

• BIO - biographic information of a person, or animal, or plant, see figure 7.

• OOO - different options based on needs.

Satellite-objects are a kind of sub-object, a textbox for example. See figure 8, 11 and 13 among others.

Building-components 3 (three) in figure 1 illustrates how the objects can be linked together. The objects can include links that might end up as aims in ones computer or globally though the internet. The aim can be a folder, a file or an object in a file. They are usually by that type, -jpeg, -tif and -pdf (BDF-files), but even other types of files can occur.

Building component 4 (four) in figure 1 demonstrates the function with links containing operator (OP) and vector (RANK). Links can contain an operator that describes the relationships between the two objects that's linked together; see figure 3. An operator can be a set of pictures or a movie that illustrates how two parts of chair can be glued together for example. Links can have an indication of information usually of hierarchic kind "UP, DOWN, LEFT, RIGHT, FORWARD, BACKWARD and CLONE". It makes the use of simple Material- and indication of production possible. One extraordinary case by using operator and rank is to build a family-tree where the operator and rank is built-in in the same word: "FATHER, MOTHER, SON, DAUGHTER, BROTHER, SISTER, CLONE etc". You can find this in the weSee application under the BIO type; see figure 7. This is also illustrated in figure 5 down on the left side.

It is possible to decide if you want the "FATHER" operator to be anonymously with up, down, left or right depending on how the graph is desired to like on the screen and the print-outs.

Building components 5 (five) demonstrates the step of the invention with an advanced addressing with help from UID, "unique identification", where the aim of a link can be found even if the file has been • moved or if the name has been changed. The technique mentioned in the patent application US 11 / 146,275 works locally, but is not enough for a global function. It can be achieved in combination with building components 6 and 7. A different option is to cooperate with search engines like Google and Picsearch to find UID-information that is needed. The last known addresses in a local link-register are saved but it is not necessary to make it work, it works more as a complement in order to work fast.

Building components 6 (six) is made out of watchman-technique.

When loading, updating and searching of XMP-files it is not necessary that the entire picture- or document file opens, it is sufficient to open the part that contains XMP-data. It means that the weSee program can scan small picture- and document archives (up to a few thousands) in short period of time. For larger archives (>ten thousands files) it takes too long for the user to just sit around and wait to see the result. To reduce the time index and some meta-data is saved in a register or an index-file. Note, the register does not contain primary information; the objective is just to speed up the search. Since the files can be moved from and to the computer and server in an uncontrollable manner for the weSee program is the last mentioned register updated where a background process with low priority is searching for changes. If a time of change in the weSee-modified file is not line with the same time in the register-file it is indicating that an update is needed and work from there. The functions checks that the modest and fast imported file (see building-component 7 down below) contains all the updated information and use its quickness and address width that the method allows.

Building component nr 7 (seven) is made out of Meta deposition.

The above mentioned watchman-technique does not work over the Internet. Search-engines like Google and Picsearch that is using spider-technology can get called, but it not sufficient. It assumes that all these search engines reads XMP-data which is not always the case. Also, those search-engines does not find BDF-flies that missing URL-links and Internet-servers does not allow outsiders to access a domain's content without stating the correct/ exact URL. In order to search time efficiently in small and large picture- and document-archives through the Internet, the weSee program prepares and updates therefore the index-files every time the ftp-function is used. The list of files down below illustrates the principle of how it will happen, where files with the name ws-index.xml contain an extract of XMP-metadata from all files in the folder, necessary for a quick search:

The file ws-index.xml can be described as a part of a distributed database that quick and easy can be distributed and found by the weSee-program for a quick search.

1 FoldernameOl Other actual file types are:

2 ws-index.xml 2 ws-tnOOl.zip

2 PictureOl.jpg "styles.css"

2 RdESf ^{" as} S ^{uide for sha} P ^{e of} characters,

2 2 P DioctcuurmeOe4n.tti0f1.pdf "t trraanns _sl l _a att _o orr"

2 Document02.pdf as guide for translation,

2 Document03.pdf °

2 Foldername02 navO2.pdf

3 ws-index.xml Navieator03.jpg 3 ws-tnOOl.zip - . ..

3 ws-tn002.zip for navigation,

3 ws-tn003.zip

3 PictureOl.jpg sekvcnsOS.xml

I _FO lSfJ ₃ alternatively

4 ws-index.xml sekvensO8.seq

4 Pictureozjpf ^as guide for interactive "slide view".

4 PictureO3.jpg

3 PictureO3.jpg

3 PictureO4.tif

3 Document01.pdf

3 Documont02.ρdf

3 Document03.pdf etc.

Figure 15, illustrates what it can look like on a screen where (1) is the physical storage, (2) indicates URL, (3) demonstrates how to search and (4) constitutes the index-files in question.

The technique opens fantastic opportunities of an international collaboration. A trade fair for tourists in Berlin has participants from all EU-countries and it has been decided that the weSee-technique will be used instead of the old Homepage-technique. Tn a result webmasters and database technicians are unnecessary. One or a few participants from each country will represent the country's need of what will be shown via the Internet. What the Greek employee does is all of sudden accessible for everybody. There can be a conflict if more than one would like to update the same file at the same time. With semaphores these kinds of problems can be solved in customary manner. The files with names like "ws-tnθl. zip","ws-tnO2.ziρ" etc is 'thumbnails' of pictures in the folder. The only purpose is to make the illustration of the folder content faster. It is an option that can be chosen in "Setting" to the weSee-program if it will be created or not. There should be different options of algorithms to chose between. There is no point of making a little "thumbnail" of a small picture that is not larger than a "thumbnail".

There are various situations that can be managed by the "watchman-technique"- and semaphore technique. Figure 16 illustrates situations.

(A) A cluster of domains updates the same Internet-domain. With help of semaphores the collision of updating the same file is prevented. If the same semaphore is used even in ws-index.xml-file it will result in that no more than one can update the file at the same time. It can then be better to let the help-file " ws-tnOl.zip", "ws-tnO2.zip" etc not be correctly updated in these situations. The error will be discovered within a short time-period and be edited by the "watchman-technique", see ditto above.

(B) Your computer is equivalent since the weSee program is able to update the same files through parallel precesses and since different weSee-programs can be running at the same time in one computer.

Building component 8 (eight) refers to the general management of different languages. The language-technique is important for a wealthy culture, cultural heritage and for economic success. The technique must be so simple to use that is available for everybody and not only for a few. This can be accomplished through an integrated system that is designed by simplicity the entire way from an individual to a digital file somewhere in the world and thereafter back to an individual. Based on the basic principles this cannot be obtained by the Homepage technique. By the weSee technique it is easy to communicate without any language barriers. Details and GUI are left to the programmers to design. Part of the invention and the principles to follow are:

1 Everyone that is typing text to XMP-metadata should easily be able to see current language. See figure 10 and figure 14 above part details 5, 12 and 13.

2 The text should be marked with a language-code, see appendix 2.

3 It should be simple to change language in between words.

4 When needed it should be simple to send a part of a text to automatic language translation, figure 12.

5 When the translated text is received it should be simple to edit and change it as well as save it as a new text based on the assumption that there is writing rights for the file.

Appendix 1 and 2 illustrates (simplified based on pedagogic reasons) principles to save information.

It is important to keep following apart:

• Fonts that comes with different languages. In order to manage different fonts there is a task in operativ system that is considered in this patent application.

• Country code where it usually follows the ISO-standard 3166.

• Language code where ISO 639-1 mainly is used.

It is significant to keep language and country code apart even if a country's flag usually symbolizes a certain language. See figure 10 and 13. Also see:

- http:/ /www.w3.org/WAI/ER/IG/ert/iso639.htm and - littp:/ /www.oasis-open.org/cover/countrySlβδ.html

- ISO 639-2, published in 1998 with three signs and 460 languages.

- SIL with more than 7 000 languages.

In a document: "Well-structured XML Goes Cosmopolitan" by Hari Aamio, 2003-06-04, this appears Jf is sometimes challenging to create and organize XML documents. Tins is even more true if the document content needs to be presented in several different languages. It makes it harder to keep the document content up to date. But don't despair. Wlien supporting multiple languages in XML, the key to success is to pay close attention to how you structure your documents. Following a few simple rules will help a lot.

1. Content-oriented structure.

2. Transforming the content-oriented structure for midtilingual resume.

3. Language-oriented structure for a multilingual resume.

4. Transforming the language-oriented structure for a multilingual resume.

5. Separating each language into its own document.

6. XSL style-sheet to produce the localized language version from separate XML documents.

The EU-commissioner representing multiple-languages, Leonard Orban, uses method 5, see figure 9, which probably is the only practical way by the Homepage technique. See http:/ /ec.europa.eu/commission_baπOSθ/orban/index_en.htm.

One or more of the above mentioned ways are appropriate to combine with the weSee technique. It is very important to develop an efficient GUI in order to choose and present a selected language and meta- information in every situation. Here is two possibilities, direct (M=manual), and indirect (A=automatic) in order to accomplish a simple function. None of them are possible with the Homepage technique based on principle reasons.

M - Registration of data: Text in one or multiple languages are stored in the meta-part of the picture- or document-file, see figure 10.

M - Reading of data: the screen illustrates the text in the one language that agrees the most with list of priorities in the user's computer, see figure 8, 11 and 13.

A- Metadata is delivered for automatic translation, received translated and demonstrated on the screen. To make a language list there is a standard function in Macintosh, see figure 11 on top to the right. In Windows this kind of priority list must be accomplished in another way, probably in the programs 'Settings'. When it is completed actual text can be matched with the priority-list and the best choice will be shown. How the weSee's multi-language function works is illustrated in Appendix 2.

Building component 9 (nine) manages multiple languages with automatic translation.

If the requested version of language is not available as XMP-data the user can chose to send the text for automatic translation. Since it performs on an object basis it is an easier and nicer way to manage than the Homepage technique. See figure 12, and figure 8, 11 and 13. The translation is also better since it is possible to mention the type of technical language that is used.

You can anticipate needs by four types of textboxes:

• The fixed text cannot be modified neither translated. Use: Name

• The mod text can be modified but not translated. Use: Name o The fixed-trans text cannot be modified but can be translated if needed.

• The mod-trans text can be modified and will be translated if possible.

The text that will be translated, will be packed by the weSee program to packages that brings together to containers that will be sent for translation. Every container contains addresses and text which describes the circumstances. Every package contains a body and text that will be translated. The body contains necessary information for the translator, if possible even subject-area in order to choose appropriate technical language. The translated text will be returned in a similar way, be packed up and illustrated in the right places. The text will be stored in the computer temporarily, if the user requests, and after a possible improvement the new text will be stored for future needs in direct method, see above. In one or more URL there is information regarding the existing automatic language translators and their characteristics, eventual cost and how to make the payment, illustration of how the text should be prepared etc. In the weSee program there is a built-in function to recall such URL and extract necessary information.

Building component 10 (ten) refers to form-technique.

Nothing extra is needed in order to use the weSee to manage forms, see figure 13, compared to the tourist-information on figure 11 and figure 8. The forms background picture, with or without text can accomplish programs like Photoshop, PowerPoint and Illustrator. But it can even be done by hand on a paper or by an existing form that gets scanned into the computer as a digital picture. 'Magnetic' outlines can simplify of getting the objects pleasant and placed exactly. To manage the weSee forms in combination with an automatic and manual language translator is a very interesting opportunity especially for EU's "24-hour authorities". It is also possible that this kind of forms can be "bank-secure" and in that case be used as digital agreements, invoices and checks in a future payment-system.

Satellite-objects can be positioned in three different ways:

1 - No specificication whereby an algorithm automatically decides position (figure 11).

2 - Form and position is decided as for objects, in other words by decimal digits (figure 8).

3 - Satellite-objects, like objects, decides placement with help by magnet lookalike frame-lines (figure 13).

Explanation to figure 13:

The figure illustrates how to construct a form.

• The background is made out of a picture.

• Choice of original-language.

• The user's choice of translation.

• Frame lines with magnet lookalike characteristics.

• Links in the document.

Component 11 (eleven) is made out of interface. We make a difference of three diverse interfaces:

• GUI refers to interface opposed to the individual /user. Since the human eye often is called the mirror of the soul, the program's GUI become the mirror of the invention and illustrates the quality of the work behind it. WeSee is from the beginning a sophisticated picture- and document illustrator that works just as well locally in ones computer as globally over the Internet. Figure 14 and 21 and some other examples mentioned demonstrate the principle communication between a human being and the machine, while the picture-based design can illustrate a somewhat different appearance. Picture 1-21 illustrates the main-characteristics of interface to the individual/ user. GUI is dynamic, multi-dimensional and interactive with unpredicted relationships.

• Interface against surrounding technique, mainly the Internet and the local computer is a question that has to be raised for programmers to design in the best way.

• The design of the different components in the preceding weSee technique and their adjustments for each other is of great importance regarding the quality and ergonomic and has a great impact regarding the possibilities of creating a well GUI.

Figure 17 illustrates the programs foundation that consists of a program-body with a built-in interface for the main functions. For special needs there is a possibility to plug-in programs that is attached to the program-body. With intension to simplify such use the interface should be structured and openly specified. Following examples of the use illustrates the function:

• Museums in EU, the US or Kina might use different standards and GUI to show digital archive- pictures. With plug-in programs it is possible to adjust for these special needs. ^β Breeding, animal-parks and individual human beings all have needs to follow up on f amity-traits. The same technique can be used for human beings, but the vocabulary and circumstances differs. This can be accomplished by plug-in programs.

• Interpol can have a need of special requirements for the fight against terror and the search of individuals and objects.

• X-ray diagnoses are very much like the police task of getting photographs from a crime scene, or by an archeological excavation, identify and describe the item, but there are also differences. These differences can be managed by the plug-in program which also creates GUI.

• Existing picture-archives by the type as FileMakerpro, Sofie and iPhoto could by assistance of a plug-in program convert to the weSee technique and then be accessible in both ways, more about this in 'Component 12' down below.

The E-cards method GUI is a synthesis of following items and more:

1 Picture/ document is the starting point and the basics for the E-card technique which is a good and fast way of expression for the human being, compared to the Homepage technique where codes and usually tables are the starting point.

2 The objects are shown once the mouse is touched.

3 The satellite-objects are shown once the pointer touches the object.

4 The information is shown in the "right" language immediately if there is availability, it is simple to change language and to send texts on objects- and satellite-level for automatic translation.

5 The tool-box is illustrated by a certain commando.

6 Groups of metadata (name, place, coordinates, and search-words for example) are shown selectively and by request.

7 The position on a map is illustrated by request if there are coordinates.

8 Coordinates can be local, national, and/ or global in three dimensions.

9 Built-in email-function for simple communication.

10 Images and objects that are three-dimensional are illustrated with layerttechnology and with help by the arrow-keys.

11 Satellite-objects are usually a text-box, but it can also be a movie, music, picture or another object by help from an operator in Component (4).

12 Satellite-objects can have a hierarchal structure (3) + (4) like a family-tree to a limited extent for example.

13 By request, the little structure /family-tree can be shown on the screen with many structures on top of what was on the screen earlier; it is then simple to go back to the starting point. The structures can be a BDF-file in ones computer or on the Internet or both at the same time (render possible by Component (6) and (7) in combination with (Z), (3) and (4)).

14 By help from Component (6) and (7) and by the use of the arrow-keys -> and <- it is possible to also reach unlinked files which is not possible with the database- and Homepage technique.

15 By help from Component (6) and (7) and the arrow-keys UP and DOWN you can get to navigates- files (corresponding index-files) which are not possible with the database- and Homepage technique.

16 The meta-data is dynamic. At data-entry all the possibilities are shown while only the necessary fields are shown through a display.

17 The meta-data can dynamically adjust to the plug-in programs (figure 17) by need.

18 Component 10 the "form-technique" is no detached technique rather a function and a GUI that is compounded by mostly all the other building-components and in particular

(2), (3), (4), (8) and (9) and mostly a synergy of all these.

19 The method of separating geographic information by occurrences and relationships as well as the concept clonelink.

20 Files of sequence with help by interactive slideshows can be accomplished locally and over the Internet at which component (4) operator in link allows for the sound and movie-sequences that comes with it. The function assumes the components 6 "watchman" and can also use Component 8 the multiple-language technique.

21 The emulator by the type of Javascript, Javaaplet and Flash which by need can be assembled in an optional Homepage browser at which a pleasant and for the user almost unnoticeable transition between the E-card technique and Homepage technique takes place.

22 "Demonstrator" is a very unique characteristic that is based on all the building-components and in particular in (1), (2), (3), (4), (6) and (8). The above mentioned picture slideview (-20) and emulator (-21) are essential functions just like the e-mail function (-9) in figure (-21).

The demonstrator is a sequence of modifiable picture-files that are in control by the slideview-files, (Demo-OO.xml) alternatively (Demo-OO.seq).

Component 12 (twelve) is made by the user and the market.

The method and the program weSee have the unique characteristic and ability to market itself by the avalanche-effect, see figure 18 and 21 and component 11 point (-20) and (-21). Since the technique is very abstract and compounded by many parts in time, room, correlations, functions etc. it is very difficult to understand from a description based on just words and pictures. When demonstrated almost everyone can understand and use the method in a very short period of time. It can be compared to learning how to ride the bike from a drawings, mathematics and descriptions in comparison to a visual experience. It is illustrated in two examples.

* Example 1 - Aircraft-museum: An international interesting museum like the Aircraft-museum in Linkδping for example decides to use the weSee method for their digital picture collection. Approx.10000 meta-dated pictures are posted to an Internet-server. They have access by both the Homepage technique and the weSee-technique and the pictures are shown with an alert at the same time which is indicating that is should be opened with the weSee program for more information. For further information and link this process simplifies which results in the user's access to the weSee program in ones computer. The user now has the opportunity to try the weSee-method for one owns pictures which results in an increased knowledge. He will probably discover the simplicity and that he can get information regarding the picture in his own language. If the user appreciates the program he or she will probably start using it themselves and might influence a contiguous society to do the same. In this way, an explosive

^' development of knowledge and usage has passed on to many people.

* Example 2 - The EU-Commissioner Leonard Orban: Assume that L Orban who is responsible for among other things multiple-languages, whishes to send a message that his staff has been reorganized to 1500 employees in the circle of contacts. He chooses to use the weSee method and delivers bjr email (see figure 21) a weSee prepared picture by the jpeg-type with an attribute to the 1500 receivers in different countries. These are then encouraged to download the weSee program in order to read all the information regarding the picture and will then discover the weSee-methods techniques. They will probably then start using it for their own needs and an explosive development has started.

To use the weSee E-card technique for an email is done in following ways, GUI see figure 21: You take a picture with a digital camera and adjust the size, gamma etc in the regular way. The picture is opened with the weSee program where a tool-list is shown. Afterward:

1 Choose language.

2 Choose e-mail function.

3 Choose one or more e-mail addresses from your address book or type new ones.

4 Create an object, type and edit text.

5 Create a satellite-object, type and edit text.

6 Create by need new objects in order to link to other folders, files and objects.

7 Send the e-mail.

8 Usually the receiver receives the picture in a JPEG-type in the email. It then assumes that the receiver already has the weSee program installed. But it is not necessary, see down below.

9 When the receiver touches the mouse the objects and the meta-information is shown. It will disappear after a while.

10 The picture can be stored i the family album and the information will be stored att the same time.

Approaching the market/ users is thus an invention in itself which results in that the users receives an E-card prepared picture. It is delivered by either e-mail or by an internet-link and it is designed with an attribute so that a help-program, like javaaplet, is downloaded. It makes it possible for the user to read the meta-information and reach basic functions. From there, the step toward the actual weSee program is not far away. The program that is an E-card browser is able to cooperate with other Web-page browser, see figure 6B, so that the user barely notices the transition between Web-pages and E-card pictures. Sooner or later the E-card browser and Web-page browser will probably be compounded into one program. The computer-program weSee's E-card technique has a unique position since no other computer program or computer method has the ability to demonstrate itself in this mentioned way.

- - — w v « « ^« t>

Component 0 (zero) constitutes the overall picture.

The application describes multiple inventions that have been designed to cooperate. Every part- invention has been designated a special body and interface to other inventions, to the users, to the Internet and to your computer. To accomplish this and the pattern for how these take place is the main invention. The weSee's E-card technique makes it simple and cost-efficient for almost all users to use the Internet both for the sender and receiver of the information and to administer picture- and document archives. See figure 5 and figure 6. From the beginning weSee is a picture-show like Preview, iPhoto, Firefox etc. But it also translates programs like Frontpage, Golive and databases like Access and Cumulus by getting rid of that unnecessary technique. The versatility has not been reached like the composite of a "Swiss knife" but through a different a smarter technique where the complicated and costly parts are not required. Otherwise the simplicity at the same time would not have been reached. The simplicity is accentuated by that the same program is used for creating, writing, archiving, searching, illustrating, reading and surfing. This is the result of many inventions-steps that has been created and then put together in a special pattern as described.

Explanation to Figure 14, top part:

The figure illustrated how the toolbar is designed. It can be located in the screen's top part as on the screen or 'floating' and be placed where the user wishes. The function is the same even if the files are in the user's computer or on the Internet.

1 A red dot indicated that metadata can be updated. The file is then on the hard-drive or such and is not protected for writing. Click's illustrates windows for updates.

2 Termination of a slide-show, back to the meta-form.

3 The object-marks turn on/ off with the button (ellipse, rectangle etc).

^• 4 A) All the meta-information is illustrated with the button. If the pointer is on top of the icon without a click, the meta-window is just shown temporarily.

B) If the pointer touches the icon then the whole icon's function is demonstrated, so-called "Tool-tips" or "Screen- tips".

5 The flag-icon illustrates all the computer's current languages and representations of signs.

6 Move forward one file.

7 Move to the closest navigator, in other words to a file with the characters "navigator" is included.

8 Move back one file.

9 Move to previous.

10 Move to the folder.

11 Illustrates the original file with the original file marked.

12 A list that illustrates available languages, shown when the pointer is moved over the flag-icon (5).

13 Icon shows the language. Click on other alternative changes the language, compare figure 8.

Explanation to figure 14. bottom part

The figure is shown on a computer-screen (the example comes from EU's webpages).

• Computer-screen.

• Object.

• Form-text. Instant language.

• Cursor.

• Toolbar (can be move). Note: see the figure's top part.

• The image shown.

• Available languages.

The image is illustrated on the computer-screen. When the cursor moves across the screen and reaches an object the objects and its information (if there is any) gets marked, and demonstrated in chosen language. By a right-click it can be sent to an automatic translator.

3D, Three-dimensional applications.

What has been described earlier in this application as a two-dimensional technique is also allowed in 3D-technique. The majority of file-types as for example but not exclusively TIF-, Photoshop-, PDF- and GIF-files allow that you work with and save information in multiple layers, see figure 19. By identifying

an object in multiple layers it is possible to describe an object three-dimensionally and even link to other objects. In the most simplified version the edges of the object get attached, usually definite by a polygon with straight vertical lines inbetween the polygon-points. It is also possible to decide / estimate the objects three-dimensional form with a more advanced vector describing algorithms.

The layers are shown with help by a 'thermometer'-scale, see figure 20. The layer below the cursor (in the example figure 20 layer 1-6) has transparency = 0, in other words they are visible to a 100%. It means that only layer 6 is shown. The layer closest above the cursor is shown in transparency in relationship to the cursor's position. In the example, the cursor has position 6,7 which means that layer 7 is shown to 70% or with a transparency of 0,3. All the layers above the 7th layer has a 100% transparency, in other words they are invisible.

The following applications are mentioned as examples:

An archeological excavation where the neighborhood and its object is demonstrated in three dimensions.

A police investigation where on a map, vehicles and people has been inserted by the position they have at different time periods, so-called GeoTime where the map has two dimensions and the third one is made out of the timeaxis.

Reconstruction of battles during the 30-year old war.

Layered pictures of objects like an airplane, fossil of an animal or a plant, buildings, and historical objects.

Layers of a map that illustrates the coast and how the land's height has increased during thousands of years.

Layers of a city's development.

An interesting area of use for the weSee E-card technique would be a conversion of computed tomography pictures in a DICOM-standard to the weSee-XMP-f ormat. After such conversion the picture would be more "manageable" and adjustable in order to use in lectures, educations, and in communications between the doctor and patient etc.

Explanation of figure 19.

The figure shows an image with multiple, in this case 8 layers, in order to reproduce objects in three dimensions. By multiple dimensions there is in every layer a market object, here marked by a red circle.

Explanation to figure 20.

The image illustrates a multilayer picture, 3D-image, demonstrated on the screen.

1 A reproduced 3D object, marked off with a red circle.

2 Scale in order to mark what layer, or position in between the layers, that will be illustrated.

3 Marker that manually can be moved up (down) on the scale.

4 Icon to automatically move the marker up (down) on the scale.

5 Positions for the different layers.

6 Toolbar.

7 Marked object that can be stretched through multiple layers and thereby restrict a three-dimensional object.

TECHNICHAL APPLICATIONS

1. Description of how to register metadata.

The XMP-data can of course only be inserted if the file exists on a media in ones computer with the right to update. With the weSee-ftp utility even the Internet- and Intranet-servs updates with XMP metadata. Programs like Photoshop (Use: File — > File info or Window — > File Browser), and Acrobat can be used to write or read simple XMP-based meta-information. By using the weSee-program, files from internet can be downloaded and then readable and updated and the links can be followed. The file-collections can be updated in both the local computer and on the Internet-servers by weSee-prepared files with all the ftp-programs. But if weSee-ftp is used the index will be updated automatically at the same time, see figure 7, building-component 7.

On a digital picture or document an object can be identified as rectangle, ellipse, and polygon or by a dot identified by an arrow. Such objects could be a person in a wedding-picture or members in an organization, see figure 8. In the last example it is appropriate to name the file '01-navigator jpg' since it then can be used, by help from links, to navigate in the organization. Note that the file illustrated in figure 8 is a picture-file (-jpeg or -tif) or a document with multiple pages (-pdf).

You create an object (component 2) based on following ways, see figure 1:

• Choose color in the 'toolbar' see figure 8, the left part.

• Chose graphic design, rectangle, ellipse, polygon or a dot.

• Move the cursor to the object, touch the mouse and move it.

• Adjust the position and size.

• When many objects should be adjusted it is practical to use the magnetic lines, see figure 13. Before the meta-information is inserted to the object the preferred language should have been mentioned in Preferences (Window) or System-settings -> Internationally (MAC):

• Double-click or right-click on the object to get the meta-window.

• BASIC for Folder, Image or Document with or without an object.

• MULTI for ordinary pictures and documents with or more objects. ^β MAP for pictures with coordinates that can be used as a map.

• BIO for Folders, pictures and Documents that contains biographic information.

• Change of 'CASE' can be obtained as an option.

• Write all the meta-information in the fields.

• Save.

When the screen's cursor moves across a picture or document and then reaches an object:

• The object is marked.

• The meta-information (if there is any) regarding the object is shown.

• The meta-information will be shown in chosen language according to priority-list.

• By right-clicking it is possible to request that the text is sent for automatic translation, see figure 12.

If the object has a link the cursor transform into a knocking hand. If the hand knocks on the object by a mouse-click, it follows the link and the linked file /object is illustrated:

• A list of files (index) if the aim if a Folder and/ or a Folder's metadata.

• A picture with its metadata regarding the object and links.

• A document with metadata, object and links. ^■

You can make a copy, change size and resolution with optional program, based on the assumption that the program leaves the meta-data untouched, the files is moved by email for example and given a new name and the objects are still there with the correct position and size.

The description above illustrates the elegance, simplicity and low costs with weSee's E-card technique which cannot be accomplished by the Homepage technique based on technical reasons.

2. How to create links.

• Right-click on an object and an object-window is shown.

• Metadata can be inserted in the window.

• There is also an icon with a drop-type, do following:

• Pick the folder or file that will be linked.

• Macintosh — Drag-and-drop it at the drop-icon and then a linked has been created.

• Windows — instead of drag-and-drop pick the linked file in the regular Windows way.

If you would like to link a particular object there is a small procedure for picking the object at the right page in case it has multiple pages.

3. How to manage multiple languages.

See Appendix 2, and figure 10 and figure 8.

4. How to use metadata in a search.

When searching, the program has to be able to manage a number of different situations, search-methods, search-concepts, varied languages and collaboration with external search-engines. When searching on ones computer and server you mention what unit to be searched and at what rotfolder the search should begin with, see figure 15. When searching the Internet you will indicate the URL as rotfolder.

1 By searching the aim of links (see the section regarding links, building-component 3).

2 By searching certain areas in ones computer, local server and selected places on the Internet. No prepared GUI as search-function has been created, but there are many role models.

It is important that the user find and understand the graphic. It should therefore look like the computer's natural search-function no matter if the operativsystememt is LINUX, MAC or WINDOWS.

3 Global public search. The weSee-program has no global search itself but it can use search-engines like Google, Yahoo, Ask Jeves, Picsearch etc.

4 By searching in specific fields, examples would be: Headline, Intention, Project, Date of the object, Country, Province, City, Parish, Place, Library, Source, Worked on, Right, Secretes, First name, Surname, Date of birth, Date of death etc.

5 By searching a location (country, city).

6 By searching a word-search (Red, croft, knuttimrad). The weSee program is prepared to handle word-searches. However, word-searches should only be used in special situations. In most cases, it is better to have the word-search included in the description of the object or as a coded search, see down below.

7 By searching a phrase, for example "the giant Garp". Free field search.

8 By searching in different languages. The program's function of an automatic translation can be used. See the section of how to handle multiple languages.

9 Internationally coded search. In international collaborations different code-tables (* Outlines) are used for different occurrences and objects. In this way you avoid the difficulty of search-words in different languages. To insert such search-concepts in the XMP-schedule is trivial.

* Outline (a quote from www.hembygd.se). Most Swedish Museums are today classified by an Outline (Outline of Cultural Materials - OCM) a system based on number-codes for different terms. Outline, Samoreg and Sweterm are different standards and aids for your work-document, glossaries are available on the Internet.

A professional in this area realized that applications and modifications based on the mind of invention can be combined, developed and designed in many ways. For example, the invention is integrated with ^■ existing programs like Internet Explorer and Firefox as well as Sofie and similar programs.

APPENDIX

Appendix 1

DESCRIPTION OF HOW METADATA IS ORGANIZED AND STORED.

Below principles of how metadata are organized in the file "Fig2a.jpg" are shown. The description is edited by pedagogic means and is not technically correct.

> GENERAL FILE INFORMATION

<rdf:Descriptionrdf:about='uuid:7becd8d3-e966-lldb-b4a O-844c8cl590b7' xmlns:xap='http:/ /ns.adobe.com/xap/ 1.0/' xap:CreateDate='2004-04-UT02:27:51+02:00' xap:Modi£yDate='2004-04-HT02:27:51+02:00' xap:MetadataDate='2004-05-08T12:17:01+02:00' xap:CreatorTool='Adobe Photoshop CS Macintosh'>

^' xmlns:nff='http://ns.adobe.com/tiff/1.0/' tiff:Orientation=T tiff:XResolution='100/l' tiff:YResolution='100/l' tiff:ResolutionUnit='2'>

<rdf:Description rdf:about='uuid:7becd8d3-e966-lldb-b4a0-844c8cl590b7' xmlns:dc='http:/ /purl.org/dc/ elements/ 1.1/' dc:format='imagc7jpeg'>

<dc:descripUon>

<rdf:Alt> > NOW FOLLOWS weSee INJECTED XMP-METAD ATA ρhotoshop:Headline='weSee' photoshop:Country='SE' photoshop:DateCreatcd='2004-04-ll'

(Note: copy to <ws:Date> copy from EXIF DateTimeOriginal if existing) photoshop:Source='weSee'>

<rdf:li xml:lang='x-defaulf >The weSee principles to identify objects and link them together.</rdf:lix/rdf:Alt> </ dc:description>

<dc:creatorxrdf:Seq>

<rdf:li>Lars Cornell</rdf:li>

</rdf:Soq>

</dc:creator>

</ rdf:Description>

</rdf:RDF>

</x:xmpmeta> > NOW FOLLOWS OBJECT INFORMATION xmins:xap='http:/ / www.wesee.eu/ ws/ 1.0/'

. ws:Ob]ectType='l' <ws:Multi rdf:parscType='Resource'> <ws:MultiDataList><rdf:Bag> <rdf:li rdf:parseType='Resource'> <ws:Data>Exampre of a weSee link.</ ws:Data>

<ws:yl>0.459119</ ws:yl>

<ws:xl>0.578475</ws:xl>

<ws:y2>0.647799</ ws:y2>

<ws:x2>0.762332</ws:x2>

<ws:Pagol</ws:Page>

<ws:Shape>Oval</ws:Shaρo>

<ws:Color>6496,0,45341</ws:Color>

</rdf:lix/rdf:Bag></ws:MultiDataListx/ws:Multi&g t; > NOW FOLLOWS LINK INFORMATION

<ws:URL>http:/ / www.wesee.eu/ en/bilder/F2C.ipe</ws:URL> <ws:URRL>.. /FigO2b.jpg</ ws:URRL> <ws:UID>AB20F858-E7C3-llDB-9770-OOOA95966D50 -7becd8d3-e966-lldb-b4a0-844c8cl590b7x/ws:UID> <ws:Alias> </ws:Alias>

(Not: URL, URRL and UID are all used to search and find tine target of the link. If the target is an object in a multipage document additional information is needed.) > NOW FOLLOWS 'MAGNETIC GRID INFORMATION

<ws:gpixel>3+10</ws:gpixel> <ws:gyl>0.159119</ws:gyl> <ws:gy2>0.447799</ ws:gy2> <ws:gxl>0.178475</ws:gxl> <ws:gx2>0.562332</ ws:gx2>

19

; &uυo i y y y 3 « _j ^ *

Appendix 2

DESCRIPTION OF THE PRINCIPLES TO HANDLE MANY LANGUAGES.

The source is: http:/ /ec.europa.eu/ commission_barroso/orban/ index_en.htm Also see http:/ /europa.eu.int:80/languages/sv/chapter/17 and the edition method RTF.

<en>

- Many people speaking many languages -

Languages are fundamental for Europeans wanting to work together.

Promoting multilingualism in the different Policies of the European Union, such as culture, education, communication and employment is at the centre of my objectives. I want to make a real contribution to the competitiveness of the European economy.

<FTX>Leonard Orban</εIX>

</en><ro>

- Cunoasterea mai multor limbi de catre cat mai mulfi oameni -

Cunoasterea mai multor limbi este absolut necesara pentru ca europenii sa poata munci lmpreuna

Promovarea multilingvismului in diferitele Politici ale Uniunii Europene, precum cultura, educa|ia, comunicarea ori politica sociala constituie until dintre obiectivele esen|iale ale mandatului meu. Doresc sa contribui in mod real Ia competitivitatea economiei europene.

<EJX>Leonard Orban</FlX>

</roxel>

20