Download (direct link):
2. Develop a plan with a workflow change strategy. In accomplishing the preceding goals, you will need to look at the current workflow process and be able to communicate (and document) how it must be changed. You may want to invest in workflow products that incorporate these technologies into your production process. Once you've thought about these things, it is time for the next step.
3. Set appropriate staff in place. At this point, you may want to consider creating an ontology department, a data production department, and a Web service deployment department that work together in order to accomplish some of your goals.
4. Set a schedule. At this point, you are ready to set a schedule to implement these changes. If some of the work can be done behind the scenes without impacting the employees, this should be done first (such as creating Web service interfaces to existing applications). Make certain that you do this work (ontology planning, Web service, production planning) with your staff (last bullet) before change impacts your regular employees. Once your employees' processes will have to change, be ready to unveil
a change in their workflow process. Incorporate this into the schedule.
Now, it's time to implement your schedule. At this point, you may want to communicate your plans to the company, starting with your reasons behind doing this and your high-level goals. Explain to them that specialized staff is working behind the scenes in order to accomplish these goals and make a smooth work transition. When the time is ready, schedule training to help your regular employees adapt to the new process.
General George S. Patton once said, "Accept the challenges so that you can feel the exhilaration of victory." The road to change may be rocky, and you will certainly be challenged along the way. With an intelligent plan and an incremental process, it is extremely doable, and it will be worth it when you get there.
This chapter presented a vision of where the typical organization is—and where we need to be to become a knowledge-centric organization in leveraging the technologies of the Semantic Web. In doing so, we have defined a knowledge-centric process and a how-to roadmap for crafting your company's roadmap to the Semantic Web.
Ahmed, K., D. Ayers, M. Birbeck, J. Cousins, D. Dodds, J. Lubell, M. Nic, D. Rivers-Moore, A. Watt, R. Worden, and A. Wrightson. 2001. XML Meta Data. Birmingham, UK: Wrox Press, Ltd.
Allegro Common Lisp. http://franz.com/. . .
Alter, J. 2002. "Actually, the Database Is God." Newsweek. (November 4, 2002). Available at http://stacks.msnbc.com/news/826637.asp.
Baader, F., and B. Hollunder. 1991. "KRIS: Knowledge Representation and Inference System." In Special Issue on Implemented Knowledge Representation and Reasoning Systems, SIGART Bulletin 2, no. 3 (June 1991): 108-113.
Bechhofer, S., J. Broekstra, S. Decker, M. Erdmann, D. Fensel, C. Goble,
F. van Harmelen, I. Horrocks, M. Klein, D. McGuinness, E. Motta, P. Patel-Schneider, S. Staab, and R. Studer. 2000. "An Informal Description of Standard OIL and Instance OIL." White paper. (November 28, 2000.) Available at http://www.ontoknowledge.org/oil/downl/oil-whitepaper.pdf.
Beckett, D., ed. 2001. "RDF/XML Syntax Specification (Revised)." W3C Working Draft. (December 18, 2001). Available at http://www.w3.org/ TR/2001/WD-rdf-syntax-grammar-20011218/.
Berners-Lee, T. 2002. Weaving the Web. San Francisco: Harper San Francisco.
Berners-Lee, T. "What the Semantic Web can Represent." Available at http://www.w3.org/DesignIssues/RDFnot.html.
Berners-Lee, T., J. Hendler, and O. Lassila. 2001. "The Semantic Web." The Scientific American. (May 2001). Available at http://www.scientificamerican. com/2001/0501issue/0501berners-lee.html.
Biezunski, M., S. Newcomb, and M. Bryan, eds. 2002. "Guide to the Topic Map Standards." Project ISO 13250, ISO/IEC JTC 1/SC34 Information Technology—Document Description and Processing Languages. (June 23, 2002). Available at http://www.y12.doe.gov/sgml/sc34/document/ 0323.htm.
Biezunski, M. 2003. "Introduction to the Topic Maps Paradigm." Chapter 2 in XML Topic Maps: Creating and Using Topic Maps for the Web, edited by Jack Park and Sam Hunting. Reading, MA.: Addison-Wesley, 17-33.
Brachman, R. J. 1978. "A Structural Paradigm for Representing Knowledge." Bolt, Baranek, and Newman. BBN Report 3605. Cambridge, MA. Revision of Brachman's Ph.D. thesis. Harvard University. 1977.
Brachman, R. J., and H. Levesque, eds. 1985. Readings in Knowledge Representation. Los Altos, CA: Morgan Kaufmann.
Brachman, R. J., and J. G. Schmolze. 1985. "An Overview of the KL-ONE Knowledge Representation System." Cognitive Science 9, no. 2: 171-216.
Brickley, D., and R. V. Guha, eds. 2002. "RDF Vocabulary Description Language 1.0: RDF Schema." W3C Working Draft. (April 30, 2002). Available at http://www.w3.org/TR/rdf-schema/.
BusinessWeek. 2002. "The Web Weaver Looks Forward." Interview with Tim Berners-Lee. (March 27, 2002). Available at http://www.businessweek .com/bwdaily/dnflash/mar2002/nf20020327_4579.htm.