<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href="http://sw.opencyc.org/xsl/OpenCycOWLCollectionDisplayVersioned.xsl"?>

<!DOCTYPE rdf:RDF [
     <!ENTITY ocyc "http://sw.opencyc.org/concept/" >
     <!ENTITY cyc  "http://sw.cyc.com/concept/" >
     <!ENTITY rdf  "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
     <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
     <!ENTITY xsd  "http://www.w3.org/2001/XMLSchema#" >
     <!ENTITY owl  "http://www.w3.org/2002/07/owl#" >
   ]>

<rdf:RDF xml:base="http://sw.opencyc.org/2008/06/10/concept/"
         xmlns="http://sw.opencyc.org/2008/06/10/concept/"
         xmlns:cycAnnot="http://sw.cyc.com/CycAnnotations_v1#"
         xmlns:rdf="&rdf;"
         xmlns:rdfs="&rdfs;"
         xmlns:owl="&owl;"
         xmlns:xsd="&xsd;">

  <owl:Ontology rdf:about="http://sw.opencyc.org/2008/06/10/concept/">
    <owl:versionInfo>2008/06/10</owl:versionInfo>
    <rdfs:comment xml:lang="en">

      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.

    </rdfs:comment>
  </owl:Ontology>

  <owl:AnnotationProperty rdf:about="http://sw.cyc.com/CycAnnotations_v1#externalID">
    <rdfs:label xml:lang="en">externalID</rdfs:label>
    <rdfs:comment xml:lang="en">
      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.
    </rdfs:comment>
    <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#FunctionalProperty"/>
  </owl:AnnotationProperty>

  <owl:AnnotationProperty rdf:about="http://sw.cyc.com/CycAnnotations_v1#label">
    <rdfs:label xml:lang="en">label</rdfs:label>
    <rdfs:comment xml:lang="en">
      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.
    </rdfs:comment>
  </owl:AnnotationProperty>

  <owl:Class rdf:about="Mx4rvV_d4ZwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">InternetStandard</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard is a kind of product specification, applicable to &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtUyJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkingProgram&lt;/a&gt;s, concerning how the product behaves in the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt; environment.</rdfs:comment>
    <rdfs:label xml:lang="en">Internet standard</rdfs:label>
    <rdfs:subClassOf rdf:resource="Mx4rvVkF3ZwpEbGdrcN5Y29ycA"/>
    <rdf:type rdf:resource="Mx4rvVirnZwpEbGdrcN5Y29ycA"/>
    <owl:sameAs rdf:resource="&cyc;Mx4rvV_d4ZwpEbGdrcN5Y29ycA"/>
    <owl:sameAs rdf:resource="http://umbel.org/umbel/sc/InternetStandard"/>
    <owl:sameAs rdf:resource="http://dbpedia.org/resource/Internet_standard"/>
    <owl:sameAs rdf:resource="&ocyc;Mx4rvV_d4ZwpEbGdrcN5Y29ycA"/>
    <wikipediaArticleURL>http://en.wikipedia.org/wiki/Internet_standard</wikipediaArticleURL>
    <Mx4rwLSVCpwpEbGdrcN5Y29ycA xml:lang="en">Internet standards</Mx4rwLSVCpwpEbGdrcN5Y29ycA>
  </owl:Class>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvdGoXZwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">NIPRNetProtocol</cycAnnot:label>
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvdGoXZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NIPRNetProtocol&lt;/a&gt; is the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvhfdXpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkLayerProtocol&lt;/a&gt; which ensures that packets which adhere to it are routed only on machines on the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvril6pwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NIPRNet_PathSystem&lt;/a&gt;.</rdfs:comment>
    <rdfs:label xml:lang="en">NIPR Net Protocol</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwVVQ5JwpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">The &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetStandard&lt;/a&gt; that governs the distribution of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwRwJz5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Usenet&lt;/a&gt; news postings on the internet.</rdfs:comment>
    <rdfs:label xml:lang="en">Network News Transfer Protocol</rdfs:label>
    <cycAnnot:label xml:lang="en">NetworkNewsTransferProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rkLoHtuhKQdaM7I7JXRW7hQ">
    <rdfs:label xml:lang="en">IEEE 802.11 Wireless LAN Protocol</rdfs:label>
    <cycAnnot:label xml:lang="en">802-11WirelessLANProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvWEXx5wpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">SecureSocketsLayer</cycAnnot:label>
    <rdfs:label xml:lang="en">the Secure Sockets Layer</rdfs:label>
    <rdfs:comment xml:lang="en">The Secure Sockets Layer: a &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWa8TpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;CommunicationsSecurityProtocol&lt;/a&gt; and an &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetStandard&lt;/a&gt;.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwRTgSZwpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">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.</rdfs:comment>
    <cycAnnot:label xml:lang="en">KermitFileTransferProtocol</cycAnnot:label>
    <rdfs:label xml:lang="en">Kermit File Transfer Protocol</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvWLk_JwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">TCP-IP</cycAnnot:label>
    <rdfs:label xml:lang="en">TCP/IP</rdfs:label>
    <rdfs:comment xml:lang="en">TCP/IP: a group of network protocols and an &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetStandard&lt;/a&gt;.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvvn3fJwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">InternetProtocol</cycAnnot:label>
    <rdfs:label xml:lang="en">IP</rdfs:label>
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvvn3fJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetProtocol&lt;/a&gt; is the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvhfdXpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkLayerProtocol&lt;/a&gt; which is commonly  used in &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TCP_IP&lt;/a&gt;.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rHWu2ckjkEdaKIQACs0uFOQ">
    <rdfs:comment xml:lang="en">NTP: an &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvV_d4ZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetStandard&lt;/a&gt;, a &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rxo_VAfHDEdaO6gABAkLVdg&quot; class=&quot;cyc_term&quot;&gt;MachineProtocol&lt;/a&gt;, and a &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvzDExpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkProtocol&lt;/a&gt;.</rdfs:comment>
    <rdfs:label xml:lang="en">NTP</rdfs:label>
    <cycAnnot:label xml:lang="en">NetworkTimeProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rv5_2ppwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">gopher</rdfs:label>
    <rdfs:comment xml:lang="en">A once-popular distributed document retrieval system which started as a Campus Wide Information System at the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWaHMpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;UnivOfMinnesota&lt;/a&gt;. 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. &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rv5_2ppwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Gopher_InternetProtocol&lt;/a&gt; has been largely superceded by the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQvpJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;WorldWideWeb_DynamicIndexedInfoSource&lt;/a&gt;, 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.</rdfs:comment>
    <cycAnnot:label xml:lang="en">Gopher-InternetProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwVZKTZwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">file transfer protocol</rdfs:label>
    <cycAnnot:label xml:lang="en">FileTransferProtocol</cycAnnot:label>
    <rdfs:comment xml:lang="en">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.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwUCL2pwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">UDP</rdfs:label>
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwUCL2pwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;UserDatagramProtocol&lt;/a&gt; is a &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwFMKvpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TransportLayerProtocol&lt;/a&gt;. 
It is commonly used in &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TCP_IP&lt;/a&gt; and therefore
in network communications on the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt;.</rdfs:comment>
    <cycAnnot:label xml:lang="en">UserDatagramProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rv_UVS5wpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">Common Gateway Interface</rdfs:label>
    <cycAnnot:label xml:lang="en">CommonGatewayInterface</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard specifying how to pass arguments from a form on a website, etc., to an external program or script (often written in Perl and residing in a &apos;cgi-bin&apos; directory) running on the web server. It also defines some environmental variables and allows the browser to be sent a customized webpage or be redirected to a url.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rm-Pd0MtCEdaAAAACs6hPlg">
    <cycAnnot:label xml:lang="en">InternetProtocol-v6</cycAnnot:label>
    <rdfs:comment xml:lang="en">The newest version of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvvn3fJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetProtocol&lt;/a&gt;, the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvhfdXpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkLayerProtocol&lt;/a&gt; which is commonly used in &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TCP_IP&lt;/a&gt;.</rdfs:comment>
    <rdfs:label xml:lang="en">IPv6</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rv4547ZwpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">The Trivial File Transfer 
protocol (&amp;quot;TFTP&amp;quot;) 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 &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwVZKTZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;FileTransferProtocol&lt;/a&gt; implementations. It uses the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwUCL2pwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;UserDatagramProtocol&lt;/a&gt; (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.</rdfs:comment>
    <rdfs:label xml:lang="en">TFTP</rdfs:label>
    <cycAnnot:label xml:lang="en">TrivialFileTransferProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwJobjpwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">HTTP</rdfs:label>
    <cycAnnot:label xml:lang="en">HypertextTransferProtocol</cycAnnot:label>
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwJobjpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;HypertextTransferProtocol&lt;/a&gt; is the common protocol used by the  &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWQvpJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;WorldWideWeb_DynamicIndexedInfoSource&lt;/a&gt; in communications between client and server via a browser.</rdfs:comment>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvxy0PZwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">Lightweight Directory Access Protocol</rdfs:label>
    <rdfs:comment xml:lang="en">A protocol for updating and searching on-line directory services over &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TCP_IP&lt;/a&gt;. 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 &apos;phone books&apos; containing publicly available information about students and staff.</rdfs:comment>
    <cycAnnot:label xml:lang="en">LightweightDirectoryAccessProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rwU3mZJwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">SIPRNetProtocol</cycAnnot:label>
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwU3mZJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;SIPRNetProtocol&lt;/a&gt; is the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvhfdXpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkLayerProtocol&lt;/a&gt; which ensures that packets which adhere to it are routed only on machines on the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvp9VppwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;SIPRNet_PathSystem&lt;/a&gt;.</rdfs:comment>
    <rdfs:label xml:lang="en">SIPR Net Protocol</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvq6iipwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">IPX-SPX</cycAnnot:label>
    <rdfs:label xml:lang="en">IPX/SPX</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rvxNZKpwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">TelnetProtocol</cycAnnot:label>
    <rdfs:comment xml:lang="en">The &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvxNZKpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TelnetProtocol&lt;/a&gt; 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.</rdfs:comment>
    <rdfs:label xml:lang="en">telnet protocol</rdfs:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rv6bbn5wpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rv6bbn5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TransmissionControlProtocol&lt;/a&gt; is a &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwFMKvpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TransportLayerProtocol&lt;/a&gt;.  It is commonly used in &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWLk_JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;TCP_IP&lt;/a&gt; and therefore in network communications on the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt;.</rdfs:comment>
    <rdfs:label xml:lang="en">TCP</rdfs:label>
    <cycAnnot:label xml:lang="en">TransmissionControlProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <Mx4rvV_d4ZwpEbGdrcN5Y29ycA rdf:about="Mx4rviWwoZwpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">The Internet Control Message Protocol, which is an extension of the original &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvvn3fJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;InternetProtocol&lt;/a&gt; that provides  error and congestion control.</rdfs:comment>
    <rdfs:label xml:lang="en">ICMP</rdfs:label>
    <cycAnnot:label xml:lang="en">InternetControlMessageProtocol</cycAnnot:label>
  </Mx4rvV_d4ZwpEbGdrcN5Y29ycA>

  <owl:Class rdf:about="&ocyc;Mx4rvV_d4ZwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">InternetStandard</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard is a kind of product specification, applicable to &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtUyJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkingProgram&lt;/a&gt;s, concerning how the product behaves in the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt; environment.</rdfs:comment>
    <rdfs:label xml:lang="en">Internet standard</rdfs:label>
  </owl:Class>

  <owl:Class rdf:about="Mx4rvVkF3ZwpEbGdrcN5Y29ycA">
    <rdfs:comment xml:lang="en">A specialization of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVib1JwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Specification&lt;/a&gt;.  Each instance of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVkF3ZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ProductStandard&lt;/a&gt; is a precise description applied to the instances of a particular instance of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjKkZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ProductType&lt;/a&gt;.  Manufacturers of that product type agree explicitly or in practice, or they may obey a government requirement, to make product designs following the specifications stated in the standard, so that products within the type will all have certain features in common.  For example, telephones and television sets fulfil certain product standards.  The resultant interchangeability allows compatibility with other devices and products, with public utilities, commercial trading expectations, and government purchasing requirements.</rdfs:comment>
    <cycAnnot:label xml:lang="en">ProductStandard</cycAnnot:label>
    <rdfs:label xml:lang="en">product standard</rdfs:label>
  </owl:Class>

  <owl:ObjectProperty rdf:about="Mx4rwLSVCpwpEbGdrcN5Y29ycA">
    <rdfs:label xml:lang="en">Pretty String</rdfs:label>
    <rdfs:comment xml:lang="en">(&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;prettyString&lt;/a&gt; TERM STRING) means that STRING is the English word or expression (sequence of words) commonly used to refer to TERM.  The predicate &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwLSVCpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;prettyString&lt;/a&gt; is used by the code which generates CycL to English paraphrases, but its applicability is not restricted to this use.</rdfs:comment>
    <cycAnnot:label xml:lang="en">prettyString</cycAnnot:label>
  </owl:ObjectProperty>

  <owl:Thing rdf:about="http://dbpedia.org/resource/Internet_standard">
    <cycAnnot:label xml:lang="en">InternetStandard</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard is a kind of product specification, applicable to &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtUyJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkingProgram&lt;/a&gt;s, concerning how the product behaves in the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt; environment.</rdfs:comment>
    <rdfs:label xml:lang="en">Internet standard</rdfs:label>
  </owl:Thing>

  <owl:DataProperty rdf:about="wikipediaArticleURL">
  </owl:DataProperty>

  <owl:Class rdf:about="Mx4rvVirnZwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">ObjectType</cycAnnot:label>
    <rdfs:comment xml:lang="en">The collection of all collections that are &amp;quot;object-like&amp;quot; in at least one respect. A collection &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt; is object-like just in case there is some sense of &apos;part&apos; according to which any (or nearly any) given proper part of an instance of &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt; is &lt;i&gt;not&lt;/i&gt; itself an instance of &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt;; when this happens &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt; is said to be object-like with respect to that sense of &apos;part&apos;.
&lt;p/&gt;
More precisely, for a collection &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt; to be an instance of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ObjectType&lt;/a&gt; it is sufficient that there be some specialization &lt;code&gt;&lt;b&gt;PARTPRED&lt;/b&gt;&lt;/code&gt; of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw&quot; class=&quot;cyc_term&quot;&gt;properParts&lt;/a&gt; such that, for any &lt;code&gt;&lt;b&gt;OBJ1&lt;/b&gt;&lt;/code&gt; and &lt;code&gt;&lt;b&gt;OBJ2&lt;/b&gt;&lt;/code&gt;, if &lt;code&gt;(&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;isa&lt;/a&gt; &lt;b&gt;OBJ1&lt;/b&gt; &lt;b&gt;COL&lt;/b&gt;)&lt;/code&gt; and &lt;code&gt;(&lt;b&gt;PARTPRED&lt;/b&gt; &lt;b&gt;OBJ1&lt;/b&gt; &lt;b&gt;OBJ2&lt;/b&gt;)&lt;/code&gt; both hold, then &lt;code&gt;(&lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvViBBJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;isa&lt;/a&gt; &lt;b&gt;OBJ2&lt;/b&gt; &lt;b&gt;COL&lt;/b&gt;)&lt;/code&gt; does &lt;i&gt;not&lt;/i&gt; hold.  (Also sufficient for &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt;&apos;s being an object-type is that there be some specialization &lt;code&gt;&lt;b&gt;INVPARTPRED&lt;/b&gt;&lt;/code&gt; of the &lt;i&gt;inverse&lt;/i&gt; of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rwgfukKs8QdePzLB9nLNpTw&quot; class=&quot;cyc_term&quot;&gt;properParts&lt;/a&gt; (see &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWHsNJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;genlInverse&lt;/a&gt;) such that &lt;code&gt;(&lt;b&gt;INVPARTPRED&lt;/b&gt; &lt;b&gt;OBJ2&lt;/b&gt; &lt;b&gt;OBJ1&lt;/b&gt;)&lt;/code&gt;, with everything else remaining the same as above.)  Note that neither of the above sufficient conditions for &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt;&apos;s being an object-type is strictly necessary: some exceptions are allowed.  Thus as long as either one of the above conditionals holds in &lt;i&gt;nearly&lt;/i&gt; all cases, &lt;code&gt;&lt;b&gt;COL&lt;/b&gt;&lt;/code&gt; should be considered an instance of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ObjectType&lt;/a&gt;.
&lt;p/&gt;
Here are two examples.  Consider &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Automobile&lt;/a&gt;.  Take an instance of that, say my car.  Now consider one of the proper &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVj5FpwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;physicalParts&lt;/a&gt; of my car, say the steering wheel.  The steering wheel is &lt;i&gt;not&lt;/i&gt; an instance of &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Automobile&lt;/a&gt;.  And the same would be true for any proper physical part of any car.  So &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvViVwZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Automobile&lt;/a&gt; is an &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ObjectType&lt;/a&gt;.  Consider &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;CalendarYear&lt;/a&gt;. No proper &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvWn4OZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;timeSlices&lt;/a&gt; of a year is itself a year.  So &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVjyV5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;CalendarYear&lt;/a&gt; is an &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVirnZwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;ObjectType&lt;/a&gt;.  
&lt;p/&gt;
See &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVir35wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;StuffType&lt;/a&gt; for the contrasting (though not disjoint) notion of being stuff-like.</rdfs:comment>
    <rdfs:label xml:lang="en">type of object</rdfs:label>
  </owl:Class>

  <owl:Class rdf:about="&cyc;Mx4rvV_d4ZwpEbGdrcN5Y29ycA">
    <cycAnnot:label xml:lang="en">InternetStandard</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard is a kind of product specification, applicable to &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtUyJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkingProgram&lt;/a&gt;s, concerning how the product behaves in the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt; environment.</rdfs:comment>
    <rdfs:label xml:lang="en">Internet standard</rdfs:label>
  </owl:Class>

  <owl:Thing rdf:about="http://umbel.org/umbel/sc/InternetStandard">
    <cycAnnot:label xml:lang="en">InternetStandard</cycAnnot:label>
    <rdfs:comment xml:lang="en">An internet standard is a kind of product specification, applicable to &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVtUyJwpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;NetworkingProgram&lt;/a&gt;s, concerning how the product behaves in the &lt;a href=&quot;http://sw.opencyc.org/2008/06/10/concept/Mx4rvVnZe5wpEbGdrcN5Y29ycA&quot; class=&quot;cyc_term&quot;&gt;Internet&lt;/a&gt; environment.</rdfs:comment>
    <rdfs:label xml:lang="en">Internet standard</rdfs:label>
  </owl:Thing>

</rdf:RDF>
