alist of the representation formats supported by the service. Example: text/html, text/xml, application/json the version or release identifier of the service the default format used by the service unless otherwise specified the set of namespaces recognized by this service. Because many namespace identifiers tend to be cryptic (i.e. HL7 OIDs, BioPortal URL's, etc.), <i>knownNamespace</i> includes the namespace name, an optional URI \emph{and} a place to provide textual detail describing what the namespace references. Note that namespace names must be unique across an entire CTS2 implementation - the same namespace name cannot represent one namespace in code system A and a second in code system B. Note also that namespace names are \emph{local} to a service instance. Information that is communicated between service instances, recorded in data tables or client software \emph{must} use full URIs. a reference to the individual or organization that provides the service. the set of service profiles that are supported by this service implementation a description of the service, its use, etc. a short name that identifies the particular service and implementation the particular implementation type(s) supported by this profile Intersect the supplied entity list with what the entities in the resolved set and return those that are in common. Load the resolved value set into the local resolution list and return a URI that references it. remove the referenced set from the service