a non-empty sequence of characters. As terminological resourcesare often multilingual, it is expected that most CTS2 Platform SpecificModels (PSMs) will require that the String implementation
supportinternational character sets.
represents an "Instant" as defined in the OWL Time Specification.CTS2 implementations must be able to support temporal units of second,
minute, hour, day, month, and year, and be able to represent and compare instances represented in any of these units. DateAndTime can only provide a partial ordering and, as a
consequence, is never used as an index, unique identifier or to sequence data or events.
"An enumeration defines a set of literals that can beused as its values" UML Infrastructure, Version 2.3, Section 10.3.2. Because enumeration is a built in part of the UML meta model, the
\guillemotleft enumeration \guillemotright ~stereotype is used to represent them in the UML rendering.
an identifier that uniquely references a class, individual, property or other resource within the context of a specific CTS2 service implementation. LocalIdentifier syntax must match the PNAME_LN production as defined in the SPARQL Query Specification . LocalIdentifiers may begin
with leading digits, where XML Local Identifiers and NameSpaceIdentifiers may not
an identifier that uniquely references thescoping namespace of an Entity (class, role or individual) within a the context of a CTS2 service. NamespaceIdentifier syntax must match the PNAME_NS production as defined in the SPARQL Query Specification - meaning that it must begin alphabetic
character.
a Universal Resource Identifier (URI) as defined in IETF RFC 3986. CTS2 implementations are encouraged to consider implementing this data type
using the IRI (RFC3987) specification.
represents the relative strength of the result of a search. Represented as a real number $\mathbb{R}$ such that $0.0 < MatchStrength \leq 1.0$.
a non-negative integer ($\nat$). NaturalNumber is used exclusively for representing quantities in this specification.
a quantity of time. AmountOfTime is used exclusively to represent service timeout limits.
An opaque inner type that can contain any well-formed, but arbitrary information.
PSM
Opaque data is the equivalent of an ASN.1 External Type ISO/IEC 8824-1:2008 Information technology -- Abstract Syntax Notation One (ASN.1): Specification of basic notion. Clause 37 - Notation for the
external type or the XML Schema anyType. An OpaqueData instance may represent text with an optional spoken or written language code or a
formal structure such as embedded HTML, XML or MIME encoded data. When a formal structure is included, its type should be specified in the format attribute and, when the type is an XML variant, the corresponding
schema (or DTD) should be included in the schema parameter.The OpaqueData data type must be encoded in such a way that the content can be represented by a character string. Binary data is not permitted,although
hyperlinks to binary data are.
the instance value. Note that instance value should be encoded in such a way that it allows embedded structures. As an example, in XML Schema, this encoding should be to xs:anyType or an
equivalent.
the format or encoding for value. This is typically recorded as the URI of a Mime Type.
a reference to the written or spoken language used in value.
if the format of the document involves an XML encoding, this contains the URI of a document that carries the corresponding XML Schema or DTD.
EntryDescription is a subclass of OpaqueData. The purpose behind this is that there are certain textual fields that some CTS2 service implementations may want constrain. As an example,
Designation text is of type \\ EntryDescription, but implementations may want to restrict the OpaqueData
value attribute to a simple string rather than xs:anyType. When OpaqueData appears directly as a model element, implementations must be able to support the full OpaqueData model. EntryDescription,
however, may be constrained by implementations or specialized PSMs.
a Universal Resource Identifier (URI) that persists across service instances. Persistent URI's have enduring reference and meaning.
the unique identifier of a set of change instructions that can potentially transform the contents of CTS2 service instance from one state to another.
a reference to a "work" in the bibliographic sense. It is not necessary that a DocumentURI be directly or indirectly resolvable to a digital resource - it may simply be the name of a book, publication or
other abstraction.
a URI that names a unique resource. CTS2 implementations should never assume that ExternalURI is resolvable via an http: GET operation - ExternalURIs should always be passed as
parameters to service implementations to get the sanctioned equivalent in a given service context
a URI or handle whose scope is local to the implementing service. LocalURI cannot be used as a permanent identifier in a message or a data record.
the unique name of a query that, when executed results in a list of resources that, in the context of a given service, satisfy the query.
a URI or handle that is directly readable by a specific instance of a CTS2 service implementation. RenderingURI must resolve to Changeable CTS2 element.
the URI or handle of a service implementation.
the state of this model element in an externally defined workflow
Detailed information about the last change that resulted in this changeable element being in the state that it is now. changeDescription is only present in services that support the HISTORY profile and then only when specifically requested.
an indicator that states whether the Changeable element is ACTIVE, and subject to searching and browsing access or INACTIVE, meaning that it is only accessible if its identity is
already known or if the service calls specifically state that they want to see inactive service elements
An element that can evolve over time. All Changeable elements must have identity.
the current state of the Changeable element. Note that entryState represents the state of the element itself - not the state of a given change. The applicability of a given change is
identified by its effectiveDate, not entryState.
the ChangeAble element is no longer considered to be an active component. The element may still be retrieved if its entryID is known, but it does not appear in search and browse operations
unless specifically requested.
the Changeable element is considered to be an active member of the containing resource and may appear in any search, browse or query operations.
The detailed description of what happened to a changeable resource. ChangeDescription will only be present in service profiles that support either the History or MAINTENANCE profiles.
a note, set of instructions and other information about the nature and purpose of this change
the person or organization responsible for this change
the local identifier and URI of the resource that was cloned in this change if this is a CLONE operation.
the type of change that occurred to cause the associated Changeable element to reach the state it is in
an indicator that states whether the change has been committed and is available to service consumers or is still pending while further authoring may occur. committed must always be COMMITTED
in services that do not support the MAINTENANCE profile
the URI of the ChangeSet that contains the described change
the URI of the ChangeSet that contains the change that immediately preceded this change, if any
the date and time when this change was applied to the local service instance. changeDate is only present on committed changes.
the date and time that this change is (or was) scheduled to take effect in the local service instance. Typically this attribute is used to schedule a component to become active on a given date.A
change having a future effectiveDate will not be visible to service calls whose reference time is earlier to this time. This attribute may only be present in committed changes. A compliant CTS2 service
implementation MUST not allow a change to be written with a effectiveDate that is earlier than changeDate. The purpose of this requirement is to prevent the "rewriting of history" - making a change
effective in the past.
An indicator that shows the type of change that occurred that transformed a Changeable element from its immediately previous state to the state that the ChangeType is associated
with.
the element was newly created.
one or more non-identifying attributes of the element changed. Note that UPDATE does not include changes to the Changeable attributes (entryState, status, and owner).
These are considered to be METADATA changes.
a change occurred to the entryState or status attributes. METADATA changes are separated because they may often be service specific.
the changeable element was completely removed from the service and may no longer be retrieved by id or search. Service implementations may choose to disable and/or map DELETE operations to
some other form, but this exists to allow the complete removal of errors and historically irrelevant information.
create the new versionable resource and create a (virtual) copy of all of the resource's dependents
include the contents of an external resource version as a read-only part of the importing version
the commitment state of an individual change
the specific change is part of an OPEN change set and has not yet been committed to the database. The change is only visible through queries that carry the ChangeSetURI of the open
ChangeSet.
the specific change is a part of a ChangeSet that has reached a FINAL state, meaning that it is (or will be) considered an official part of the service content.
A common base for various change set elements. This exists to allow ChangeSet to be represented as a choice in the "Updates" module
PSM
the person or organization who initially created the change set
documentation and instructions about the purpose and application of the change set
a globally unique identifier that signifies this particular change set
the date and time that the change set was initially created
the date and time that this set of changes became (or should become) effective from the perspective of the authors. This parameter enables history queries from both the perspective of the service
("What did the service return on July 1") and the perspective of the resource author ("What would the state of the terminology have been on July 1 had it been loaded prior to that date and not been locally modified?").
the date and time that this change set was finalized (state = FINAL). Once finalized, a change set cannot be further modified.
the number of Changeable members in the set
The Finalizable mixin determines whether a resource version or a change set is still undergoing change (OPEN) or has reached its final state (FINAL).
the state of the inheriting resource
possible states of a Finalizable resource
the contents of a ChangeSet or ResourceVersionDescription may change, meaning that the contents cannot be determined by using the ChangeSetURI or
DocumentURI.
the contents of a ChangeSet or ResourceVersionDescription cannot be changed, meaning that they can be unambiguously referenced via the corresponding URI.
Provides a directory or list of resources that match a specific filter and are ordered in a specified order. A directory is read-only and is not necessarily immutable.Note that the name of the link to
DirectoryEntry is called "entries" rather than "entry". This allows subclasses to use "entry" without type collisions in the Z.
the filter(s) that were applied to generate this directory
the sort criteria used in the directory. When this is left as optional, there is the possibility that some directories may not be ordered. Some PSMs may chose to make sortCriteria
mandatory, meaning that all directory listings must reflect some sort order.
an indicator that states whether the complete directory listing is included in entries or whether additional retrievals are needed to get the full listing.
the number of entries in this directory segment. Note that this is not the total number of entries in the complete directory listing - just the number of entries in this
segment.
a URI that, when de-referenced, produces the preceding set of entries in the directory.
a URI that, when de-referenced, produces the next set of entries in the directory.
a LocalURI that resolves to the full resource described by the DirectoryEntry. This should be present if the service either (a) supports the Read functional profile for the specified
type or (b) is aware of another service that does.
a local identifier that names a unique resource within the context of type and the service context. This attribute must be present if the corresponding element has a local name. Note, however, that
some elements (e.g. Association, ValueSetDefinition, etc.) do not local names and are identified exclusively by their href.
a relative measure of the "goodness of fit" of the directory entry within the context of the directoryFilter in the containing Directory.
an entry in a directory. DirectoryEntry is a mixin that identifies the attributes that must or may be present in any element that can be represented as an entry in a Directory.
An indicator that determines whether a Directory contains all of the qualifying entries or only some.
the Directory contains all of the qualifying entries
the directory contains only a partial listing of the qualifying entries
a DirectoryURI that references a set of Associations.
a DirectoryURI that references a set of ChangeSets.
a DirectoryURI that references a set of CodeSystemCatalogEntries.
a DirectoryURI that references a set of CodeSystemVersionCatalogEntries.
a DirectoryURI that references a set of ConceptDomainCatalogEntries
a DirectoryURI that references a set of ConceptDomainBindings.
a DirectoryURI that references a set of EntityDescriptionDirectory
a DirectoryURI that references a set of MapCatalogEntries
a DirectoryURI that references a set of MapVersions
a DirectoryURI that references a set of MapEntries
a DirectoryURI that references a set of Statements
a DirectoryURI that references a set of ValueSetCatalogEntries
a DirectoryURI that references a set of ValueSetDefinitions
The URI, local namespace and name and optional designation of an EntityDescription. EntitySynopsis represents entities when they are referenced from the context of a single code system, such as
the resolution of value sets and association graphs.
a designation considered appropriate for the entity in the specific context of use
The URI, namespace/name (if known) and a list of code systems that make assertions about the entity.
the namespace and name by which this entity is known within the context of the service implementation
a reference to a version of a code system that makes one or more assertions about the referenced entity. Note that only one version of a given code system is allowed in the describingCodeSystem
list. Unless specified otherwise in a specific call, the code system version with the tag "CURRENT" must be used.
the entity URI. This is an ExternalURI if the entityReferenceType is NAMED_ENTITY and a LocalURI is the entityReferenceType is ANONYMOUS_ENTITY.
A reference to specific version of a code system that contains assertions about a given entity, including the namespace and name by which the entity is referenced, an optional designation appropriate to the
given usage context and an optional RenderingURI that references the full EntityDescription contained in the specific code system version.
a reference to the code system version that describes the entity
a contextually appropriate designation for the entity derived from the \\ describingCodeSystemVersion
a RenderingURI that, if followed, will provide a full CTS2
EntityDescription derived from the corresponding code system version
A list (set) of zero or more entity references
A reference to an entity whose name and description is local to the containing code system and service. Information about anonymous entities cannot be shared between services or across code
systems
the namespace and name by which this entity is known within the context of the service implementation
a reference to a version of a code system that makes one or more assertions about the referenced entity. Note that only one version of a given code system is allowed in the describingCodeSystem
list. Unless specified otherwise in a specific call, the code system version with the tag "CURRENT" must be used.
the local URI that identifies this entity within the context of the particular service
A reference to an entity that is identified through a globally unique URI.
the namespace and name by which this entity is known within the context of the service implementation
a reference to a version of a code system that makes one or more assertions about the referenced entity. Note that only one version of a given code system is allowed in the describingCodeSystem
list. Unless specified otherwise in a specific call, the code system version with the tag "CURRENT" must be used.
a URI that identifies a unique entity in a global context
The combination of a namespace identifier and a local name. Scoped entity names are not portable - they only work within the context of a single service instance, as different services may assign different
namespace identifiers to the same namespace and different services may make different choices of the appropriate local identifier to use to represent an entity. As an example, one service may choose to use the entity code
while a second may use another designation that is known to be unique.
an identifier that references a unique namespace URI within the context of the service
the local entity name within the context of the namespace. What is chosen for the entity name is service specific
The combination of a URI and/or and ScopedEntityName.
an identifier that references a unique namespace URI within the context of the service
the local entity name within the context of the namespace. What is chosen for the entity name is service specific
a URI that uniquely references the target entity
a URI that resolves to the full EntityDescription represented by this resource
An expression in a given ontology language and syntax that describes or defines an entity. Examples might include descriptions of entities in Manchester OWL Syntax, RDF, SNOMED Concept Expression,
etc.
An expression in a given ontology language and syntax that describes or defines an entity. Examples might include descriptions of entities in Manchester OWL Syntax, RDF, SNOMED Concept Expression,
etc.
the ontology language and syntax of the expression
the actual expression
a name or identifier that uniquely names an association instance in a code system
a reference to a tool that can be used to create an ontology
a reference to a method model that can be used to create an ontology
A NameAndMeaningReference consists of a local identifier that references a unique meaning within the context of a given domain in a CTS2 service instance and a globally unique URI that
identifies the intended meaning of the identifier.
an ExternalURI that references the meaning of a name. Meaning is optional only because the meaning of some of the elements have not been fully specified in some legacy
terminology resources. If meaning is not supplied, the intent of a reference cannot be shared among services or between other resources.
a RenderingURI that, when dereferenced, results in a CTS2 compliant representation of the meaning of the given NameAndMeaningReference. This must be present if the
implementing CTS2 service is aware of a CTS2 resource that carries the definition.
a reference to an entity that describes the role that a given value set binding plays for a concept domain. Typical values represent "overall", "minimum" or "maximum", the significance of which can be found in
HL7 Version 3 documentation.
a reference to a description of the relative formality an ontology
a reference to an entity that describes significance of the case in term or designation
a reference to information about a paradigm model used to create an ontology (aka. knowledge representation paradigm
a reference to a code system or ontology
a reference to a specific version of code system and, if known, the code system which it is a version of
A reference to the code system that the version is a version of. Must be present if this information is known to the CTS2 service implementation.
a reference to a concept domain
a reference to a realm or context
a reference to a description about designation faithfulness or accuracy
a reference to a designation type or form such as "short name", "abbreviation", "eponym"
a reference to a particular way that information is encoded for storage or transmission
a reference to a spoken or written human language
a reference to an abstract map
a reference to a map version and the corresponding map, if known
a reference to the corresponding map. Must be present if it is known the implementing CTS2 service
a reference to a way that the source and target in a map can be related or assessed
a reference to an algorithm used for selecting and filtering data
a reference to an attribute defined in the CTS2 specification
a reference to a conceptual space that groups identifiers to avoid conflict with items that have the same name but different meanings
a reference to a subject domain for an ontology
a reference to a language in which an ontology may be implemented
a reference to a syntax in which an ontology may be represented
a reference to a purpose for which an ontology can be designed
a reference to the nature of the content of an ontology
An EntityReference that serves the role of predicate. Note that this varies slightly from the base class of NameAndMeaningReference because the name attribute is a namespace/name
combination rather than a simple name scoped exclusively by the domain.
a reference to a formal algorithm for making inferences about an ontology
a reference to a role that an individual, organization or bibliographic reference can play in the construction of a resource or resource component
a reference to an individual, organization of bibliographic reference
a reference to a source that also includes the role that the source played and/or fixes the particular chapter, page or other element within the reference
a role that the source played in the creation of the containing resource
additional bibliographic information such as page number, edition, etc.
a reference to a state in an external ontology authoring workflow
a reference to a named set of entity references
a reference to a set of rules for constructing a value set along with the corresponding value set if known
A reference to the corresponding value set. Must be present if known to the implementing CTS2 service
a reference to a tag that can be assigned to versionable resources within the context of a service implementation
General set operators that specify set union, difference or intersection in various contexts
Include all members of both sets in the result
include only members common to both sets in the result
remove all members in the second set from the first set
A collection of one or more filters. The result of applying a Filter component is the intersection of the sets of qualifying elements. As an example, a filter having two components - one which
says that the rights attribute must exist and a second that says that the text "SNOMED" must appear in the synopsis would return all resources having BOTH a rights attribute and "SNOMED" in the
description.
A restriction on an attribute, property or special field
the algorithm to be used for testing the referenced component. Examples might include "starts with", "regular expression match", "exists", "inRange", etc. NOTE: The CTS2 specification
needs to establish a core set of match algorithms that all compliant implementations must support.
the value to be used in comparison. The structure and format of matchValue depends on the specific matchAlgorithm. As an example, a "startsWith" algorithm would be plain text, a
"regularExpression" algorithm would have a regular expression while an "exists" algorithm would have nothing in the matchValue attribute.
The particular attribute, property or special element to be sorted along with the sort direction
the type and name of the attribute, property or special element to be sorted
the sort order
The collating order of a sort.
sort in ascending collation order
sort in descending collation order
An ordered list of sort criterion. The first entry in the list identifies the primary sort order, the second entry the sub sort order, etc.
An indicator that determines whether an entity reference / predicate combination is to be evaluated with the entity reference in the source (left hand side) position of the association query or the target
(right hand side or "object") position.Note:
AssociationDirection doesn't strictly belong in this diagram, but it is kind of an orphan class and we didn't want to create an entire new diagram just for one element.
the statement is to be resolved with the entity reference in the role of source.
the statement is to be resolved with the entity reference in the role of target.
A reference to a CTS2 model element. PropertyReference may reference a model attribute, a Property or a special element such as match strength.
the type of thing being referenced
the possible types of property references
a reference to an attribute in a CTS2 model such as formalName, designation, etc.
a reference to a model Property. The reference target carries the namespace/name or URI of the property predicate.
the target of the reference is a special element such as the match strength of a search
a local identifier for a CodeSystem
a local identifier for a CodeSystemVersion
a local identifier for a ConceptDomain.
a local identifier for a Map
a local identifier for a MapVersion
a local identifier for a ValueSet
a local identifier for a VersionTag
Note corresponds to the target of skos:note. It contains an attributed literal that may include a language, format and, when appropriate,
schema.
the code system version that contains the assertion(s) represented in the Note
the URI of the Statement from which this note was derived. This will only be present in services that support the Statement profile.
an external identifier assigned to this note by an outside party
Text or other representation that is intended to communicate the intended meaning of the associated entity to a human being. While this is intended to be very close in meaning to skos:definition, its intent is slightly different in that the CTS2 specification does not treat definition as a subproperty of note -
rather it views comments, examples and definitions as separate entities.
the context(s) in which the definition is considered applicable
the role that the definition plays with respect to the defined entity
An example. See: skos:example
PSM
A Note about the history, scope or provenance of the containing element. Comment is differentiated from Example and Definition specifically because it is frequently searched and
displayed under different circumstances and usage contexts. Example and Definition are frequently made available to the end users of a code system while Comments are typically consumed by authors and
editors.
A change note. See: skos:changeNote
PSM
An editorial note. See skos:editorialNote
PSM
A history note. See: skos:historyNote
PSM
A scope note. See: skos:scopeNote
PSM
Undifferentiated See: skos:Note, but do not use for Definition or Example
PSM
The role that a given definition plays for a given entity.
the definition is considered to be official or normative by the assigning body
the definition is considered to be of value, but not completely normative
The language and syntax of an expression in an ontology. Language identifies the expression semantics (e.g. OWL 2.0, RDF, SNOMED Compositional Expression, etc) and syntax identifies how it is represnted (e.g.
XML, text/plain, xml/rdf, manchester syntax, etc)
The formal language (semantics) of the expression.
The syntax of the expression.
ResourceDescription represents the shared characteristics common to both abstract and resource version descriptions. ResourceDescription is an abstract type and, as such, cannot be directly
created. Resource descriptions are Changeable, meaning that they have identity and can be created, updated and deleted.
additional identifiers that are used to index and locatethe resource
the class(es) that this resource instantiates
a textual summary of the resource - what it is, what it is for, etc.
a reference to a document thatprovide additional information about the resource
a reference to an individual, organization of bibliographic reference that participated in the creation, validation, review, dissemination of this resource and therole(s) they
played
copyright and IP information. Note that rights applies to the source resource, not the CTS2 rendering.
an additional note or comment about the resource
additional information about the resource that doesnot fit into any of the attributes described above
an alternative identifier that uniquely names this resource in other environments as contexts. As an example, if a resource had both an ISO Object Identifier and a DNS name, the DNS name might
be assigned as the entryID of the resource by one service while the ISO OID would be recorded as an alternateURI using the "urn:oid" prefix. Note that alternateIds can be added or removed
during resource updates.
a DirectoryURI that references the set of statements that were used to construct the containing resource. This attribute must (may?) be present if and only if the service supports the
Statement profile
the (or a) definitive URI that represents the resource being described. Note that this is NOT the URI of the resource description in the CTS2 format, but of the resource itself. As an example, the
about URI for the Wine ontology would be "http://www.w3.org/TR/2003/PR-owl-guide-20031209/wine#". The NCI Thesaurus has, amongst others, the
about URI of http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#. HL7 uses ISO Object Identifiers (OIDs) to label resources so, from the HL7 perspective, the about URI of the NCI Thesaurus would
be "urn:oid:2.16.840.1.113883.3.26.1.1"
the formal or officially assigned name of this resource, if any
the resource types that can be described in a CTS2 service
an ontology, classification scheme, thesaurus or code system
a specific release or version of an ontology, classification scheme, thesaurus or code system.
a "data element concept" - a specification of the conceptual domain of an element in a database, form, message, etc.
a set of rules for transforming a set of entity references into a second set of entity references, drawn from a different code system or value set.
a specific version or release of a MAP
a set of entity references
a set of rules for establishing which entity references belong to a value set at a given point in time
A
DirectoryEntry that identifies the elements of a resource description that appear in every directory of resources of a particular type. ResourceDescriptionDirectoryEntry is an abstract type and is realized in
the implementing subtypes listed in CTS2ResourceType
a textual summary of the resource - what it is, what it is for, etc.
the (or a) definitive URI that represents the resource being described.
the formal or officially assigned name of this resource
a summary of an abstract resource description
A summary of a resource version.
a label or identifier that was assigned to this version by its publisher
information about the source, format, release date, version identifier, etc. of a specific version of an abstract resource
a URI that identifies the specific version, language and notation of the about resource
the description of the characteristics of a resource that are independent of the resource content
documentation about the frequency and natureof releases (version) of this resource.OMV 2.4.1 pp 18
a format and notation that thereleases (versions) of this resource are published in
information about the source, format, release date, version identifier, etc. of a specific version of an abstract resource
a description of where the (or a) source of the version may be found, what format and language it is available in, etc.
a reference to the name and URI version of the resource from which this current version is derived - the version of the resource that immediately preceded it
an official label or identifier that was assigned to this version by its publisher
the date that this version of the resource officially became available
the date that this version of the resource is stated by its publishers to go into effect
a URI that identifies the specific version, language and notation of the about resource. This URI needs to be constructed in such a way that, if necessary, it will be possible to
differentiate resource versions that were loaded from different document syntaxes. As an example, if an image of a the wine ontology was loaded from a resource that was in Manchester Syntax, it should be given a
different URI than the image loaded from the RDF/XML syntax. The reasoning behind this is, even in cases where different syntaxes are 100% compatible the transformation into the CTS2 model may not be
identical.
A description of the source from which the ResourceVersionDescription was derived. When possible, SourceAndNotation should include a reference to the actual source document from which it was
derived. As an example, if the resource was derived from the W3C Wine Ontology, the URI http://www.w3.org/TR/2003/CR-owl-guide-20030818/wine would unambiguously name the document. In the cases, however, when a definitive
source document is not available, a textual description should be provided, instead, in sourceAndNotationDescription. Where possible, the ontology language and ontology syntax should also be provided. In the case of
the Wine Ontology above, the ontology language would be http://www.w3.org/2002/07/owl# (OWL) and the syntax would be application/rdf+xml.
a textual description of where the specified resource version was derived from. This parameter must be supplied if a reasonable PersistentURI for the source document is not
available.
a persistent URI that references the document from which the resource version was derived. This URI may be resolvable to a digital resource or may be the name of a book, publication or other external
document.
the formal language, if any, that the source for the resource version is expressed in. Examples include Common Logic, OWL, OWL-DL, CLAML,
etc.
the syntax of the source of the resource version, if known. Examples might include rdf/xml, Turtle, Manchester Syntax, CSV, etc.
the target of a Statement. StatementTarget represents one of a literal value, a reference to a non-entity type resource, an entity, or an anonymous blank BNODE.
the URI and optional namespace/name when the target type is ENTITY
the literal target when the statement type is LITERAL.
the resource URI when the statement type is RESOURCE
a collection of statements about an anonymous subject
an external identifier that has been assigned to the statement with this particular target by the authoring body. As an example, this would carry the SctId if the authoring body were
SNOMED-CT
A statement lacking a named subject.
the predicate of the anonymous statement
the target of the anonymous statement
assertions whose subject is the anonymous statement
A tag/value pair that does not have a corresponding model attribute. Property represent any statement about a resource (e.g. CodeSystem, Entity, etc.) that does not have a corresponding attribute in the
CTS2 model. As an example, the NCI Thesaurus uses a tag named BioCarta_ID (C43677) to associate appropriate thesaurus entities with Bio Carta pathway references. This would be represented by a property,
whose predicate is the URI for C436777 and the value is the actual id.
the name and URI of the property predicate
the target(s) of the property. Note that this can only represent the literal format of the property. The details about the original property will be found in the correspondingStatement if the
CTS2 implementation supports the Statement profile.
an assertion whose subject is the assertion in the property instead of the property subject
a link to the original statement from which this Property is derived. Will only be present in CTS2 implementations that support the Statement profile.
a return type that indicates a positive or negative answer to the specific question that was posed.
A parameter in a REST Resource
PSM
The header information for any REST resource retrieval
PSM
The URI of the REST service. As an example, if the resource URI
was "http://informatics.mayo.edu/cts2/rest/codesystems", the resourceRoot would be
"http://informatics.mayo.edu/cts2/rest/"
PSM
The relative URI of the resource with respect to the resourceRoot. As an example,
if the resource URI was "http://informatics.mayo.edu/cts2/rest/codesystems", the resourceURI would
be "codesystems". Fragment and query identifiers should also be included.
PSM
The paramaters that were used in executing the query. This carries all of the parameters that
are needed to reconstruct the complete query in either a RESTful or procedural environment. The service provider
may or may not include non-CTS2 related parameters such as security tokens, routing requests, etc.
PSM
The date and time that the resource was accessed.
PSM
Message header that wraps all returns.
PSM