<![CDATA[
<!-- For best results, you should include the HTML-coded -->
<!-- metadata that you find further down the page -->
<!-- (below the line) in the <HEAD></HEAD>-tag of your -->
<!-- page. This will simplify correct indexing by robots. -->
<!-- ---------------------------------------------------- -->
<META NAME="DC.Title" CONTENT="Exchange of mathematical information on the web: Present and Future">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#title">
<META NAME="DC.Creator" CONTENT="Athale Manasi">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#creator">
<META NAME="DC.Contributor" CONTENT="Athale Rahul">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#contributor">
<META NAME="DC.Subject" CONTENT="mathematics knowledge management">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject">
<META NAME="DC.Subject" CONTENT="knowledge transfer on the web">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject">
<META NAME="DC.Subject" SCHEME="CCS" CONTENT="H.3 INFORMATION STORAGE AND RETRIEVAL">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject">
<META NAME="DC.Subject" SCHEME="CCS" CONTENT="H.3.0 General">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#subject">
<META NAME="DC.Description" CONTENT="The advancement in the technology has given us the new and most powerful communication medium, Internet. It has opened up many new avenues and also has posed different problems. These can be categorized into two broad categories, namely problems regarding storage and problems regarding communication. This can be explained in scientific terms as computer-supported build-up of mathematical knowledge and computer-supported retrieval of mathematical knowledge. In this paper, we suggest that for storing data, we categorize the users according to their needs, or in other words, according to their usual usage of information. We explain our categorization based on the needs with specific examples and why we came up with these categories. To fulfill the needs of users from different categories, we either have to store the same information in many formats with minor changes, or add some extra information, using which we can use the same information for different users. We give an example to show our approach in this regard. ">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#description">
<META NAME="DC.Publisher" CONTENT="Research Institute for Symbolic Computation, Linz, Austria">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#publisher">
<META NAME="DC.Type" CONTENT="Text.Proceedings">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#type">
<META NAME="DC.Format" SCHEME="IMT" CONTENT="application/postscript">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#format">
<LINK REL=SCHEMA.imt HREF="http://sunsite.auc.dk/RFC/rfc/rfc2046.html">
<META NAME="DC.Format.X-Carrier" CONTENT="printed material">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#format">
<META NAME="DC.Identifier" SCHEME="URL" CONTENT="http://www.risc.uni-linz.ac.at/conferences/MKM2001/Proceedings">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#identifier">
<META NAME="DC.Language" SCHEME="ISO639-1" CONTENT="en">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#language">
<META NAME="DC.Date.X-MetadataLastModified" SCHEME="ISO8601" CONTENT="2001-11-02">
<LINK REL=SCHEMA.dc HREF="http://purl.org/metadata/dublin_core_elements#date">
]]>