Line 317: |
Line 317: |
| systems are all playing a part in the definition and implementation of | | systems are all playing a part in the definition and implementation of |
| this technology. In addition, input has been sought for and discussed | | this technology. In addition, input has been sought for and discussed |
− | with many other systems and software vendors, including Borland and IBM, | + | with many other systems and software vendors, including Borland and [[IBM]], |
| and we expect support from many of these other companies for the OpenDoc | | and we expect support from many of these other companies for the OpenDoc |
| architecture. You can expect to see more announcements in the future | | architecture. You can expect to see more announcements in the future |
Line 325: |
Line 325: |
| vendors as well as looking toward cooperation with recognized industry | | vendors as well as looking toward cooperation with recognized industry |
| associations, such as as the Object Management Group (OMG), Open Software | | associations, such as as the Object Management Group (OMG), Open Software |
− | Foundation (OSF), and X Consortium. Apple¹s stated intent is to make | + | Foundation (OSF), and X Consortium. Apple's stated intent is to make |
| OpenDoc technology not only cross-platform but also truly open‹with both | | OpenDoc technology not only cross-platform but also truly open‹with both |
| systems vendors and independent software vendors able to obtain the | | systems vendors and independent software vendors able to obtain the |
| source code easily. In contrast, the other major effort along these | | source code easily. In contrast, the other major effort along these |
| lines, Microsoft's OLE 2.0, is a proprietary approach. Currently, the OLE | | lines, Microsoft's OLE 2.0, is a proprietary approach. Currently, the OLE |
− | 2.0 source code is held by Microsoft, and provided only under Microsoft | + | 2.0 source code is held by [[Microsoft]], and provided only under Microsoft |
| license. However, OpenDoc will be interoperable with OLE 2.0, so | | license. However, OpenDoc will be interoperable with OLE 2.0, so |
| developers can take advantage of OpenDoc's broader feature set and | | developers can take advantage of OpenDoc's broader feature set and |
Line 341: |
Line 341: |
| at a higher level of functionality on Windows or Macintosh, and to | | at a higher level of functionality on Windows or Macintosh, and to |
| interoperate across multiple platforms and distributed systems as well. | | interoperate across multiple platforms and distributed systems as well. |
− | Apple, IBM, and Taligent plan to design complete interoperability between | + | Apple, [[IBM]], and [[Taligent]] plan to design complete interoperability between |
| OpenDoc and Taligent, similar to the interoperability between OpenDoc and | | OpenDoc and Taligent, similar to the interoperability between OpenDoc and |
| OLE 2.0. This is intended to enable developers and customers to migrate | | OLE 2.0. This is intended to enable developers and customers to migrate |
Line 379: |
Line 379: |
| services. Because OpenDoc is CORBA-compliant, OpenDoc documents and parts | | services. Because OpenDoc is CORBA-compliant, OpenDoc documents and parts |
| will be able to use CORBA-compliant services and interoperate with other | | will be able to use CORBA-compliant services and interoperate with other |
− | CORBA-compliant architectures. | + | CORBA-compliant architectures. |
| | | |
| =The Shape of the Future= | | =The Shape of the Future= |