<?xml version="1.0" encoding="UTF-8"?> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:ns0="http://purl.org/goodrelations/v1#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:metadata_def="http://data.bioontology.org/metadata/def/" xmlns:metadata="http://data.bioontology.org/metadata/" xmlns:ns1="http://purl.org/goodrelations/"> <owl:Class rdf:about="http://purl.org/goodrelations/v1#PaymentChargeSpecification"> <rdfs:subClassOf rdf:resource="http://purl.org/goodrelations/v1#PriceSpecification"/> <metadata_def:mappingSameURI rdf:resource="http://purl.org/goodrelations/v1#PaymentChargeSpecification"/> <metadata_def:mappingLoom>paymentchargespecification</metadata_def:mappingLoom> <owl:disjointWith rdf:resource="http://purl.org/goodrelations/v1#UnitPriceSpecification"/> <metadata_def:prefLabel>Payment charge specification</metadata_def:prefLabel> <rdfs:comment xml:lang="en">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.</rdfs:comment> <metadata:prefixIRI>gr:PaymentChargeSpecification</metadata:prefixIRI> <rdfs:isDefinedBy rdf:resource="http://purl.org/goodrelations/v1"/> <rdfs:label xml:lang="en">Payment charge specification</rdfs:label> </owl:Class> <rdf:Description rdf:about="http://purl.org/goodrelations/v1#DeliveryChargeSpecification"> <owl:disjointWith> <rdf:Description rdf:about="http://purl.org/goodrelations/v1#PaymentChargeSpecification"> <metadata_def:mappingSameURI rdf:resource="http://purl.org/goodrelations/v1#PaymentChargeSpecification"/> </rdf:Description> </owl:disjointWith> </rdf:Description> <rdf:Description rdf:about="http://purl.org/goodrelations/v1#appliesToPaymentMethod"> <rdfs:domain rdf:resource="http://purl.org/goodrelations/v1#PaymentChargeSpecification"/> </rdf:Description> </rdf:RDF>