Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Bucket comment "The class of elements that can contain other elements but no text nodes.".
- Container comment "This class concerns the structural organization of a document. Elements following this pattern contain no textual content and contain only elements compliant with the patterns: Meta, Field, Block and any subtype of Container. It is disjointed with the pattern Popup, although they share the same content model.".
- Field comment "This class is defined to describe literal metadata or text that is not really part of the document body, contrarily to its disjointed sibling Atom. Its main difference with Meta is that Field can contain textual content.".
- Flat comment "The class of elements that can contain text nodes but no elements.".
- HeadedContainer comment "This class describes container elements whose content model need to begin with one or more block elements (the heading), specified through the property containsAsHeader.".
- Inline comment "This class has the same use and content model of the pattern Block, but differing primarily because a) inline elements can contain other elements compliant with the same pattern while block elements cannot, and b) inline elements must always be contained by other block or inline elements and by no other type of element.\n\nThese constraints also imply that inline elements cannot be used as root elements of documents and that the class Block is disjoint with the class Inline (i.e., a markup element cannot be a block and an inline at the same time).".
- Marker comment "The class of elements that can contain neither text nodes nor elements.".
- Meta comment "This class describes elements that contain neither other elements nor textual content. Contrarily to the pattern Milestone, which was meant to describe markup elements that impact the document because of their location, the main feature of its disjoint sibling is the mere existence, independently from the position it has within the document. Meta elements convey metadata information about the document or part of it, independently of where they are. Thus, meta elements can be contained only within container elements.".
- Milestone comment "This class describe elements that contain neither other elements nor textual content. Moreover, similarly to Inline, elements following the Milestone pattern can only be contained within block or inline elements (and consequently they also cannot be used as root elements of documents).\n\nThe distinctive characteristic of the pattern Milestone is the location it assumes within the document.".
- Mixed comment "The class of elements that can contain other elements and text nodes.".
- NonStructured comment "The class of elements that cannot contain other elements.".
- NonTextual comment "The class of elements that cannot have textual content in their content models.".
- Pattern comment "A structural pattern is an atomic component of a document, that is able to capture a recurrent and well knwon structure of a document.\n\nAny entity belonging to this class is compliant with exactly one structural pattern.".
- Popup comment "This class defines bucket elements that are only present within block and inline elements. Popup elements are used whenever complex structures need to be placed within content elements such as paragraphs.".
- Record comment "This class describes container elements that can only contain heterogeneous and non repeatable elements.".
- Structured comment "The class of elements that can contain other elements.".
- Table comment "This class describes container elements that must contain only homogeneous elements (but they can be repeated).".
- Textual comment "The class of elements that can have textual content in their content models.".
- canContainHeteronymousElements comment "A hierarchical-based entity contains al least two entities having different names.".
- canContainHomonymousElements comment "A hierarchical-based entity contains al least two entities that share the same name.".
- contains comment "A structured element contains another generic element.".
- containsAsHeader comment "A structured element contains another generic element as part of its header.".
- hasName comment "The name of a particular element.".
- isContainedBy comment "An element that is contained by another structured element.".
- isContainedByAsHeader comment "An element is contained by another structured element as part of its header.".
- tvc comment "A pattern for the description of scenarios that involve entities having some value during a particular time and within a particular context.".
- ValueInTime comment "It defines a particular kind of time-indexed situation that represents a hub linking the entity having a particular value, the value itself and the temporal and contextual extents from which the entity-value relationship depends.".
- atTime comment "It specifies the particular temporal instant or time period in which the situation takes place.".
- hasValue comment "It links an entity (e.g., a Person) to a particular ValueInTime situation;".
- withValue comment "It holds the value had by the entity taking part to the situation.".
- withinContext comment "It links to the specific context within which the fact of the entity having the value is relevant.".
- cito-functions comment "CiTOFunctions is an ontology that classifies each CiTO property according to the factual and rhetorical citational function it refers to.".
- CitationFunction comment "A class defining the set of citation types having a particular function.".
- FactualFunction comment "A class defining the set of citation types having a factual function.".
- NegativeRhetoricalFunction comment "A class defining the set of citation types having a negative rhetorical function.".
- NeutralRhetoricalFunction comment "A class defining the set of citation types having a neutral rhetorical function.".
- PositiveRhetoricalFunction comment "A class defining the set of citation types having a positive rhetorical function.".
- RhetoricalFunction comment "A class defining the set of citation types having a particular rhetorical function.".
- vagueness comment "The Vagueness Ontology (VO) allows one to specify vagueness characterisations of the TBox entities of an ontology.".
- ApplicabilityContext comment "A context defines precise boundaries of application of descriptions of vagueness/non-vagueness or of the relation between a justification and a certain dimension.".
- DescriptionOfNonVagueness comment "The descriptive characterisation of non-vagueness to associate to an ontological entity by means of an annotation. It provides at least one justification for considering the target ontological entity non-vague. This description is primarily meant to be used for entities that would typically be considered vague but which, for some reason, in the particular ontology are not. \n\nA description of non-vagueness is a context-dependent object, which means that it can be applied within the boundaries of a particular context (i.e. the same entity can be vague in one context and non-vague in another).".
- DescriptionOfVagueness comment "The descriptive characterisation of vagueness to associate to an ontological entity by means of an annotation. It specifies a vagueness type and provides at least one justification for considering the target ontological entity vague. \n\nA description of vagueness is a context-dependent object, which means that it can be applied within the boundaries of a particular context (i.e. the same entity can be vague in one context and non-vague in another).".
- Dimension comment "A dimension is part of the justification of a description of quantitative vagueness. Dimensions of such a justification are used to identify what boundaries are not defined precisely by a particular entity and, thus, are part of the causes of vagueness for the entity itself. A dimension is defined either as natural language text, an entity, a more complex logic formula, or any combination of them. \n\nThe relation between a justification and a dimension may be context-dependent, which means that it can be applied within the boundaries of a particular context (i.e. the same entity can be vague in dimension A in one context and in dimension B in another). In this case, instances of the classes 'DimensionInContext' should be used to link the justification to the related dimension.".
- DimensionInContext comment "This class describes situations where a particular dimension in considered according to a particular context. In particular, instances of this class are actually specifying that the relation between a justification and a certain dimension must be considered according to a particular applicability context.".
- Justification comment "A justification that explains one possible reason behind a vagueness/non-vagueness description. It is defined either as natural language text, an entity, a more complex logic formula, or any combination of them.".
- VaguenessAnnotation comment "The annotation of an ontological entity with information about its vagueness is a particular act of tagging done by someone (i.e., an agent) who associates a description of vagueness/non-vagueness (called the body of the annotation) to the entity in consideration (called the target of the annotation).".
- VaguenessType comment "A particular kind of vagueness that characterizes the entity.".
- hasApplicabilityContext comment "This property links either descriptions of vagueness/non-vagueness or dimensions of descriptions of quantitative vagueness to the context to which they apply.".
- hasDimension comment "It links justifications of a description of quantitative vagueness to the dimensions that identify what boundaries are not defined precisely by a particular entity and, thus, are part of the causes of vagueness for the entity itself.".
- hasDimensionInContext comment "It links justifications of a description of quantitative vagueness to situations where a particular dimension, which identifies the boundaries that are not defined precisely by a particular entity, has to be considered within a particular applicability context.".
- hasEntity comment "The entity defining the body of either a justification or dimension.".
- hasJustification comment "It links a particular description of vagueness/non-vagueness to a related justification.".
- hasLogicFormula comment "The logic formula defining the body of either a justification or dimension.".
- hasNaturalLanguageText comment "The natural language text defining the body of either a justification or dimension.".
- hasVaguenessType comment "The link between a description of vagueness and the particular type of vagueness it describes.".
- qualitative-vagueness comment "A vagueness type that concerns the identification of such other discriminants of which boundaries are not quantifiable in any precise way.".
- quantitative-vagueness comment "A vagueness type that concerns the (real or apparent) lack of precise boundaries defining an entity along one or more specific dimensions.".
- withDimension comment "It links the dimension that is used in a justification according to a particular applicability context.".
- ontology comment "Modifications from version 3.01 :\n Added : gn:GeonamesFeature, subclass of gn:Feature.\n Added : explicit property gn:geonamesID, mandatory and unique for each gn:GeonamesFeature instance.\n Deleted : owl:FunctionalProperty declarations for properties attached to gn:Feature, replaced by local cardinality restrictions on gn:GeonamesFeature\n The gn:Feature class and attached properties can therefore be used in the open world for features not necessarily identified in the Geonames data base, or with partial descriptions.\n Modified : Equivalent classes and superclasses of geonames:Feature in other vocabularies.\n Added : new feature codes for historical features.\n Improved metadata.".
- A comment "country, state, region ...".
- Class comment "A class of features.".
- Code comment "A feature code.".
- Feature comment "A geographical feature".
- Feature comment "An entity that has a geonames feature id".
- H comment "stream, lake, ...".
- L comment "parks,area, ...".
- Map comment "A Web page displaying a map".
- P comment "city, village,...".
- R comment "road, railroad, ...".
- RDFData comment "A Document containing RDF description of one or several features.".
- S comment "spot, building, farm, ...".
- T comment "mountain, hill, rock, ...".
- U comment "undersea".
- V comment "forest, heath, ...".
- WikipediaArticle comment "A Wikipedia article".
- countryCode comment "A two letters country code in the ISO 3166 list".
- countryCode comment "The countryCode value for a Geoname Feature is equal to the countryCode value of the parentCountry value.".
- featureClass comment "The main category of the feature, as defined in geonames taxonomy.".
- featureCode comment "Type of the feature, as defined in geonames taxonomy.".
- locatedIn comment "Indicates that the subject resource is located in the object feature".
- name comment "The main international name of a feature. The value has no xml:lang tag.".
- parentFeature comment "A feature parent of the current one, in either administrative or physical subdivision.".
- ns comment "Marl is an ontology designed to use for publishing the results of the opinion mining process in a form of structured data on the Web. The goal is to unify the access the numerical approximation of the opinion concept and allow extensive reasoning and search over multiple resources from different content providers.".
- AggregatedOpinion comment "The same as Opinion class but indicates that the properties of this class aggregate all the opinions specified in the \"extractedFrom\" source. Optionally, if the aggregatesOpinion property is used this class could be created to aggregate only certain opinions (e.g. in a text about political scene it there could be many AggregatedOpinion classes each with opinions per different politician).".
- Negative comment "Negative polarity.".
- Neutral comment "Neutral polarity".
- Opinion comment "Describes the concept of opinion expressed in a certain text.".
- Polarity comment "Class that represents the opinion polarity. Use instances to express if the polarity is positive, neutral or negative.".
- Positive comment "Positive polarity".
- SentimentAnalysis comment "<p style=\"margin-top: 0\">\n The action of analysing the sentiment in an entity. It produces a \n marl:opinion\n </p>".
- extractedFrom comment "Indicates the text from which the opinion has been extracted.".
- hasOpinion comment "Indicates that a certain text has a subjective opinion expressed in it.".
- ns comment "Onyx is an ontology designed to use for publishing the results of the emotion mining process in a form of structured data on the Web. The goal is to unify the access the numerical approximation of the emotion concept and allow extensive reasoning and search over multiple resources from different content providers.".
- ActionTendency comment "Action Tendency of the emotion: a desire to behave in select communicative or important actions that are connected to a particular feeling.".
- AggregatedEmotion comment "The same as Emotion, used to aggregate several emotions".
- AggregatedEmotionSet comment "The same as the EmotionSet class but indicates that the properties of this class aggregate all the emotions detected in the \"extractedFrom\" source. If the aggregatesEmotionSet property is used this class could be created to aggregate only certain emotions.".
- AppraisalProperty comment "Parent for Appraisal properties.".
- DimensionProperty comment "Parent for Dimension properties.".
- Emotion comment "Class that represents emotions in a generic way".
- EmotionAnalysis comment "The action of analysing the sentiment in an entity. It produces an onyx:emotion".