Ontologies Classes Object Properties Data Properties Annotation Properties Individuals Datatypes Clouds

Annotation Property: rdfs:comment

Usage (96)

  • DD040_PercutaneousCoronaryIntervention isConditionedTo perSession
  • DL020_InvasiveMonitoring isConditionedTo otherUnits
  • dc:contributor dc:contributor dc:contributor rdfs:comment "Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity." @en-us 
  • dc:coverage rdfs:comment "Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges." @en-us 
  • dc:creator rdfs:comment "Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity." @en-us 
  • dc:date rdfs:comment "Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601." @en-us 
  • dc:description rdfs:comment "Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource." @en-us 
  • dc:format rdfs:comment "Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types." @en-us 
  • dc:identifier rdfs:comment "Recommended best practice is to identify the resource by means of a string conforming to a formal identification system." @en-us 
  • dc:language rdfs:comment "Recommended best practice is to use a controlled vocabulary such as RFC 4646." @en-us 
  • dc:publisher rdfs:comment "Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity." @en-us 
  • dc:relation rdfs:comment "Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system." @en-us 
  • dc:rights rdfs:comment "Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights." @en-us 
  • dc:source rdfs:comment "The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system." @en-us 
  • dc:subject rdfs:comment "Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element." @en-us 
  • dc:title rdfs:comment "Typically, a Title will be a name by which the resource is formally known." @en-us 
  • dc:type rdfs:comment "Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary. To describe the file format, physical medium, or dimensions of the resource, use the Format element." @en-us 
  • dcterms:Agent rdfs:comment "Examples of Agent include person, organization, and software agent." @en-us 
  • dcterms:AgentClass dcterms:AgentClass rdfs:comment "Examples of Agent Class include groups seen as classes, such as students, women, charities, lecturers." @en-us 
  • dcterms:FileFormat dcterms:FileFormat rdfs:comment "Examples include the formats defined by the list of Internet Media Types." @en-us 
  • dcterms:LinguisticSystem rdfs:comment "Examples include written, spoken, sign, and computer languages." @en-us 
  • dcterms:PhysicalMedium dcterms:PhysicalMedium rdfs:comment "Examples include paper, canvas, or DVD." @en-us 
  • dcterms:RFC3066 rdfs:comment "RFC 3066 has been obsoleted by RFC 4646." @en-us 
  • dcterms:RFC4646 rdfs:comment "RFC 4646 obsoletes RFC 3066." @en-us 
  • dcterms:SizeOrDuration dcterms:SizeOrDuration rdfs:comment "Examples include a number of pages, a specification of length, width, and breadth, or a period in hours, minutes, and seconds." @en-us 
  • dcterms:accessRights rdfs:comment "Access Rights may include information regarding access or restrictions based on privacy, security, or other policies." @en-us 
  • dcterms:alternative rdfs:comment "The distinction between titles and alternative titles is application-specific." @en-us 
  • dcterms:bibliographicCitation rdfs:comment "Recommended practice is to include sufficient bibliographic detail to identify the resource as unambiguously as possible." @en-us 
  • dcterms:contributor rdfs:comment "Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity." @en-us 
  • dcterms:coverage rdfs:comment "Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges." @en-us 
  • dcterms:creator rdfs:comment "Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity." @en-us 
  • dcterms:date rdfs:comment "Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF]." @en-us 
  • dcterms:dateAccepted rdfs:comment "Examples of resources to which a Date Accepted may be relevant are a thesis (accepted by a university department) or an article (accepted by a journal)." @en-us 
  • dcterms:dateSubmitted rdfs:comment "Examples of resources to which a Date Submitted may be relevant are a thesis (submitted to a university department) or an article (submitted to a journal)." @en-us 
  • dcterms:description rdfs:comment "Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource." @en-us 
  • dcterms:format rdfs:comment "Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types [MIME]." @en-us 
  • dcterms:identifier rdfs:comment "Recommended best practice is to identify the resource by means of a string conforming to a formal identification system." @en-us 
  • dcterms:instructionalMethod rdfs:comment "Instructional Method will typically include ways of presenting instructional materials or conducting instructional activities, patterns of learner-to-learner and learner-to-instructor interactions, and mechanisms by which group and individual levels of learning are measured. Instructional methods include all aspects of the instruction and learning processes from planning and implementation through evaluation and feedback." @en-us 
  • dcterms:isVersionOf rdfs:comment "Changes in version imply substantive changes in content rather than differences in format." @en-us 
  • dcterms:language rdfs:comment "Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]." @en-us 
  • dcterms:mediator rdfs:comment "In an educational context, a mediator might be a parent, teacher, teaching assistant, or care-giver." @en-us 
  • dcterms:provenance rdfs:comment "The statement may include a description of any changes successive custodians made to the resource." @en-us 
  • dcterms:publisher rdfs:comment "Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity." @en-us 
  • dcterms:relation rdfs:comment "Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system." @en-us 
  • dcterms:rights rdfs:comment "Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights." @en-us 
  • dcterms:source rdfs:comment "The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system." @en-us 
  • dcterms:subject rdfs:comment "Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element." @en-us 
  • dcterms:type rdfs:comment "Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE]. To describe the file format, physical medium, or dimensions of the resource, use the Format element." @en-us 
  • skos:altLabel rdfs:comment "The range of skos:altLabel is the class of RDF plain literals." @en 
  • skos:altLabel rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties." @en 
  • skos:broader rdfs:comment "Broader concepts are typically rendered as parents in a concept hierarchy (tree)." @en 
  • skos:exactMatch rdfs:comment "skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch." @en 
  • skos:hiddenLabel rdfs:comment "The range of skos:hiddenLabel is the class of RDF plain literals." @en 
  • skos:hiddenLabel rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties." @en 
  • skos:mappingRelation rdfs:comment "These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice." @en 
  • skos:memberList rdfs:comment "For any resource, every item in the list given as the value of the
    skos:memberList property is also a value of the skos:member property."     @en 
  • skos:narrower rdfs:comment "Narrower concepts are typically rendered as children in a concept hierarchy (tree)." @en 
  • skos:prefLabel rdfs:comment "A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag." @en 
  • skos:prefLabel rdfs:comment "The range of skos:prefLabel is the class of RDF plain literals." @en 
  • skos:prefLabel rdfs:comment "skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise
    disjoint properties."     @en 
  • skos:related rdfs:comment "skos:related is disjoint with skos:broaderTransitive" @en 
  • Access rdfs:comment "Access models types of access related to a specific medical procedure. It explains how the target region of the medical procedure was reached. Access is static information already available in the APC." 
  • ActiveProduct rdfs:comment "Active implantable devices are products, which are implanted in the human body and need an additional source of energy (other than energy obtained from the human body or gravity)." 
  • Aim rdfs:comment "Aim describes and models the aim, which underlies a specific procedure. It answers the question, what is the best possible outcome of a medical procedure?" 
  • AnesthesiaRespiratorDevice rdfs:comment "Medical products and accessories for supply, conditioning, monitoring, distribution, and emission of respiration gas or medical and anesthetic gas" 
  • BiologicalDevice rdfs:comment "Medical Devices that are of biological origin (e.g. xenografts)" 
  • BodyFunction rdfs:comment "Body function models functions of the human body. Body function is static information available in the APC." 
  • BodySystem rdfs:comment "The Body system describes the system of a human body that is affected by a specific medical procedure. The body system contains static information from the Austrian Procedure catalogue." 
  • ChargableUnit rdfs:comment "Unit describes how often a medical procedure can be coded." 
  • ComplementaryMedicineDevice rdfs:comment "Medical devices that are used for complementary medicine." 
  • DentalDevice rdfs:comment "Products used for identification, prevention, monitoring, treating, or relief of diseases of the mouth, jaw or facial area, and teeth." 
  • Device rdfs:comment "Device models the medical devices used to perform a specific medical procedure." 
  • Discipline rdfs:comment "If a medical procedure is related to a certain medical discipline, it is modeled in Discipline." 
  • DrainProcedure rdfs:comment "direct the evacuation of a fluid away from its place of origin in the body, by means of a suitable device (drain, wick, drainage sheet tec) left in place" 
  • ElectromedicalMechanicalDevice rdfs:comment "Elektromedical and electromechanical devices are medical products, which need an additional electric source of energy for functioning." 
  • HospitalInventory rdfs:comment "Hospital inventory subsumes products that are not used vor diagnostics or examinations and have no direct influence on the assessment of the patient's status, the examination results or the further treatment." 
  • ImagingDevice rdfs:comment "Medical devices for diagnostics or therapy taht make use of X-rays, magnetic resonance, ultrasound, isotopes, or linear accelerators." 
  • InVitroExamination rdfs:comment "In vitro examination procedures" 
  • InVivoSituDiagnostics rdfs:comment "In vivo and in situ diagnostic procedures" 
  • MedicalProcedure rdfs:comment "The core of the ontology is the Medical procedure concept, which is directly related to most of the other concepts. It represents the Medical procedure itself according to the APC." 
  • MedicalTreatment rdfs:comment "Treatment based on medication" 
  • NonActiveProduct rdfs:comment "Non-active implantable products are products that are implanted for 30 days or longer and are no active implantable products." 
  • OphthalmicDevice rdfs:comment "Products used for identification, prevention, monitoring, treating, or relief of diseases of the eyesight." 
  • Pathology rdfs:comment "Pathology models the disease or malfunction that made a specific medical procedure necessary. This class can be used as some sort of connection points, if the ontology needs to be extended with diseases or mapped to a disease or diagnosis coding system or ontology (e.g. the International Classification of Diseases – ICD)." 
  • Population rdfs:comment "If specific demographic groups are affected by a medical procedure, it is modeled in the Population." 
  • ProcedureType rdfs:comment "Procedure type models the type of a medical procedure according to the original version of the Austrian Procedure catalogue." 
  • ReusableDevice rdfs:comment "Mecical devices that can be reused after cleaning and sterilization." 
  • Side rdfs:comment "Side discribes, which side of of the human body was affected by a medical procedure in case a terget site has two different sides (e.g. lunge, kidney)." 
  • SingleUseDevice rdfs:comment "Single use devices are products meant for one-time use only." 
  • SpecialOverhead rdfs:comment "Describes procedures where special overheads are needed." 
  • TechnicalAssistanceDevice rdfs:comment "Products for the compensation, relief, prevention, or neutralization of a physical impairment, the loss of a bodily function or a handicap." 
  • Technique rdfs:comment "Technique class models the exact approach of a medical procedure. They are often named after their inventor." 
  • Therapy Therapy rdfs:comment "Describes a medical procedure as a therapy procedure" 
  • rdfs:comment "OWL 2 DL ontology for Dublin Core metadata elements from the http://purl.org/dc/elements/1.1/ namespace" @en
  • rdfs:comment "OWL 2 DL ontology for Dublin Core metadata terms from the http://purl.org/dc/terms/ namespace; this version is grounded in the DC elements ontology and only uses annotation properties." @en
  • rdfs:comment "OWL 2 DL ontology for a few terms of the DCMI abstract model from the http://purl.org/dc/dcam/ namespace" @en

OWL HTML inside