LocationFeatureSpecification

A Schema.org Type

Thing > Intangible > StructuredValue > PropertyValue > LocationFeatureSpecification

[more...]

Canonical URL: https://schema.org/LocationFeatureSpecification
Check for open issues.

Specifies a location feature by providing a structured value representing a feature of an accommodation as a property-value pair of varying degrees of formality.

Property	Expected Type	Description
Properties from LocationFeatureSpecification
`hoursAvailable`	OpeningHoursSpecification	The hours during which this service or contact is available.
`validFrom`	Date or DateTime	The date when the item becomes valid.
`validThrough`	Date or DateTime	The date after when the item is not valid. For example the end of an offer, salary period, or a period of opening hours.
Properties from PropertyValue
`maxValue`	Number	The upper value of some characteristic or property.
`measurementTechnique`	Text or URL	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 or 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 or 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`	Boolean or Number or StructuredValue or Text	The value of the quantitative value or property value node. For QuantitativeValue and MonetaryAmount, the recommended type for values is 'Number'. For PropertyValue, it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'. Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similiar Unicode symbols. Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.
`valueReference`	DefinedTerm or Enumeration or MeasurementTypeEnumeration or PropertyValue or QualitativeValue or QuantitativeValue or StructuredValue or Text	A secondary value that provides additional information on the original value, e.g. a reference temperature or a type of measurement.
Properties from Thing
`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`	PropertyValue or Text or URL	The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
`image`	ImageObject or URL	An image of the item. This can be a URL or a fully described ImageObject.
`mainEntityOfPage`	CreativeWork or URL	Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. Inverse property: mainEntity
`name`	Text	The name of the item.
`potentialAction`	Action	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`	CreativeWork or Event	A CreativeWork or Event about this Thing. Inverse property: about
`url`	URL	URL of the item.

Instances of LocationFeatureSpecification may appear as a value for the following properties

Property	On Types	Description
amenityFeature	Accommodation or FloorPlan or LodgingBusiness or Place	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.

Acknowledgements

This element is based on the STI Accommodation Ontology, see http://ontologies.sti-innsbruck.at/acco/ns.html for details. Many class and property definitions are inspired by or based on abstracts from Wikipedia, the free encyclopedia.

Examples

Example 1

No Markup Microdata RDFa JSON-LD Structure

Example notes or example HTML without markup.

This example is in microdata only.

Example encoded as Microdata embedded in HTML.

<div itemscope itemtype="https://schema.org/Hotel">
  <h1><span itemprop="name">ACME Hotel Innsbruck</span></h1>
  <span itemprop="description">A beautifully located business hotel right in the
heart of the alps. Watch the sun rise over the scenic Inn valley while
enjoying your morning coffee.</span>
  Hotel Features:
  <ul>
  <li itemprop="amenityFeature" itemscope itemtype="https://schema.org/LocationFeatureSpecification">
    <span itemprop="name">Sauna</span>
    <meta itemprop="value" content="True">
  </li>
  <li itemprop="amenityFeature" itemscope itemtype="https://schema.org/LocationFeatureSpecification">
    <span itemprop="name">Gym</span>
    <meta itemprop="value" content="True">
  </li>
  </ul>
</div>

Example encoded as RDFa embedded in HTML.

This example is in microdata only.

Example encoded as JSON-LD in a HTML script tag.

This example is in microdata only.

Structured representation of the JSON-LD example.

Example 2