Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- usedStar comment "A multi-step used property.".
- value comment "the value of a role or a property".
- wasDerivedFromStar comment "the transitive closure of wasDerivedFrom".
- wasGeneratedByStar comment "A multi-step wasGeneratedBy edge.".
- fridge comment "Ontology for Open Fridge project".
- EnergyObservation comment "An energy observation is the main class of the measurment system. The observation connects to the sensing device, the measurement property, the observed appliance, the measurment result, and the time of measurement.".
- EnergySensingDevice comment "An energy sensing device is sensing device for sensing energy consumption data".
- OpenFridgeHousehold comment "Information about the household of the open fridge user".
- OpenFridgeUser comment "The main user of the system, which lives in a household with a energy consumption measuring system.".
- Power comment "Power is the observed measurment property".
- hasHousehold comment "Open fridge user has an open fridge household".
- observationProperty comment "Property of a fridge in the time period of observation.".
- AboveRoomTemperature comment "A WeatherPhenomenon describing a temperature of more than 25 degrees Celsius.".
- AtmosphericPressure comment "A WeatherPhenomenon specifying atmospheric pressure using the hasPressure property (in hPa/mbar on MSL).".
- BelowRoomTemperature comment "A WeatherPhenomenon describing a temperature of less than 20 degrees Celsius.".
- Calm comment "A WeatherPhenomenon describing a wind speed of less than 1 m/s.".
- ClearSky comment "A WeatherPhenomenon describing a cloud layer with cloud cover 0 (clear sky).\n\nNOTE: This class only specifies a single cloud layer. It does not make any statement about other cloud layers.".
- CloudCover comment "A WeatherPhenomenon giving information about a cloud layer. There are two properties: hasCloudCover gives the cloud cover of this layer in okta (an integer in the interval [0-9] where 0 is clear sky, 8 is overcast and 9 is unknown). hasCloudAltitude gives the altitude of that cloud layer.\n\nIf there is more than one cloud layer, for each cloud layer another WeatherPhenomenon must be created and linked to the appropriate WeatherState.".
- CurrentWeatherReport comment "A WeatherState describing the current weather.".
- DewPoint comment "A WeatherPhenomenon specifying the dew point. The actual value is specified in degrees Celsius using the hasDewPoint property.".
- Dry comment "A WeatherPhenomenon describing a humidity of less than 40 percent.".
- Forecast12HoursWeatherReport comment "A WeatherState describing the weather in 12 hours.".
- Forecast15HoursWeatherReport comment "A WeatherState describing the weather in 15 hours.".
- Forecast18HoursWeatherReport comment "A WeatherState describing the weather in 18 hours.".
- Forecast1HourWeatherReport comment "A WeatherState describing the weather in one hour.".
- Forecast21HoursWeatherReport comment "A WeatherState describing the weather in 21 hours.".
- Forecast24HoursWeatherReport comment "A WeatherState describing the weather in 21 hours.".
- Forecast2HoursWeatherReport comment "A WeatherState describing the weather in two hours.".
- Forecast3HoursWeatherReport comment "A WeatherState describing the weather in three hours.".
- Forecast6HoursWeatherReport comment "A WeatherState describing the weather in 6 hours.".
- Forecast9HoursWeatherReport comment "A WeatherState describing the weather in 9 hours.".
- ForecastWeatherReport comment "A WeatherState describing the weather for some time in the future.".
- Frost comment "A WeatherPhenomenon describing a temperature of less than 0 degrees Celsius.".
- Heat comment Temperature.
- Heat comment WeatherPhenomenon.
- Heat comment "A WeatherPhenomenon describing a temperature of more than 30 degrees Celsius.".
- Heat comment hasTemperature.
- Humidity comment "A WeatherPhenomenon specifying relative humidity. Relative umidity specified using the hasHumidity property (in the interval [0,1]).".
- Hurricane comment "A WeatherPhenomenon describing a wind speed of more than 32 m/s.".
- LightWind comment "A WeatherPhenomenon describing a wind speed of less than 1 m/s.".
- Moist comment "A WeatherPhenomenon describing a humidity of more than 70 percent.".
- MostlyCloudy comment "A WeatherPhenomenon describing a cloud layer with cloud cover 5, 6 or 7 (mostly cloudy).\n\nNOTE: This class only specifies a single cloud layer. It does not make any statement about other cloud layers.".
- NoRain comment "A WeatherPhenomenon describing the absence of precipitation, either because the probability for precipitation is 0 (specified by the property hasPrecipitationProbability) or because the amount of precipitation per hour is 0 (specified by the property hasPrecipitationValue) or both.".
- Overcast comment "A WeatherPhenomenon describing a cloud layer with cloud cover 8 (overcast).\n\nNOTE: This class only specifies a single cloud layer. It does not make any statement about other cloud layers.".
- PartlyCloudy comment "A WeatherPhenomenon describing a cloud layer with cloud cover 1, 2, 3 or 4 (partly cloudy).\n\nNOTE: This class only specifies a single cloud layer. It does not make any statement about other cloud layers.".
- Precipitation comment "A WeatherPhenomenon describing both precipitation probability (property hasPrecipitationProbability, in the interval [0,1]) and the amount of precipitation (property hasPrecipitationValue, in mm/h).".
- RoomTemperature comment "A WeatherPhenomenon describing a temperature between 20 and 25 degrees Celsius.".
- SensorSource comment "A WeatherStateSource as a (collection of) sensor(s).".
- ServiceSource comment "A WeatherStateSource as an internet service.".
- SolarRadiation comment "A WeatherPhenomenon describing sun radiation using the hasSunRadiation property (in W/m²).".
- Storm comment "A WeatherPhenomenon describing a wind speed of more than 20 m/s.".
- StrongWind comment "A WeatherPhenomenon describing a wind speed of less than 1 m/s.".
- SunPosition comment "A WeatherPhenomenon describing the sun's position at solar noon. The property hasSunAngleNoon specifies the angle of the sun above horizon in degrees Celsius.".
- Temperature comment "A WeatherPhenomenon specifying temperature. The actual temperature is specified using the hasTemperature property (in degrees Celsius).".
- WeatherCondition comment "A WeatherCondition is a simple description of the state of the weather. Currently there are: Cloud, Fog, LightCloud, PartlyCloud, Rain, Sleet, Snow, Sun, Thunder.\n\nSeveral instances of WeatherCondition can be associated with the same instance of WeatherPhenomenon using the hasCondition property. That way, it is possible to describe a thunderstorm that comes with rain.".
- WeatherPhenomenon comment WeatherState.
- WeatherPhenomenon comment hasCloudAltitude.
- WeatherPhenomenon comment hasCloudCover.
- WeatherPhenomenon comment hasPrecipitationProbability.
- WeatherPhenomenon comment hasWindDirection.
- WeatherPhenomenon comment hasWindSpeed.
- WeatherPhenomenon comment "A WeatherPhenomenon specifies information about the weather (temperature, humidity etc.) for a certain WeatherState. It is linked to the WeatherState using the belongsToState property.\n\nFor specifying the weather information, there exist several data properties: hasTemperature, hasHumidity, hasDewPoint, hasWindSpeed, hasWindDirection, hasPrecipitationProbability, hasPrecipitationValue, hasPressure, hasCloudCover, hasCloudAltitude, hasSunRadiation and hasSunAngleNoon.".
- WeatherPhenomenon comment belongsToState.
- WeatherPhenomenon comment hasDewPoint.
- WeatherPhenomenon comment hasHumidity.
- WeatherPhenomenon comment hasPrecipitationValue.
- WeatherPhenomenon comment hasPressure.
- WeatherPhenomenon comment hasSunRadiation.
- WeatherPhenomenon comment hasTemperature.
- WeatherPhenomenon comment sunAngleNoon.
- WeatherReport comment "A WeatherObservation puts together all the information known at a certain time about both the current and the future weather at a certain location.\n\nUsing the mandatory properties location a Point -- having latitude, longitude and altitude -- the location this WeatherObservation belongs to is specified. The property hasObservation time gives the time when the data has been collected.\n\nA WeatherObservation can have an arbitrary number of WeatherStates. Each of them gives some information about either the current state of the weather or the weather predicted for some time in the future.".
- WeatherReportSource comment "WeatherStateSource represents a source of weather data, either from a (collection of) sensor(s) (sub-concept SensorSource) or from an internet service (ServiceSource).\n\nWeatherStateSource is connected to WeatherState via the hasSource/isSourceOf properties.".
- WeatherState comment "A WeatherState is a set of weather information (temperature, humidity etc.). It is assigned to exactly one WeatherObservation (properties belongsToWeatherObservation/hasWeatherState), has a priority (property hasPriority) and has a source (where the weather information comes from, properties hasSource/isSourceOf).\n\nThe weather information itself (temperature, humidity etc.) is provided using instances of WeatherPhenomenon that are connected using the belongsToState/hasWeatherPhenomenon properties.".
- Wind comment "A WeatherPhenomenon giving information about wind. There are two properties: hasWindDirection gives the cloud cover of this layer in degrees (an integer in the interval [0-359] where 0 is North, 90 is East etc.). hasWindSpeed is a float specifying wind speed in m/s.".
- belongsToWeatherState comment "Inverse property of hasWeatherPhenomenon.".
- hasCondition comment "Links a WeatherCondition to a WeatherPhenomenon. A WeatherPhenomenon can be associated with an arbitrary number of instances of WeatherCondition.".
- hasPriority comment "Specifies the priority of a WeatherState (a positive integer). The higher this value is compared to another WeatherState's priority, the more the WeatherState takes precedence over the other WeatherState.".
- hasSource comment "Associates a WeatherStateSource with a WeatherState, i.e. specifies where a WeatherState's data comes from. One WeatherState can only have one WeatherStateSource.".
- hasWeatherPhenomenon comment "Associates a WeatherPhenomenon to its WeatherState. One WeatherPhenomenon can only belong to one WeatherState, but one WeatherState can have an arbitrary number of instances of WeatherPhenomenon.".
- hasWeatherState comment "Associates a WeatherState to a WeatherObservation. One WeatherState can only be associated with one WeatherObservation.".
- isSourceOf comment "Inverse property of hasSource.".
- nif-core comment "The NLP Interchange Format (NIF) is an RDF/OWL-based format that aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations. NIF consists of specifications, ontologies and software, which are combined under the version identifier \"2.0\", but are versioned individually. This ontology is developed by the NLP2RDF project (http://nlp2rdf.org) and provided as part of NIF 2.0 under CC-BY license as well as Apache 2.0. The ontology contains seven core URIs (String, RFC5147String, Context, isString, referenceContext, beginIndex, endIndex) that provide the foundation to express NLP annotations effectively in RDF.".
- CString comment "A URI Scheme for NIF which is able to refer to a single, consecutive string in a context. Note that any scheme subclassing this class, requires the existence of beginIndex, endIndex and referenceContext . \n This is an abstract class and should not be serialized. \n ".
- CStringInst comment "An abitrary URI (e.g. a URN) for an arbitrary string of the context. This is roughly the same as TextAnnotations are currently implemented in Stanbol.".
- Context comment "The string that serves as a context for its substrings. The Unicode String given in the nif:isString property must be used to calculate the begin and endIndex for all nif:Strings that have a nif:referenceContext property to this URI. For further information, see http://svn.aksw.org/papers/2013/ISWC_NIF/public.pdf \n \n Changelog\n * 1.0.1. improved documentation\n * 1.0.2. merged inf model\n ".
- ContextCollection comment "A collection of contexts used to create an unordered set of context via the nif:hasContext property. This can be compared to a document collection, but here it is a collection of nif:Context and therefore a collection of annotated strings, not documents. \n \n Open Issues\n Investigate ordered collections\n \n Changelog\n * 0.1.1 improved documentation\n ".
- ContextHashBasedString comment " cf. https://www.google.de/search?q=Linked-Data+Aware+URI+Schemes+for+Referencing+Text".
- OffsetBasedString comment "cf. Linked-Data Aware URI Schemes for Referencing Text Fragments by Sebastian Hellmann, Jens Lehmann und Sören Auer in EKAW 2012 http://jens-lehmann.org/files/2012/ekaw_nif.pdf\n\t\n\trequires the existence of begin, endIndex and referenceContext\n\t\n\tChangelog: \n\t* 1.0.0 originally a plain text string was attached to this uri scheme, but this was removed later, because of complaints and complexity. \n\t* 1.1.0 subclassing of nif:CString\n ".
- RFC5147String comment "cf. http://tools.ietf.org/html/rfc5147 URIs of this class have to conform with the syntax of RFC 5147 in a way that the end on a valid identifier, if you remove the prefix. Note that unlike RFC 5147 NIF does not requrire '#' URIs. So valid URIs are http://example.org#char=0,28 , http://example.org/whatever/char=0,28 , http://example.org/nif?char=0,28\n Changelog:\n * 1.1.0 changed subclass to CString .\n * 1.1.1 typo in rdfs:label and extension of comment\n ".
- Sentence comment "\n A sentence.\n Changelog:\n * 0.1.1 fixed spelling, added language tag\n ".
- String comment "Individuals of this class are a string, i.e. Unicode characters, who have been given a URI and are used in the subject of an RDF statement. \n This class is abstract and should not be serialized. \n \n NIF-Stanbol (nif-stanbol.ttl):\n subclassOf nifs:Annotation because it \"annotates\" strings for example with begin and end index. The class is similar to fise:TextAnnotation\n \n Changelog\n * 1.0.1. improved documentation\n * 1.0.2. merged inf and val model\n ".
- Structure comment "A structure is a more or less arbitrary label for a partitioning of a string. We do not follow a strict approach for what a word, phrase, sentence, title, paragraph is. These labels enable the definition processes for tool chains, e.g. tool analyses nif:Paragraph and calculates term frequency. \n \n This is an abstract class and should not be serialized. \n \n Changelog\n 0.1.1 not to be serialized comment\n ".
- URIScheme comment "A URI Scheme for NIF, subclasses need to define guidelines on the URI Scheme as well as the text it refers to. This class is just to keep some order, and should not be serialized. \n \n This is an abstract class and should not be serialized. \n \n Changelog:\n * 0.1.1 changed comment\n ".
- Word comment "\n The Word class represents strings that are tokens or words. A string is a Word, if it is a word. We don't nitpic about whether it is a a pronoun, a name, a punctuation mark or an apostrophe or whether it is separated by white space from another Word or something else. The string 'He enters the room.' for example has 5 words. Words are assigned by a tokenizer NIF Implementation. Single word phrases might be tagged as nif:Word and nif:Phrase. \n \n Example 1: \"The White House\" are three Words separated by whitespace\n \n Comment 1: We adopted the definition style from foaf:Person, see here: http://xmlns.com/foaf/spec/#term_Person We are well aware that the world out there is much more complicated, but we are ignorant about it, for the following reasons:\n Comment 2: \n \n 1. NIF has a client-server and the client has the ability to dictate the tokenization to the server (i.e. the NIF Implementation) by sending properly tokenized NIF annotated with nif:Word. All NIF Implementations are supposed to honor and respect the current assignment of the Word class. Thus the client should decide which NIF Implementation should create the tokenization. Therefore this class is not descriptive, but prescriptive.\n 2. The client may choose to send an existing tokenization to a NIF Implementation, with the capability to change (for better or for worse) the tokenization. \n \n \n \n The class has not been named 'Token' as the NLP definition of 'token' is descriptive (and not well-defined), while the assignment of what is a Word and what not is prescriptive, e.g. \"can't\" could be described as one, two or three tokens or defined as being one, two or three words. For further reading, we refer the reader to: By all these lovely tokens... Merging conflicting tokenizations by Christian Chiarcos, Julia Ritz, and Manfred Stede. Language Resources and Evaluation 46(1):53-74 (2012) or the short form: http://www.aclweb.org/anthology/W09-3005\n There the task at hand is to merge two tokenization T_1 and T_2 which is normally not the case in the NIF world as tokenization is prescribed, i.e. given as a baseline (Note that this ideal state might not be achieved by all implementations.)\n \n Changelog:\n * 0.1.1 fixed spelling\n * 0.2.1 added a proper definition.\n * 0.2.3 added examples and clarifications\n ".
- anchorOf comment "The string, which the URI is representing as an RDF Literal. Some use cases require this property, as it is necessary for certain sparql queries. ".
- annotation comment "\n see Towards Web-Scale Collaborative Knowledge Extraction http://svn.aksw.org/papers/2012/PeoplesWeb/public_preprint.pdf page 21 .\n Changelog:\n * 0.1.1 Fixed page number\n ".
- beginIndex comment "The begin index of a character range as defined in http://tools.ietf.org/html/rfc5147#section-2.2.1 and http://tools.ietf.org/html/rfc5147#section-2.2.2, measured as the gap between two characters, starting to count from 0 (the position before the first character of a text). \n Example: Index \"2\" is the postion between \"Mr\" and \".\" in \"Mr. Sandman\".\n Note: RFC 5147 is re-used for the definition of character ranges. RFC 5147 is assuming a text/plain MIME type. NIF builds upon Unicode and is content agnostic. \n Requirement (1): This property has the same value the \"Character position\" of RFC 5147 and it MUST therefore be castable to xsd:nonNegativeInteger, i.e. it MUST not have negative values. \n Requirement (2): The index of the subject string MUST be calculated relative to the nif:referenceContext of the subject. If available, this is the rdf:Literal of the nif:isString property.\n \n Changelog: \n * 1.0.0: Introduced stable version.\n * 1.0.1: merged val+inf, added range\n ".
- classAnnotation comment "\n see Towards Web-Scale Collaborative Knowledge Extraction http://svn.aksw.org/papers/2012/PeoplesWeb/public_preprint.pdf page 12 .\n Changelog:\n * 0.1.1 Fixed page number\n ".
- dependencyTrans comment "\n\t\tChangelog: \n\t\t* 0.1.0 initial commit of property\n\t\t* 0.1.1 merged inf model\n ".
- endIndex comment "The end index of a character range as defined in http://tools.ietf.org/html/rfc5147#section-2.2.1 and http://tools.ietf.org/html/rfc5147#section-2.2.2, measured as the gap between two characters, starting to count from 0 (the position before the first character of a text). \n Example: Index \"2\" is the postion between \"Mr\" and \".\" in \"Mr. Sandman\".\n Note: RFC 5147 is re-used for the definition of character ranges. RFC 5147 is assuming a text/plain MIME type. NIF builds upon Unicode and is content agnostic. \n Requirement (1): This property has the same value the \"Character position\" of RFC 5147 and it must therefore be an xsd:nonNegativeInteger . \n Requirement (2): The index of the subject string MUST be calculated relative to the nif:referenceContext of the subject. If available, this is the rdf:Literal of the nif:isString property.".