scispace - formally typeset
Search or ask a question
Journal ArticleDOI

Internet messaging frameworks

01 Jan 1998-Ibm Systems Journal (IBM)-Vol. 37, Iss: 1, pp 4-18
TL;DR: The current state of the most important Internet standards related to e-mail and the general state of proprietary e- Mail systems are summarized and a set of technologies developed to solve the complex problem of evolving from proprietary to Internet-standards-based e- mail systems are introduced.
Abstract: Electronic mail (e-mail) has become an important tool for companies to use to conduct their businesses. With the introduction of the World Wide Web, awareness of the existence of the Internet has exponentially increased over the last two years, and people are starting to realize that there is more to the Internet than just the Web. Companies are expanding their use of e-mail from internal to external. But the large set of proprietary, noninteroperable e-mail systems make this more of a trip through a jungle than a drive along the information highway. Most approaches to overcome the connectivity problems use gateways to convert between the proprietary format and the Internet standards. These conversions are lossy at best; hence, most proprietary system vendors are revamping their systems to base them on Internet standards. This paper summarizes the current state of the most important Internet standards related to e-mail and the general state of proprietary e-mail systems. It then introduces a set of technologies we developed to solve the complex problem of evolving from proprietary to Internet-standards-based e-mail systems. We have structured these technologies into Internet Messaging Frameworks.
Citations
More filters
Book ChapterDOI
01 Jan 2004
TL;DR: This chapter examines several perspectives on answering the question “What is knowledge?” including the usable representations view, the statesView, the production view, and the knowledge-versus-information view, concluding that technology is a major enabler of knowledge-based organizations.
Abstract: This chapter examines several perspectives on answering the question “What is knowledge?” including the usable representations view, the states view, the production view, and the knowledge-versus-information view. The relationship between knowledge and technology is considered, concluding that technology is a major enabler of knowledge-based organizations. Regardless of the view of knowledge that one adopts and the degree of technology adoption, it is valuable to be aware of various attribute dimensions that qualify the nature of knowledge.

90 citations

Journal ArticleDOI
TL;DR: Evidence that the expression of communication values precedes effective task communication and team performance in swift starting action teams is presented.

39 citations

Book ChapterDOI
01 Jan 2002
TL;DR: JSP arose from efforts by a small group of people in a data processing consultancy company to improve their programming practices, and to make their programs more reliable and easier to understand and to modify.
Abstract: Jackson Structured Programming (JSP) is a method of program design. Its origins lie in the data processing systems that grew up in the 1960s, when reliable, relatively cheap and adequately powerful computers first became generally available. The fundamental abstraction in JSP is the sequential data stream. Originally, this abstraction was inspired and motivated by the sequential tape files that characterised data processing in the 1960s, but it quickly became clear that it had a much wider applicability. Today the JSP design method is valuable for applications including embedded software, processing streams of EDI messages, handling network protocols and many others.JSP arose from efforts by a small group of people in a data processing consultancy company to improve their programming practices, and to make their programs more reliable and easier to understand and to modify. In 1971 it became the core product of a very small new company, Michael Jackson Systems Limited, which offered development services, training courses, consultancy, and - from 1975 - software to support JSP design of COBOL programs. The name JSP was coined by the company's Swedish licensee in 1974. In the commercial world, IBM had appropriated the name 'Structured Programming' in the early 1970s, and Yourdon Inc. started offering courses in 'Structured Design' around 1974. A distinctive name was a commercial necessity. It was also technically appropriate to choose a distinctive and proprietary name: the JSP method was very different from its competitors.

6 citations

Proceedings ArticleDOI
10 Oct 2001
TL;DR: This work proposes partitioning educational software along lines of expertise: open source authoring and presentation tools, open protocols for instructional design, and separate content created using the most appropriate application programs.
Abstract: Using computers to deliver instructional material should be an excellent match of technology to education. Countless products meant to enhance or replace the classroom experience are currently available, yet few are utilized in spite of the national drive to increase the use of educational technology in our schools. Factors behind this under-utilization are complex but include expense, lack of flexibility, the proprietary nature of the products, and lack of teacher training, support, and time. Any computer-based instructional tool should incorporate the following characteristics in order to maximize utility and flexibility while minimizing cost and time: (1) be cross-platform, (2) separate content from delivery, (3) provide creation, editing, and delivery capabilities, and (4) use open standards. Our work proposes partitioning educational software along lines of expertise: open source authoring and presentation tools, open protocols for instructional design, and separate content created using the most appropriate application programs. We show the feasibility of meeting all the requirements with this approach using XML and Java.

3 citations


Cites background from "Internet messaging frameworks"

  • ...In general, open systems provide less functionality and offer fewer administrative-type tools (especially in their early stages of development) than proprietary systems but usually are less expensive and require less server and system administration support [3]....

    [...]