]> 2008/06/10 OpenCyc Knowledge Base Copyright© 2001-2008 Cycorp, Inc., http://www.cyc.com/, Austin, TX, USA This file contains an OWL representation of information contained in the OpenCyc Knowledge Base. The content of this OWL file is licensed under the Creative Commons Attribution 3.0 license whose text can be found at http://creativecommons.org/licenses/by/3.0/legalcode. The content of this OWL file, including the OpenCyc content it represents, constitutes the "Work" referred to in the Creative Commons license. The terms of this license equally apply to, without limitation, renamings and other logically equivalent reformulations of the content of this OWL file (or portions thereof) in any natural or formal language, as well as to derivations of this content or inclusion of it in other ontologies. externalID A unique, language-neutral, variable-sized identifier for a concept that can be used to refer unambiguously to that concept across OWL exports or across Cyc inference engines. label A natural-language representation for a concept that is both human readable and readable by the Cyc inference engine. These terms are not guaranteed to refer to the same concept across time but are guaranteed to be consistent within a particular OWL export. Use 'cycAnnot:externalID' for unambiguously referring to a concept across OWL exports or across Cyc inference engines. MachineProtocol machine protocol A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA" class="cyc_term">Specification</a>. The collection of all protocols that specify how machines should behave in order to participate in some larger system or to be considered to be of a particular type. To be considered a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a>, this interaction of system with system must involve communication, as opposed to direct action as gears perform on each other in a gearbox. Examples: There are rules that specify how a device should behave electrically in order to be considered a node on a 10 base-T Ethernet network, and there are rules about what types of messages to send to interact with a SOAP-based service on a network. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkGsW5wpEbGdrcN5Y29ycA" class="cyc_term">ProtocolStackLayer</a> is the collection of all <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a>s which are classifed relative to their position in a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwOTivZwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocolStack</a>. An instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkGsW5wpEbGdrcN5Y29ycA" class="cyc_term">ProtocolStackLayer</a> is expected to provide certain services to other <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a>s which are instances of different <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvkGsW5wpEbGdrcN5Y29ycA" class="cyc_term">ProtocolStackLayer</a>s. protocol stack layer ProtocolStackLayer transmit protocol TransmitProtocol The collection of all transmit protocols. A type of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifcZwpEbGdrcN5Y29ycA" class="cyc_term">CommunicationProtocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. BusProtocol bus protocol The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>s used on a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_8EfHDEdaO6gABAkLVdg" class="cyc_term">CommunicationBus</a>. stream-based protocol The specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a> whose instances transmit information in a continuous stream. Disjoint with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxpAjIfHDEdaO6gABAkLVdg" class="cyc_term">PacketBasedProtocol</a>. StreamBasedProtocol A type of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifcZwpEbGdrcN5Y29ycA" class="cyc_term">CommunicationProtocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. ReceiveProtocol receive protocol HIPPI HIPPINetworkProtocol The collection of all instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> according to which communications between computers are conducted in <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rm02TzHS_EdaAAACgyZzFrg" class="cyc_term">Plaintext</a>, i.e., are not <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rK5oWSnS6EdaAAACgyZzFrg" class="cyc_term">Encrypted</a>. PlaintextProtocol plaintext protocol StructuredKnowledgeSourceProtocol The collection of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>s for interacting with <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rmUy0ojIYEdaAAACQJ5pZBw" class="cyc_term">StructuredKnowledgeSource</a>s. structured knowledge source protocol <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWa8TpwpEbGdrcN5Y29ycA" class="cyc_term">CommunicationsSecurityProtocol</a> is the collection of instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> that are protocols for secure transmission and reception of information. CommunicationsSecurityProtocol security protocol packet-based protocol The specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a> whose instances transmit information in packets. This means that the information transmitted via such a protocol is sent in discrete chunks, rather than as a continuous stream. Disjoint with #$ConnectionBasedProtocol. PacketBasedProtocol The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA" class="cyc_term">InternetStandard</a> that governs the distribution of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwRwJz5wpEbGdrcN5Y29ycA" class="cyc_term">Usenet</a> news postings on the internet. Network News Transfer Protocol NetworkNewsTransferProtocol Bootstrap protocol BootstrapProtocol A protocol used for booting diskless workstations. A popular packet-oriented protocol from Columbia University for transferring text files and binary files on both full-duplex and half-duplex 8 bit and 7-bit serial connections. KermitFileTransferProtocol Kermit File Transfer Protocol Cisco Discovery Protocol CiscoDiscoveryProtocol The Internet Group Management Protocol (IGMP) is used between IP hosts and their immediate neighbour multicast agents to support the allocation of temporary group addresses and the addition and deletion of members of a group. Like ICMP, IGMP is a integral part of IP. It is required to be implemented in full by all hosts conforming to level 2 of the IP multicasting specification. IGMP messages are encapsulated in IP datagrams, with an IP protocol number of 2. InternetGroupManagementProtocol IGMP NTP: an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA" class="cyc_term">InternetStandard</a>, a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>, and a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a>. NTP NetworkTimeProtocol DHCP protocol DHCPProtocol DHCP protocol: a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> and a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. gopher A once-popular distributed document retrieval system which started as a Campus Wide Information System at the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWaHMpwpEbGdrcN5Y29ycA" class="cyc_term">UnivOfMinnesota</a>. Gopher servers provide a menu of documents, which may be plain text files, sound or image files, submenus, or other Gopher object types. They may be stored on other hosts, and may provide the ability to search through certain files for a given string. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv5_2ppwpEbGdrcN5Y29ycA" class="cyc_term">Gopher_InternetProtocol</a> has been largely superceded by the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQvpJwpEbGdrcN5Y29ycA" class="cyc_term">WorldWideWeb_DynamicIndexedInfoSource</a>, which includes access to Gopher documents as one of its access schemes, but also includes html, which has the ability to combine images, sound, and text on a single page. Gopher-InternetProtocol file transfer protocol FileTransferProtocol A client-server communication protocol which allows a user on one computer to transfer files to and from another computer over a TCP/IP network. The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> implemented by instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwHepOZwpEbGdrcN5Y29ycA" class="cyc_term">SNMPServerProgram</a>. SimpleNetworkManagementProtocol SNMP jdbc JDBCDatabaseProtocol The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a> for communicating with database servers. The Trivial File Transfer protocol ("TFTP") is a simple protocol to transfer files. It is designed to be small and easy to implement, so its implementations lack most of the features of regular <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwVZKTZwpEbGdrcN5Y29ycA" class="cyc_term">FileTransferProtocol</a> implementations. It uses the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwUCL2pwpEbGdrcN5Y29ycA" class="cyc_term">UserDatagramProtocol</a> (UDP) and can only read or write files from remote servers -- it cannot list directories, and currently has no provisions for user authentication. It is often used by servers to boot diskless workstations, X-terminals, and routers. TFTP TrivialFileTransferProtocol Dynamic Data Exchange: a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> and a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. DynamicDataExchangeProtocol Dynamic Data Exchange Asynchronous Transfer Mode A data <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVifcZwpEbGdrcN5Y29ycA" class="cyc_term">CommunicationProtocol</a> that uses high-speed switching technology that can transmit packets requiring a high rate of data tranfer. Links using <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwIpNkJwpEbGdrcN5Y29ycA" class="cyc_term">AsynchronousTransferMode</a> technology can transmit data as well as multimedia communications. AsynchronousTransferMode HTTP HypertextTransferProtocol <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwJobjpwpEbGdrcN5Y29ycA" class="cyc_term">HypertextTransferProtocol</a> is the common protocol used by the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQvpJwpEbGdrcN5Y29ycA" class="cyc_term">WorldWideWeb_DynamicIndexedInfoSource</a> in communications between client and server via a browser. <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rv7GpT5wpEbGdrcN5Y29ycA" class="cyc_term">LocalAreaTransportProtocol</a> is a DEC-specific, non-routable network protocol. LocalAreaTransportProtocol LAT Lightweight Directory Access Protocol A protocol for updating and searching on-line directory services over <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA" class="cyc_term">TCP_IP</a>. LDAP defines a directory format that arranges entries containing email addresses, photographs, and other information about individuals (whether they are in stand-alone directory servers or in X.500 directories) in a hierarchical tree structure. These directories can be accessed over the Internet to retrieve information or edit information that the user has access to. Large organizations such as universities use LDAP for online 'phone books' containing publicly available information about students and staff. LightweightDirectoryAccessProtocol Address Resolution Protocol Address Resolution Protocol: a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA" class="cyc_term">NetworkProtocol</a> and a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. AddressResolutionProtocol X Display Manager Control Protocol XDisplayManagerControlProtocol AGPBusProtocol AGP TelnetProtocol The <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvxNZKpwpEbGdrcN5Y29ycA" class="cyc_term">TelnetProtocol</a> requires an application, also called telnet, that logs on to other computers over the internet. Both computers must support the telnet protocol in order for telnet to work. It is like two computers using modems to connect via phone lines with a phone number, but instead, the computers use telnet to connect via the internet with a telnet address. telnet protocol MachineProtocol machine protocol A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA" class="cyc_term">Specification</a>. The collection of all protocols that specify how machines should behave in order to participate in some larger system or to be considered to be of a particular type. To be considered a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a>, this interaction of system with system must involve communication, as opposed to direct action as gears perform on each other in a gearbox. Examples: There are rules that specify how a device should behave electrically in order to be considered a node on a 10 base-T Ethernet network, and there are rules about what types of messages to send to interact with a SOAP-based service on a network. protocol A spec of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjbTZwpEbGdrcN5Y29ycA" class="cyc_term">Instructions</a>. A <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> specifies how one or more agents should behave, in order to be considered to form part of, or to be participating in, some larger system. Examples: there are certain rules about how a surrender should be negotiated in war. There are rules about a way a person should behave at a rave, or in the presence of the Queen of England. There are rules about how one should behave in order to participate in a committee. There are also rules that specify how a device should behave electrically in order to be considered a node on a 10 base-T Ethernet network, and there are rules about what types of messages to send to interact with a SOAP-based service on a network. Protocol is currently partitioned into <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAvHDEdaO6gABAkLVdg" class="cyc_term">HumanProtocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a>. Specializations of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAvHDEdaO6gABAkLVdg" class="cyc_term">HumanProtocol</a> include #$DiplomaticProtocol and #$SocialProtocol. Instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg" class="cyc_term">MachineProtocol</a> include #$EthernetProtocol, #$IDEProtocol, #$SOAPProtocol. Since the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> subcollections are called XProtocol (for some X), individual <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a>s should be called Y-TheProtocol. Protocol MachineProtocol machine protocol A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA" class="cyc_term">Specification</a>. The collection of all protocols that specify how machines should behave in order to participate in some larger system or to be considered to be of a particular type. To be considered a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a>, this interaction of system with system must involve communication, as opposed to direct action as gears perform on each other in a gearbox. Examples: There are rules that specify how a device should behave electrically in order to be considered a node on a 10 base-T Ethernet network, and there are rules about what types of messages to send to interact with a SOAP-based service on a network. ObjectType The collection of all collections that are "object-like" in at least one respect. A collection <code>COL</code> is object-like just in case there is some sense of 'part' according to which any (or nearly any) given proper part of an instance of <code>COL</code> is not itself an instance of <code>COL</code>; when this happens <code>COL</code> is said to be object-like with respect to that sense of 'part'. More precisely, for a collection <code>COL</code> to be an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a> it is sufficient that there be some specialization <code>PARTPRED</code> of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw" class="cyc_term">properParts</a> such that, for any <code>OBJ1</code> and <code>OBJ2</code>, if <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ1 COL)</code> and <code>(PARTPRED OBJ1 OBJ2)</code> both hold, then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ2 COL)</code> does not hold. (Also sufficient for <code>COL</code>'s being an object-type is that there be some specialization <code>INVPARTPRED</code> of the inverse of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw" class="cyc_term">properParts</a> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWHsNJwpEbGdrcN5Y29ycA" class="cyc_term">genlInverse</a>) such that <code>(INVPARTPRED OBJ2 OBJ1)</code>, with everything else remaining the same as above.) Note that neither of the above sufficient conditions for <code>COL</code>'s being an object-type is strictly necessary: some exceptions are allowed. Thus as long as either one of the above conditionals holds in nearly all cases, <code>COL</code> should be considered an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. Here are two examples. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a>. Take an instance of that, say my car. Now consider one of the proper <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj5FpwpEbGdrcN5Y29ycA" class="cyc_term">physicalParts</a> of my car, say the steering wheel. The steering wheel is not an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a>. And the same would be true for any proper physical part of any car. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA" class="cyc_term">Automobile</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a>. No proper <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> of a year is itself a year. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA" class="cyc_term">CalendarYear</a> is an <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA" class="cyc_term">ObjectType</a>. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> for the contrasting (though not disjoint) notion of being stuff-like. type of object A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA" class="cyc_term">Specification</a>. Each instance of this collection is not a computer program itself (i.e. lines of code), but an abstract characterization of how a program should behave. For instance, a sorting program can be specified by requiring that the program's output be a list of the same elements as the input such that no element follows an element that is greater than it. A notable example of a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjDLZwpEbGdrcN5Y29ycA" class="cyc_term">ProgramSpecification</a> is UNIX - which is not (contrary to popular belief) an operating system per se, but a specification to which many different operating systems (instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvwJcVZwpEbGdrcN5Y29ycA" class="cyc_term">UnixOS</a>) conform. Note that instances of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjDLZwpEbGdrcN5Y29ycA" class="cyc_term">ProgramSpecification</a> do not necessarily specify single, discrete programs -- thus many of the internet's "RFC" protocol-establishing documents (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rwL2Ud5wpEbGdrcN5Y29ycA" class="cyc_term">RequestForComments_Internet</a>) fall into this collection. ProgramSpecification program specification MachineProtocol machine protocol A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a> and <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA" class="cyc_term">Specification</a>. The collection of all protocols that specify how machines should behave in order to participate in some larger system or to be considered to be of a particular type. To be considered a <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAPHDEdaO6gABAkLVdg" class="cyc_term">Protocol</a>, this interaction of system with system must involve communication, as opposed to direct action as gears perform on each other in a gearbox. Examples: There are rules that specify how a device should behave electrically in order to be considered a node on a 10 base-T Ethernet network, and there are rules about what types of messages to send to interact with a SOAP-based service on a network. type of temporally stuff-like thing A specialization of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA" class="cyc_term">StuffType</a> (q.v.) whose instances are all and only those collections that are temporally stuff-like. A collection <code>COL</code> is temporally stuff-like just in case every purely temporal part (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a>) of an instance of <code>COL</code> is itself an instance of <code>COL</code>, unless it is a temporal part of a temporal granule of <code>COL</code> (see <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaJJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfTemporalStuff</a>). More precisely, for a collection <code>COL</code> to be an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a> it is both a necessary and sufficient condition that for any <code>OBJ1</code> and <code>OBJ2</code> (with <code>OBJ2</code> at or above <code>COL</code>'s temporal granularity level), if <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ1 COL)</code> and <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA" class="cyc_term">timeSlices</a> OBJ1 OBJ2)</code>, then <code>(<a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA" class="cyc_term">isa</a> OBJ2 COL)</code>. Consider <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>. Take an arbitrary instance <code>WALK</code> of this collection (say Miss America 2000's victory walk down the runway and back); and then take an arbitrary time-slice <code>SUBWALK</code> of <code>WALK</code> that subsumes at least one instance of (the <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjaJJwpEbGdrcN5Y29ycA" class="cyc_term">granuleOfTemporalStuff</a> for <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>) <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViYBpwpEbGdrcN5Y29ycA" class="cyc_term">TakingAStep</a> (say her trip back from the end of the runway). <code>SUBWALK</code> is itself an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a>. So <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVi0gpwpEbGdrcN5Y29ycA" class="cyc_term">WalkingOnTwoLegs</a> is an instance of <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvVitN5wpEbGdrcN5Y29ycA" class="cyc_term">TemporalStuffType</a>. See <a href="http://sw.opencyc.org/2008/06/10/concept/Mx4rvViq35wpEbGdrcN5Y29ycA" class="cyc_term">TemporalObjectType</a> for the disjoint notion of being temporally object-like. TemporalStuffType