【正文】 ion. A closer look at a document may reveal that it consists of different types of images, primarily text, graphs, and pictorial images. These all have different image characteristics and representations such as ASCII (American Standard Code for Information Interchange) for text, vector for graphs, and raster for pictorial images. Each type of image and its associated attributes like the font, font size, halftone, gray level, resolution, and color have to be dealt with differently. In such a plex environment, there is no doubt that many patibility problems occur when an image is acquired, transmitted, displayed, and rendered. ? With the fast development of Inter technology, large volumes of data in the form of electronic documents from the Web. For the purposes of data integration and data exchange, more and more existing sources, such as relational databases, support public XML export, and increasing amount of public and private data is described in a semistructured way. A number of issues need to be addressed when we integrate data from different sources, including heterogeneous and duplicate data, multiple divisions and partners, and changes. ? Data heterogeneity results from the use of different information management systems to store data and each system has its own data structure and access methods. Relational database management systems benefit from the universal acceptance of Structured Query Language (SQL) as the primary means of getting answers whilst document and repositories are generally accessed using text search engines with varying interfaces and capabilities. Because these systems were not designed with interoperability in mind, each must generally be accessed using sourcespecific applications or application programming interfaces (APIs). ? Another difficulty in data integration is data duplicationdifferent systems represent the same piece of data in different ways. For example, customers may be identified by name in one database, but by account number in a second repository, may identify the same customer by address. Frequently a required piece of information is derived from multiple data points. Data integration is further plicated when customers do business with multiple divisions within a large pany, or with other partners. Similarly, answering questions about the state of a pany39。附錄 1 外文原文 COLOR SYSTEM OVERVIEW In the age of office automation and electronic imaging, office documents are being processed, transported, and displayed in a variety of ways. The scope of document processing is enormous。 it enpasses page layout, document length, collation, simplex/duplex, color, image quality, finishing, and binding. If the office system is worked, then another dimension of workrelated issuesprotocol, file format, page description language, pression/depression, job management, error handling, user interface, and device driverhas to be addressed. Digital colorimaging systems process electronic information from various sources。s supply chain requires access to vendor and distributor information sources. Doing business electronically across the firewall gives rise to security and data ownership issues. Finally, data integration has to deal with different types of changes。t have to close all those HTML tags. First you have to add the XML declaration and the root opening and closing HTML tags. Next, you start adding element opening and closing tags one at a time. Of course, once you have the initial sequence pleted you can just copy and paste to repeat the required elements. After doing this hundreds of times you39。s database which is an obvious attraction if the site uses Microsoft39。t fet that it is also possible to build functionality into the admin part of the site so that the cache would be flushed if new content is added to the database. That way the website administrator would not have to wait until the cache timed out in order for new content to appear on the website. Remember that data stored in Application variables is visible by all the users of the website。 the file, named , will be created automatically in a folder named DATA. Although not enabled in the build of Visual Studio against which this article was written, the Web Site Administration tool contains an entire section devoted to configuring personalization settings. In a later section, I39。ll walk you through this process momentarily. At this point, the membership database will be created, and the necessary configuration elements will be added to the file. All you need to do from here is add users to the database (which you can do using the Web Site Administration tool, or the membership APIs), set authorization restrictions on pages as desired, and create a login page. It is important to note that the database structure that is created for both personalization and membership is the same, so you can (and for efficiency39。re not willing to part with, allows you to use that and still get the benefits that membership services provide. Note that at the time of this writing, the actual means for creating custom providers could undergo some changes still, so I39。s the Data Stored Use Server Explorer to see how data is stored in . Just create a database connection to and drag tables from the connection to a page in your site. Visual Studio will create a GridView control and bind it to an AccessDataSource control (note that the worker process must have readwrite permissions on the folder containing the database for this to work). If you have difficulty browsing pages in the application, close the connection in Server Explorer before browsing the pages. Add Personalization and Membership Support Enough with the theory。s get to an example already. I39。 adding a user to the membership database。 and using those properties from a page, both for anonymous and loggedin users