This HTML5 document contains 5 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
grhttp://purl.org/goodrelations/v1#
rdfshttp://www.w3.org/2000/01/rdf-schema#
n5http://purl.org/goodrelations/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
owlhttp://www.w3.org/2002/07/owl#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
gr:DeliveryChargeSpecification
rdf:type
owl:Class
rdfs:subClassOf
gr:PriceSpecification
rdfs:label
DeliveryChargeSpecification
rdfs:isDefinedBy
n5:v1
rdfs:comment
A Delivery Charge Specification is a conceptual entity that specifies the additional costs asked for the delivery of a given Offering using a particular Delivery Method by the respective Business Entity. A Delivery Charge Specification is characterized by (1) a monetary amount per order specified as a literal value of type float in combination with a Currency, (2) the Delivery Method, (3) the target Country or Region, and (4) whether this charge includes local sales taxes, namely VAT. An Offering may be linked to multiple Delivery Charge Specifications that specify alternative charges for disjoint combinations of target Countries or Regions, and Delivery Methods. Examples: Delivery by direct download is free of charge worldwide, delivery by UPS to Germany is 10 Euros per order, delivery by Mail within the US is 5 Euros per order. The total amount of this charge is specified as a float value of the hasCurrencyValue property. The currency is specified via the hasCurrency datatype property. Whether the price includes VAT or not is indicated by the valueAddedTaxIncluded datatype property. The Delivery Method to which this charge applies is specified using the appliesToDeliveryMethod object property. The region or regions to which this charge applies is specified using the eligibleRegions datatype property, which uses ISO 3166-1 and ISO 3166-2 codes. If the price can only be given as a range, use hasMaxCurrencyValue and hasMinCurrencyValue for the upper and lower bounds. Important: When querying for the price, always use hasMaxCurrencyValue and hasMinCurrencyValue.