Knowledge Base Article

Understanding common industry terminology

  • API: Application Programing Interface: A source code interface that a computer system or program library provides in order to support requests for services to be made of it by a computer program. More
  • Breadcrumb: A set of links at a the top of the page that (1) show users where they are and (2) allow uses to retrace their steps up a hierarchy. More
  • CGI Script: Common Gateway Interface script: A standard protocol for interfacing external application software with an information server, commonly a web server. More
  • CNAME: A CNAME record or canonical name record is an alias of one name to another. The address record that the alias is pointing to can be either local or remote - on a foreign name server. This is useful when running multiple services (like an FTP and a web server) from a single IP address. Each service can then have its own entry in DNS (like ftp.example.com and www.example.com.)
  • CSS: Cascading Style Sheets: A stylesheet language used to describe the presentation of a document written in a markup language, the most common application of which is to style web pages written in HTML and XHTML. More
  • DNS: Domain Name Service: DNS stores and associates many types of information with domain names; most importantly, it translates domain names (computer hostnames) to IP addresses. More
  • htaccess: The .htaccess file is a configuration file for web server directory configuration and control. At Khoros, this file is most often used in the context of granting or restricting access to a web site via an IP address range.
  • HTML: HyperText Markup Language: The predominant markup language for the creation of web pages. More
  • IE: Internet Explorer: Microsoft's web browser
  • MX Record: An MX record or mail exchange record maps a domain name to a list of mail exchange servers for that domain.
  • Query String: The part of a URL that contains data to be passed to CGI programs. More
  • Query String Parameters: Data to be passed to CGI Programs in a Query String.
  • REST Representational State Transfer: a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term is also often used in a loose sense to describe any simple interface that transmits domain-specific data over HTTP without an additional messaging layer such as SOAP or session tracking via HTTP cookies. More
  • RFP: Request For Proposal: A formal request submitted to a vendor for a product or service. Typically meant to form the basis of any subsequent SOW. More
  • RSS: Really Simple Syndication (et al): Family of web feed formats used to publish frequently updated digital content, such as blogs, news feeds or podcasts. More
  • SEO: Search Engine Optimization: The process of improving the volume or quality of traffic to a web site from search engines. More
  • SOW: Statement Of Work: A formal document describing in detail the work about to be undertaken for the customer, the responsibilities of each party and the acceptance protocol.
  • SSL: Secure Sockets Layer: cryptographic protocol which provides secure communications on the Internet for such things as web browsing, e-mail, Internet faxing, instant messaging and other data transfers. More
  • SSO: Single Sign On: A specialized form of software authentication that enables a user to authenticate once and gain access to the resources of multiple software systems. More
  • XHTML: eXtensible HyperText Markup Language: A markup language successor to HTML designed to allow for automated processing to be performed using a standard XML library. More

 

 

Updated 6 years ago
Version 8.0
Best Practices
  • bkling's avatar
    bkling
    Boss
    14 years ago

    I would like to suggest you use the same exercise in the Engagement Center and in Reporting, to weed out using mulitple names for the same thing or inaccurate names.  For example, in the Content Tab of Engagement Center, there is a section for "Answer Rate" but these are not answers in that they answered the Topic author's question, but rather "Replies" - it is maybe a small but very significant difference, even then in how we show these reports and outputs internally.  In the Product Support world, an Answer is a very different thing.  In the Responsiveness section you have "Response Rate" - is this different or the same thing?  See this thread...

     

    http://lithosphere.lithium.com/t5/Customer-Connection-Private/Time-to-Answer-and-Response-Time-engagement-centre/m-p/27816#M1531