http://purl.org/goodrelations/v1#PaymentChargeSpecification
A payment charge specification is a conceptual entity that specifies the additional costs asked for settling the payment after accepting a given gr:Offering using a particular gr:PaymentMethod. A payment 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 payment method, and (3) a whether this charge includes local sales taxes, namely VAT.
A gr:Offering may be linked to multiple payment charge specifications that specify alternative charges for various payment methods.
Examples: Payment by VISA or Mastercard costs a fee of 3 Euros including VAT, payment by bank transfer in advance is free of charge.
The total amount of this surcharge is specified as a float value of the gr:hasCurrencyValue property. The currency is specified via the gr:hasCurrency datatype property. Whether the price includes VAT or not is indicated by the gr:valueAddedTaxIncluded datatype property. The gr:PaymentMethod to which this charge applies is specified using the gr:appliesToPaymentMethod object property.
If the price can only be given as a range, use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue for the upper and lower bounds.
Important: When querying for the price, always use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue.
Instances of gr:PaymentChargeSpecification can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class gr:PaymentChargeSpecification | |||
| gr:appliesToPaymentMethod | owl:ObjectProperty | This property specifies the gr:PaymentMethod to which the gr:PaymentChargeSpecification applies. | gr:PaymentMethod |
| From class gr:PriceSpecification | |||
| gr:hasCurrency | owl:DatatypeProperty | The currency for all prices in the gr:PriceSpecification given using the ISO 4217 standard (3 characters). | xsd:string |
| gr:hasCurrencyValue | owl:DatatypeProperty | This property specifies the amount of money for a price per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the price per delivery or payment. GoodRelations also supports giving price information as intervals only. If this is needed, use gr:hasMaxCurrencyValue for the upper bound and gr:hasMinCurrencyValue for the lower bound. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y. | xsd:float |
| gr:hasMaxCurrencyValue | owl:DatatypeProperty | This property specifies the UPPER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the UPPER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the UPPER BOUND of the price per delivery or payment. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y. | xsd:float |
| gr:hasMinCurrencyValue | owl:DatatypeProperty | This property specifies the LOWER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc. For a gr:UnitPriceSpecification, this is the LOWER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the LOWER BOUND of the price per delivery or payment. Using gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y. | xsd:float |
| gr:valueAddedTaxIncluded | owl:DatatypeProperty | This property specifies whether the applicable value-added tax (VAT) is included in the price of the gr:PriceSpecification or not. Note: This is a simple representation which may not properly reflect all details of local taxation. | xsd:boolean |
| From class owl:Thing | |||
| dc:contributor | owl:AnnotationProperty | owl:Thing | |
| dc:creator | owl:AnnotationProperty | owl:Thing | |
| dc:rights | owl:AnnotationProperty | owl:Thing | |
| dc:subject | owl:AnnotationProperty | owl:Thing | |
| dc:title | owl:AnnotationProperty | owl:Thing | |
| dcterms:license | owl:AnnotationProperty | owl:Thing | |
| foaf:depiction | owl:ObjectProperty | owl:Thing | |
| foaf:homepage | owl:AnnotationProperty | owl:Thing | |
| gr:displayPosition | owl:AnnotationProperty | The position at which the option or element should be listed in a menu or user dialog, lower numbers come first. The main usage of this property are the days of the week (gr:DayOfWeek), but it is also possible to apply it e.g. to product features or any other conceptual element. Note: Rely on this property only for data originating from a single RDF graph; otherwise, unpredictable results are possible. | owl:Thing |
| gr:relatedWebService | owl:AnnotationProperty | The URI of a SOAP or REST Web Service from which additional information about the gr:BusinessEntity, gr:Offering, gr:PriceSpecification, or gr:ProductOrService, or any other element, can be obtained. The recommended range is xsd:anyURI i.e., the URI of a SOAP or REST Web Service. In principle, any existing or upcoming vocabulary for Web Services can be used in combination with GoodRelations, because the association between (a) the service description and (b) the GoodRelations description can be found via the Web Service URI value used with this gr:relatedWebService property. | owl:Thing |
| http://schema.org/description | owl:DatatypeProperty | owl:Thing | |
| http://schema.org/image | owl:ObjectProperty | owl:Thing | |
| http://schema.org/manufacturer | owl:ObjectProperty | owl:Thing | |
| http://schema.org/name | owl:DatatypeProperty | owl:Thing | |
| http://schema.org/productID | owl:DatatypeProperty | owl:Thing | |
| owl:deprecated | owl:AnnotationProperty | owl:Thing | |
@prefix gr: <http://purl.org/goodrelations/v1#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
gr:PaymentChargeSpecification a owl:Class ;
rdfs:label "Payment charge specification"@en ;
rdfs:comment """A payment charge specification is a conceptual entity that specifies the additional costs asked for settling the payment after accepting a given gr:Offering using a particular gr:PaymentMethod. A payment 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 payment method, and (3) a whether this charge includes local sales taxes, namely VAT.
A gr:Offering may be linked to multiple payment charge specifications that specify alternative charges for various payment methods.
Examples: Payment by VISA or Mastercard costs a fee of 3 Euros including VAT, payment by bank transfer in advance is free of charge.
The total amount of this surcharge is specified as a float value of the gr:hasCurrencyValue property. The currency is specified via the gr:hasCurrency datatype property. Whether the price includes VAT or not is indicated by the gr:valueAddedTaxIncluded datatype property. The gr:PaymentMethod to which this charge applies is specified using the gr:appliesToPaymentMethod object property.
If the price can only be given as a range, use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue for the upper and lower bounds.
Important: When querying for the price, always use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue."""@en ;
rdfs:isDefinedBy <http://purl.org/goodrelations/v1> ;
rdfs:subClassOf gr:PriceSpecification ;
owl:disjointWith gr:DeliveryChargeSpecification,
gr:UnitPriceSpecification .