Overview of keyword tags

Cocoa is one of Apple Inc.'s native object-oriented application programming interfaces (APIs) for the Mac OS X operating system and - along with the Cocoa Touch extension for gesture recognition and animation - for applications of iOS on Apple's iPhone and iPad product lines. Cocoa applications are typically developed using the development tools provided by Apple, specifically Xcode (formerly Project Builder) and Interface Builder, using the Objective-C language. However, the Cocoa programming environment can be accessed using other tools, such as Clozure CL, LispWorks, Object Pascal, Python, Perl, Ruby, and AppleScript with the aid of bridging mechanisms such as PasCocoa, PyObjC, CamelBones and RubyCocoa. An implementation of the Ruby language, called MacRuby, which does away with the requirement for a bridging mechanism, is under development by Apple, while Nu is a Lisp-like language which can be used with Cocoa without a bridge. It is also possible to write Objective-C Cocoa programs in a simple text editor and build it manually with GCC or clang from the command line or from a makefile. (Excerpt from Wikipedia article: Cocoa)

The description of collections is important in the context of network library services and an important underpinning for developing a collective resource. The creation of collection descriptions allows the owners or curators of collections to disclose information about their existence and availability to interested parties. Although collection descriptions may take the form of unstructured textual documents (for example a set of Web pages describing a collection), there are significant advantages in describing collections using structured, open and standardised formats. Such descriptions would enable: users to discover and locate collections of interest; users to perform searches across multiple collections in a controlled way; software to perform such tasks on behalf of users, based on known user preferences. (Excerpt from this source)

A communications protocol (also known as a network protocol) is a formal description of digital message formats and the rules for exchanging those messages in or between computing systems and in telecommunications. Protocols may include signaling, authentication and error detection and correction capabilities. A protocol describes the syntax, semantics, and synchronization of communication and may be implemented in hardware or software, or both. (Excerpt from Wikipedia article: Network protocol)

The verb license or grant licence means to give permission. The noun license (American English) or licence (British English) refers to that permission as well as to the document recording that permission. A license may be granted by a party ("licensor") to another party ("licensee") as an element of an agreement between those parties. A shorthand definition of a license is "an authorization (by the licensor) to use the licensed material (by the licensee)." In particular a license may be issued by authorities, to allow an activity that would otherwise be forbidden. It may require paying a fee and/or proving a capability. The requirement may also serve to keep the authorities informed on a type of activity, and to give them the opportunity to set conditions and limitations. (Excerpt from Wikipedia article: License)

Content Management Interoperability Services (CMIS) is a specification for improving interoperability between Enterprise Content Management systems. OASIS approved CMIS as an OASIS Specification on May 1, 2010. CMIS provides a common data model covering typed files, folders with generic properties that can be set or read. In addition there may be an access control system, and a checkout and version control facility, and the ability to define generic relations. There is a set of generic services for modifying and querying the data model, and several protocol bindings for these services, including SOAP and Representational State Transfer (REST), using the Atom convention. The model is based on common architectures of document management systems. Although initiated by AIIM, CMIS is now being administered by the OASIS standards body. Participants in the process include Adobe Systems Incorporated, Alfresco, EMC, eXo, FatWire, HP, IBM, ISIS Papyrus, Liferay, Microsoft, Open Text, Oracle and SAP. The standard is available for public comment at OASIS. (Excerpt from Wikipedia article: Content Management Interoperability Services)

A content package is a file containing content and metadata. A content package is used in e-learning to define some learning content or an assessment that can be delivered, for example by a Learning Management System. It's a standard way of describing learning content that can be read by many programs. The most widely used content packaging format is that defined by IMS Global, which uses an XML manifest file called imsmanifest.xml wrapped up inside a zip file. The learning content itself is either included in the zip file if it is HTML or other media that can run on its own, or else is referenced as a URL from within the manifest. The IMS format was used by SCORM to define their packaging format, and typically every SCORM content object (SCO) is defined by a content package. (Excerpt from Wikipedia article: Content package)

Web syndication is a form of syndication in which website material is made available to multiple other sites. Most commonly, web syndication refers to making web feeds available from a site in order to provide other people with a summary or update of the website's recently added content (for example, the latest news or forum posts). The term can also be used to describe other kinds of licensing website content so that other websites can use it. (Excerpt from Wikipedia article: Content syndication)

Controlled vocabularies provide a way to organize knowledge for subsequent retrieval. They are used in subject indexing schemes, subject headings, thesauri and taxonomies. Controlled vocabulary schemes mandate the use of predefined, authorised terms that have been preselected by the designer of the vocabulary, in contrast to natural language vocabularies, where there is no restriction on the vocabulary. (Excerpt from Wikipedia article: Controlled vocabularies)

What makes a cool URI? A cool URI is one which does not change....Keeping URIs so that they will still be around in 2, 20 or 200 or even 2000 years is clearly not as simple as it sounds. However, all over the Web, webmasters are making decisions which will make it really difficult for themselves in the future. Often, this is because they are using tools whose task is seen as to present the best site in the moment, and no one has evaluated what will happen to the links when things change. The message here is, however, that many, many things can change and your URIs can and should stay the same. They only can if you think about how you design them. (Excerpt from this source)