| Property | On Types | description |
|---|---|---|
| amenityFeature | An amenity feature (e.g. a characteristic or service) of the Accommodation. This generic property does not make a statement about whether the feature is included in an offer for the main accommodation or available at extra costs. |
| Property | Expected Type | description |
|---|---|---|
| hoursAvailable | The hours during which this service or contact is available. | |
| validFrom | Date DateTime | the date and time when the offer becomes active, meaning when you can start booking, purchasing, or accepting it. Example: For the boat lease, this might be when the offer is first posted (e.g., June 1, 2010). |
| validThrough | Date DateTime | This is the date and time after which the offer can no longer be accepted. It’s the deadline to book or buy. Example: For the boat lease, this is the last moment to reserve it (e.g., July 15, 2010, at 23:59). |
| Property | Expected Type | description |
|---|---|---|
| maxValue | Number | The upper value of some characteristic or property. |
| measurementTechnique | URL Text | A technique or technology used in a Dataset (or DataDownload, DataCatalog),
corresponding to the method used for measuring the corresponding variable(s) (described using variableMeasured). This is oriented towards scientific and scholarly dataset publication but may have broader applicability; it is not intended as a full representation of measurement, but rather as a high level summary for dataset discovery. For example, if variableMeasured is: molecule concentration, measurementTechnique could be: "mass spectrometry" or "nmr spectroscopy" or "colorimetry" or "immunofluorescence". If the variableMeasured is "depression rating", the measurementTechnique could be "Zung Scale" or "HAM-D" or "Beck Depression Inventory". If there are several variableMeasured properties recorded for some given data object, use a PropertyValue for each variableMeasured and attach the corresponding measurementTechnique. |
| minValue | Number | The lower value of some characteristic or property. |
| propertyID | Text URL | A commonly used identifier for the characteristic represented by the property, e.g. a manufacturer or a standard code for a property. propertyID can be
(1) a prefixed string, mainly meant to be used with standards for product properties; (2) a site-specific, non-prefixed string (e.g. the primary key of the property or the vendor-specific ID of the property), or (3)
a URL indicating the type of the property, either pointing to an external vocabulary, or a Web resource that describes the property (e.g. a glossary entry).
Standards bodies should promote a standard prefix for the identifiers of properties from their standards. |
| unitCode | Text URL | The unit of measurement given using the UN/CEFACT Common Code (3 characters) or a URL. Other codes than the UN/CEFACT Common Code may be used with a prefix followed by a colon. |
| unitText | Text | A string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for
unitCode. |
| value | The value of the quantitative value or property value node.\n\n For QuantitativeValue and MonetaryAmount, the recommended type for values is 'Number'.\n For PropertyValue, it can be 'Text', 'Number', 'Boolean', or 'StructuredValue'.\n Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator. | |
| valueReference | A secondary value that provides additional information on the original value, e.g. a reference temperature or a type of measurement. |
| Property | Expected Type | description |
|---|---|---|
| additionalType | URL | An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally. |
| alternateName | Text | An alias for the item. |
| description | Text | A description of the item. |
| disambiguatingDescription | Text | A sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation. |
| identifier | The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. | |
| image | URL ImageObject | An image of the item. This can be a URL or a fully described ImageObject. |
| instanceOf | Type to which this subject belongs. Use for membership in a value set (Enumeration), not inheritance. Example: K2 instanceOf mountain; volcano subClassOf mountain. | |
| mainEntityOfPage | URL CreativeWork | Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. |
| name | Text | The name of the item. |
| potentialAction | Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role. | |
| sameAs | URL | URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website. |
| subjectOf | A CreativeWork or Event about this Thing. | |
| url | URL | URL of the item. |