Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- DocumentFragmentByOffset comment "We may treat a document a one dimensional string, so we can mark a fragment with two offsets. We don't use byte because characters in text document may be multi-bytes.".
- Format comment "A plan for the organization and arrangement of specified information. Examples: binary, text, pdf, etc.".
- IdentifiedThing comment "The abstract root of provenance related concepts. It organizes a collection of common metadata about the referenced object, and it does not have any instance.".
- InferenceEngine comment "An inference engine represents an engine that is able to produce a justification for a conclusion. Note that the phrase \"inference engine\" applies not only to reasoners but also to other systems like search engines which may justify their answers by direct assertion".
- InferenceRule comment "Inference rules are used to derive conclusions from premises.\nInference Web divides inference rules into three classes: Primitive and Derived and Translation. \nThis is an abstract class without any direct instance. A primitive rule is an atomic rule with respect to an inference engine. An inference engine may support rules that it does not need to further decompose. Since a primitive rule is an inference engine dependent concept, we may find a rule is primitive to one inference engine but not to another engine. For example a `natural deduction reasoner R1 may define Modus Ponens as a primitive rule and another reasoner R2 may register Robinson's resolution rule as a primitive rule. The reasoner R2 may be able to derive a Modus Ponens rule using its primitive resolution rule.".
- Information comment "A piece of information, e.g. a formula in logic languages, and an utterance/word/phrase/sentence/paragraph/article in natural language. It is used as a range of iw:hasContent. This class and two of its sub-classes enable users to specify four types of semantics (i) Information Annotation - annotate just the format and language used by the content of information; (ii) Information With Content - additionally provide the content of information that is materialized as string without loading a web page; (iii) Information external - additionally provide the URL for fetching the content; and (iv) Information - with every thing including the content string and URL. The second semantics is especially useful when the content is short or mainly used locally. For example, when learning by instruction, the utterances used for learning can be stored within the PML document without being externally stored. By assigning URI reference to information, we can even use owl:sameAs to capture the equivalence of two pieces of information.".
- Language comment "The language used to encode the raw string, e.g. English, Knowledge Interchange Format (KIF) , and N3. Languages are in general registered at the core IWRegistry.".
- LearnedSourceUsage comment "A special type of source usage. It records the modification of sources - the question that initiates the learning process, the duration of learning, the original source and current source used by learning.".
- MethodRule comment "A method inference rule, uses patterns for premises and its conclusions, and additionally contains a method that must be applied. In addition, \nthe conclusion needs to be a valid output of the method, using the premises. For example, procedural attachment is a common encoding form for method rules.".
- Organization comment "A group of agents organized for a particular purpose, e.g., KSL, stanford.".
- PrettyNameMapping comment "specially designed for pretty display purpose.".
- Publication comment "If we have two versions of the same publication, we need to create two instances of Publication. A publication may have multiple ISBNs.".
- Software comment "written programs or procedures or rules and associated documentation pertaining to the operation of a computer system and that are stored in read/write memory.(WordNet)".
- Source comment "A source refers to the source of information. It is the place where we obtain information.".
- SourceUsage comment "A usage of the source. It records an access of a source at a certain date time.".
- TranslationRule comment "Translation rules are special kinds of inference rules which are used to translate expressions from one language to the other.".
- hasAbstract comment "The abstract of a document.".
- hasAuthorList comment "A list of agents primarily responsible for making the artifact, for example, a person, an organization, or a software service. The AgentList enables an ordered list of agents; however, domain applications may optionally choose to ignore the order. We should be able to derive that each agent is the dc:creator of the artifact.".
- hasContent comment "This is a common concept that links to a piece of information. Currently, we focus on content of document, and inference rule.".
- hasCreationDateTime comment "When the artifact has been first created.".
- hasDataCollectionEndDateTime comment "the time stamp when data collection ended".
- hasDataCollectionStartDateTime comment "the time stamp when data collection started".
- hasDocument comment "A document fragment always depend on one source document, which is also the source.".
- hasEnglishDescriptionTemplate comment "it is sub-property of rdfs:comment. It is also a simplified template for adding rule description template in English rather than using hasDescription.".
- hasFormat comment "it specifies the format of information, e.g. \"pdf\", \"ppt\" (Power Point). It is mainly used to determine the appropriate application for process/display purpose.".
- hasFromCol comment "The from column of the fragment (inclusive, index based on 1)".
- hasFromLanguage comment "language used by the source.".
- hasFromOffset comment "The from offset of the fragment (inclusive, index based on 0).".
- hasFromRow comment "The from row of the fragment (inclusive, index based on 1)".
- hasISBN comment "The International Standard Book Number.".
- hasInferenceEngineRule comment "The inference rules used by the inference engine".
- hasLanguage comment "it specifies the language used to encode information, e.g. \"Tony's specialty is shellfish\" is encoded in English. This property may also link to a registered formal language such as KIF.".
- hasMember comment "An organization may have member agents such as persons and other organizations.".
- hasName comment "the human readable label of the identified thing.".
- hasOwner comment "the owner of a thing.".
- hasPrettyNameMappingList comment "The rendering instruction. UI tools may feed the PrettyNameMapping in sequence to string replace operation to get a pretty rendering of the conclusion of a NodeSet. It only applies to the conclusion of the node set.".
- hasPrettyString comment "the human friendly presentation of the information. Its format is text and it is usually written in English.".
- hasPublicationDateTime comment "When the publication is published.".
- hasRawString comment "materialized version of the content of information".
- hasReferenceSourceUsage comment "Explain how this information is obtained from a source: by whom, when, which source and which part of the source.".
- hasSource comment "the source of the Source Usage, i.e. where does it come from.".
- hasToCol comment "The to column of the fragment (inclusive, index based on 1)".
- hasToLanguage comment "language used by the target.".
- hasToOffset comment "The to offset of the fragment (exclusive, index based on 0)".
- hasToRow comment "The to row of the fragment (inclusive, index based on 1)".
- hasURL comment "The URL of a relevant web page.".
- hasUsageDateTime comment "the time stamp when the source usage occurred.".
- hasUsageQueryContent comment "The query content that leads to the source usage. e.g. the query part of a URL.".
- hasVersion comment "the version number.".
- kdo comment "This ontology has been developed in context with the RENDER project.".
- Bias comment "A bias can be attached to a kdo:Statement and can therefore also relate to agents, posts, and opinions. More specifically, a bias can also relate to another bias.".
- Opinion comment "The opinion class represents is used to contextualize2 provenance, crawling other meta-information. A blank node may be used to represent opinions. Opinions are connected to statement through kdo:hasOpinion.".
- Polarity comment "The kdo:Polarity class is used to express the polarity of sentiments. The predefined instances of this class are: kdo:neutralPolarity, kdo:positivePolarity, kdo:negativePolarity.".
- Sentiment comment "The sentiment class represents the sentiments expressed by the opinions and posts. A sentiment can have (kdo:hasPolarity) different types of polarity (positive, negative, and neutral) and a decimal score (kdo:hasScore). It is in the range of kdo:hasSentiment.".
- Statement comment "The statement class is the central class in the core of the KD ontology. It serves as a hub that connects sentiments (kdo:hasSentiment), opinions (kdo:hasOpinion), biases (kdo:hasBias), posts (kdo:hasPost), and agents (kdo:involvedAgent). Moreover, each statement may have an expression which is a string literal.".
- food.owl comment "Defines concepts and properties specific for the Philips use case (cooking domain).".
- Recipe comment SideCourse.
- EndpointStatus comment "A Status of a void:Dataset endpoint at a particular time".
- statusIsAvailable comment "Describes whether a void:Dataset endpoint is available or not".
- statusResponseTime comment "If a void:Dataset endpoint is available, this property indicates in milliseconds the responseTime to a simple Select query".
- Agent comment "An Agent is an abstract entity which has agency or is considered capable of acting in some way. Current subclasses include Deities and Persons.".
- Attestation comment "An Attestation models a piece of evidence for something in a text (e.g. the mention of a person in a document). Typically it is the conjunction of a Citation and an entity like a name or person.".
- Citation comment "A Citation models a bibliographic reference as a resource.".
- CollationItem comment "(Experimental) Part of a collation of witnesses to a text.".
- ConceptualWork comment "A Conceptual Work groups together one or more Written Works which\n have the same intellectual source. E.g. The Iliad, as opposed to a particular manuscript witness or edition of the Iliad.".
- EvidentiaryItem comment "Superclass for types of evidence that support assertions.".
- Name comment "A name is a resource providing a name for some thing. It may be specialized with subclasses like PersonalName or PlaceName".
- Person comment "Any person, whether historical, mythological, or fictional".
- Place comment "Any conceivable place, such as a town, a mountain, or the site of a building.".
- Reading comment "(Experimental) The superclass for members of the readingScheme concept scheme. A Reading is a word, phrase, or larger chunk of text from a witness (or any observation of variance concerning the text, such as an omission or interpolation).".
- Siglum comment "A Siglum represents a witness (a Written Work of some kind) and\n associates it with a symbol used to represent that work in the context of an\n Edition.".
- WrittenWork comment "A written work, whether extant or not. May be considered to embody a Conceptual Work.".
- readingScheme comment "(Experimental) The SKOS scheme for classifying types of lawd:Reading.".
- responsibleAgent comment "Connects a work of any type to the person, group, or insitution\n responsible for the creation of the work.".
- responsibleFor comment "Connects any kind of author or creator to the work he/she/it is\n responsible for creating. The author may be anonymous or fictional.".
- where comment "Generic location relation.".
- lemon comment "Lemon: The lexicon model for ontologies is designed to allow for descriptions of lexical information regarding ontological elements and other RDF resources. Lemon covers mapping of lexical decomposition, phrase structure, syntax, variation, morphology, and lexicon-ontology mapping.".
- Argument comment "A slot representing a gap that must be filled in realising a lexical entry in a given projection".
- Component comment "A constituent element of a lexical entry. This may be a word in a multi-word lexical element or a constituent of a compound word".
- ComponentList comment "A node within a list of components. This should generally be a blank node,see rdf:List".
- Form comment "A given written or spoken realisation of a lexical entry".
- Frame comment "A stereotypical example of the usage of a given lexical entry. The most common example of projections are subcategorization frames which describe the slots taken by the arguments of a verb.".
- HasLanguage comment "Structural element for all elements that can be tagged with a language".
- LexicalCondition comment "An evaluable condition on when a sense applies.".
- LexicalContext comment "Indicates the pragmatic or discourse context in which a sense applies".
- LexicalEntry comment "An entry in the lexicon. This may be any morpheme, word, compound, phrase or clause that is included in the lexicon".
- LexicalSense comment "Represents the intersection in meaning between the lexical entry and the ontology entity. This is used as the ontology entity and lexical entry may not be in one-to-one correspondence as such the existence of a sense between them states meerly that there are some cases when this lexical entry refer to the ontology entity and vica versa. Mapping elements can be used to further specify this relation".
- LexicalTopic comment "Indicates the topic of a lexicon or a lexical entry".
- Lexicon comment "The lexicon object. This object is specific to the given language and/or domain it describes".
- Node comment "A node in a phrase structure or dependency parse graph".
- NodeConstituent comment "The class of constituents, that is types applied to nodes in a phrase structure graph".
- Part comment "An affix is a morpheme that is attached to a word stem to form a new word. Use this for lexical entries with only abstract forms".
- Phrase comment "A phrase in lemon is defined in the looser sense of a sequence of words, it does not have to a fully grammatical phrase".
- PhraseElement comment "A terminal node in a phrase structure graph, i.e., a realisable, lexical element.".
- PropertyValue comment "A value that can be used in the range of linguistic property".
- SenseContext comment "Indicates the context in which a term is to be used. The context refers not to the immediate syntactic context, but the document and register the document is used in".
- SenseDefinition comment "A definition of a sememe, that is the a text describing the exact meaning of the lexical entry when its sense is the given ontology reference".
- SynRoleMarker comment "The indicator of a given syntactic argument, normally a preposition or other particle marker or a linguistic property such as case".
- UsageExample comment "An example of the usage of a lexical entry when refering to the ontology entity given by the sememe's reference. This should in effect be an example of the form used in context. E.g., \"this is a *usage example*\"".
- Word comment "A word is a single unit of writing or speech. In languages written in Latin, Cyrillic, Greek, Arabic scripts etc. these are assumed to be separated by white-space characters. For Chinese, Japanese, Korean this should correspond to some agreed segmentation scheme.".