COLOR SYSTEM OVERVIEW
(Y. Nayatani, K. Takahama, H. Sobagaki, and K. Hashimoto,
"Color appearance model and chromatic adaptation transform,"
Color Res. Appl., 15:210-221 (1990).）

?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 encompasses page layout, document length, collation, simplex/duplex, color, image quality, finishing, and binding. If the office system is networked, then another dimension of network-related issues-protocol, file format, page description language, compression/decompression, job management, error handling, user interface, and device driver-has to be addressed. Digital color-imaging systems process electronic information from various sources; images may come from a local-area network, a remote-sensing device, different color workstations, or a local scanner. After processing, a document is usually compressed and transmitted to several places via a computer network for viewing, editing, or printing. Moreover, the trend in the industry is moving toward an open environment. This means that various devices such as scanners, computers, workstations, modems, and printers from multiple vendors are assembled into one system. Implementations should be based on public-domain technology rather than proprietary standards. This will allow vendors equal access to the market for system components and give users the widest choice in selecting components. It is a vastly large task to enable the communication of all system components regardless of differences in the operating system, file format, page description language, and information content. Ideally, the exchange should not cause information loss or alteration. 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 complex environment, there is no doubt that many compatibility problems occur when an image is acquired, transmitted, displayed, and rendered. ?

With the fast development of Internet 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 semi-structured 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 email 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 source-specific applications or application programming interfaces (APIs).
? Another difficulty in data integration is data duplication-different 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 email address. Frequently a required piece of information is derived from multiple data points. Data integration is further complicated when customers do business with multiple divisions within a large company, or with other partners. Similarly, answering questions about the state of a company'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; change in business requirements and strategies, in IT systems, mergers and acquisitions, and new product launches. This demands that a data integration solution be sufficiently flexible and adaptable.
One possible solution for the data integration problems mentioned above is to provide an XML Web services break down the barriers between different computing platforms, development environments and communications networks, allowing organizations to work together electronically without the expense and delay of agreeing on semantics, schema, interfaces, and other application integration.
XML provides the flexibility for handling data with differing structures. As XML is becoming the principal medium for data exchange over the Web and for information integration in general, increasing amounts of public and private data are described in XML. XML data is usually defined in a tree or graph based, self-describing object instance model (Boncz and Kersten, 1999). However, semi-structured data is incompatible with the flat structure of relational database tables, and so the growth of XML data requires new and complex query optimization techniques.
Creating XML files with a text editor would be a lot easier if you didn'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 completed you can just copy and paste to repeat the required elements. After doing this hundreds of times you'll be looking for a faster way to create XML files.
Some XML editors will automatically add the closing tag after you have finished typing the opening tag but, you still have to type the brackets around the opening tag. I kept thinking this process should be easier. So, I came up with a solution that allows you to create XML files without using HTML tags.
This console application will create an XML file based on user input. Just enter the file name, how many element fields you want, and the name of each field. Optionally, you can include a data type separated by a comma after the field name. You can just enter the field name because the data type is not required. The structure of the XML file that is created will be compatible with the .NET Dataset and can be easily added to a database.
In addition to creating the XML file, an XSL file and HTML file are also created. The HTML file uses client side JavaScript to transform the XML file using the XSL file. This provides an easy way to view the new XML file by displaying it in a table layout.
The download includes both the source code and the already compiled application. You can start using the executable right away or customize it to meet your needs. All you will need is the .NET Framework and a text editor, like Notepad, to build this application.
Improving ASP Performance with Data Caching
One of the nicest features of ASP.NET is the ability to cache page content. This can be used to substantially reduce load on a website's database - which is an obvious attraction if the site uses Microsoft's Access to store data rather than SQL Server. Unfortunately there is no built in caching system in classic ASP, but it is easy to build one by using the Application object to store data.
When to use ASP Caching. Caching is most useful for data that changes - but not too often. For example an e-commerce store could display a list of popular products, or an information site could display a list of press releases.
Don't forget 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。

在办公室自动化和电子图像年代中，办公文件以多种方式正被处理,传送和显示。文件处理的范围是巨大的；它包含页面布局规划，文件长度，校刊，单面或双面印刷，颜色，图像质量，终结和装订。如果用网络连接办公系统,那么另外有关网络协议的规格，文件形式，页面描述语言，压缩/解压，工作管理，错误操作 ,用户接口,和设备驱动，这些都必须被编址保存。数字彩色图像系统处理来自各种不同的来源电子数据；图像可能来自本地局域网,或者遥感设备,或者是不同的彩色工作站,亦或者是一个本地扫描仪。经过处理，一份文件通常被压缩，经由计算机网络传送到一些地方,继续检视，编辑,印刷。另外，现在工业越来越趋向于开放环境。这就意谓着那些来自各种设备（例如，扫描仪，计算机，工作站，调制解调器和打印机等）的文件汇集到一个系统之内。执行过程的落实应该以公共流通技术为基础，而非专有的标准。这将会为系统元件进入到市场保持公平，并且拓宽了使用者选择范围。促使不同的系统成份的沟通，在无论是不同的操作系统，文件格式，页描述语言还是数据内容，这将是一个巨大的任务。理想的说，交换不应该引起数据损失或变更。关注一份文件它所组成的不同类型图像，主要文本，点阵图像和矢量图形。这些全部有不同图像特性和表现，例如?ASCII( American Standard Code for Information Interchange 美国信息交换标准代码),矢量图形和光栅图像。每个类型的图像和其相关属性，比如字型，字体大小，照相铜版，灰度级，分辨率和颜色必须被分开处理。在如此的一个复杂的环境中,毫无疑问，当获得，传输，显示一个图像的时候,就会发生许多相容性的问题。
随着网络技术的飞速发展，存在了大量以电子文档形式的数据。为了数据整合和数据交换,越来越多已经存在的来源，例如，关系数据库，支援公共的XML输出，和逐渐增加的大量的公众和私人的数据，都以半构成的方式被描述。当我们整合来自不同的来源数据的时候,许多的争议都是需要被演说的。包括混杂和备份数据，多样的区分和合伙,以及变化。
数据的不统一性起因于不同的数据管理系统使用的储存数据方式，而且每个系统有它的自己数据结构和存取方法。关系数据库管理系统获益于全世界对于SQL（Structured Query Language ）的接受程度，例如得到文档响应的主要方法和电子邮件的存取，通常都要和本文搜寻引擎一起使用来改变接口和功能。因为这些系统并不是由于主观的相互操作性而被设计。
在数据整合中的另一种困难是数据备份-不同的系统以不同的方式展现相同的数据。举例来说，用户可能通过在一个数据库中的名字而被识别,但是用户帐户数据存储在另一个储器中,也同样可以通过电子邮件地址识别用户。通常，一个所需的数据起源于多样的取值点。当用户在与一家大型企业中的多样的部门,或者与其他的合伙人进行商业活动的时候，数据整合将更为复杂。与此类似，回答关于公司的供应链状态的问题，则需要从卖主和经销人信息来源。跨越防火墙做电子生意会引起安全和数据所有权问题争议。最后，数据整合必须处理不同的类型变化；在生意需求和策略中改变，在IT系统，合并,获得 ,和新的产品启动。这就要求一个数据综合解决的办法要足够灵活和适合。
之前所提到的能够解决数据整合问题的方法之一，就是提供一个XML网络服务，分类剖析不同的计算机操作平台，开发环境和相连网络，允许组织不用花费费用和时间在决定语言结构，框架，接口和其他延迟的消除问题的解决上。
XML提供给处理数据不一致结构的灵活性。因此XML在Web上的数据交换技术逐渐成为主要媒介，而且总体上综合信息，随之，大量的公共和私人的数据都在用XML语言描述。XML数据通常定义基于为树形或曲线图,自我描述反对例证模型(Boncz 和 Kersten,1999)。然而 ,半结构化的数据与相关的数据库表格的单调结构不能并存，因此XML数据的发展需要更新和更复杂质问优化技术。
用一个文本编辑器创建XML文件将会是比较容易的，你不用关心所有的那些未完整的HTML标签。首先你必须增加XML声明打开脚本，同时关闭 HTML标签。然后，你开始同时添加元素打开和关闭的标签。当然，一旦你的初始序列完成，你能够重复扶植和粘贴所必需的元素。在做这数百次之后，你将寻找一种更快的方法建立XML文件。一些XML编辑器将会在你输入开始标签之后自动地增加结束标签, 但是, 你仍然必须在开始标签旁输入括号。我一直在考虑这个过程应该可以更容易。因此,我提出允许你不使用 HTML 标签而产生XML文件的解决方法。
这操纵台应用将建立一个基于用户输入的XML文件。仅仅是输入文件名称，你想要多少个要素字段，以及每一个字段的名字。你也可以包含数据类型，并且在字段名用逗号分开。如果数据类型没有要求，你也可以仅输入字段名称。由此创建的XML文件的结构将与.NET相容并且很容易被增加到数据库。
除了建立XML文件之外，一个XSL文件和HTML文件也被同时创建。HTML文件使用客户端JavaScript通过XSL文件解释XML文件。这提供一种在表格里展示布局时察看新XML文件的方法。
下载包括源码和已经编辑的应用。你能够马上开始使用可执行文件或者定制它们以满足你的需要。你所需要的是. NET框架和一个文本编辑器，象记事本一样，去建造这种应用环境。
ASP.NET的最好的特征之一就是隐藏页内容的能力。这能用来实质上减少一个网站的数据库上的负荷-是什么吸引站点使用微软的Access去存储数据而不是SQL服务器。令人遗憾的是，隐藏功能并没有在优秀的ASP系统建造中，但是通过使用物体存储数据来建造隐藏功能是很容易的。
什么时候使用ASP隐藏。隐藏对于变更的数据非常有用，但不是经常使用。 例如一家电子商务商店能展示受欢迎的产品的目录，或者一个信息网站展示新闻发布的目录。

不要忘记，也有可能建立官能度到管理部分，以便更新数据库的内容，高速缓存将被冲洗。站点管理者不必等待的那路高速缓存调节在外为了新内容在站点上出现。要记得，储存在应用变量过程中的数据对于站点的全部用户来说都是可见的