TL;DR: In a multi-unit organization, each unit can learn from each other and benefit from new knowledge developed by other units as mentioned in this paper, and knowledge transfer among organizational units provides opportunities for mutual learning and interunit cooperation that stimulate the creation of new knowledge and contribute to organizational units' ability to innovate.
Abstract: Inside a multiunit organization, units can learn from each other and benefit from new knowledge developed by other units. Knowledge transfer among organizational units provides opportunities for mutual learning and interunit cooperation that stimulate the creation of new knowledge and, at the same time, contribute to organizational units' ability to innovate (e.g., Kogut & Zander, 1992; Tsai &
TL;DR: This document defines the string representation used in the Lightweight Directory Access Protocol (LDAP) to transfer distinguished names.
Abstract: The X.500 Directory uses distinguished names as the primary keys to
entries in the directory. Distinguished Names are encoded in ASN.1 in
the X.500 Directory protocols. In the Lightweight Directory Access
Protocol, a string representation of distinguished names is
transferred. This specification defines the string format for
representing names, which is designed to give a clean representation
of commonly used distinguished names, while being able to represent
any distinguished name.
TL;DR: This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory and is intended to be a complement to the DAP itself.
Abstract: The protocol described in this document is designed to provide access to the X.500 Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the X.500 Directory, and is intended to be a complement to the DAP itself.
TL;DR: In this article, a hierarchical/relational translation system is provided for enabling information from unrelated heterogeneous relational computing systems to be accessed, navigated, searched, browsed, and shared over a hierarchical computing system.
Abstract: A hierarchical/relational translation system is provided for enabling information from unrelated heterogeneous relational computing systems to be accessed, navigated, searched, browsed, and shared over a hierarchical computing system. In one embodiment, the hierarchical/relational translation system includes a virtual directory server for capturing information in the nature of relational database schema and metadata. The captured schema and metadata are then translated into virtual directories that are universally compatible with standard communication protocols used with hierarchical computing systems. A virtual directory of information organizes an index of data records and a standard addressing schema is provided to enable customizable access to relevant views of relational computing systems. Several embodiments for presenting the virtual directory information tree are included. In one embodiment, the virtual directory is displayed using browser format. In another embodiment, the virtual directory is presented in electronic mail format. Still, in another embodiment the virtual directory is presented over a wireless medium and through portable devices.
TL;DR: The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of theX.500 Directory Access Protocol (DAP).
Abstract: The protocol described in this document is designed to provide access to directories supporting the X.500 models, while not incurring the resource requirements of the X.500 Directory Access Protocol (DAP). This protocol is specifically targeted at management applications and browser applications that provide read/write interactive access to directories. When used with a directory supporting the X.500 protocols, it is intended to be a complement to the X.500 DAP.