@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://purl.org/goodrelations/v1#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix ns1: <http://purl.org/goodrelations/> .
ns0:DeliveryChargeSpecification
owl:disjointWith ns0:PaymentChargeSpecification .
ns0:PaymentChargeSpecification
metadata_def:mappingLoom "paymentchargespecification" ;
metadata_def:mappingSameURI ns0:PaymentChargeSpecification ;
metadata_def:prefLabel "Payment charge specification" ;
metadata:prefixIRI "gr:PaymentChargeSpecification" ;
a owl:Class ;
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 ns1:v1 ;
rdfs:label "Payment charge specification"@en ;
rdfs:subClassOf ns0:PriceSpecification ;
owl:disjointWith ns0:UnitPriceSpecification .
ns0:appliesToPaymentMethod
rdfs:domain ns0:PaymentChargeSpecification .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ns0: <http://purl.org/goodrelations/v1#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix metadata_def: <http://data.bioontology.org/metadata/def/> .
@prefix metadata: <http://data.bioontology.org/metadata/> .
@prefix ns1: <http://purl.org/goodrelations/> .
ns0:DeliveryChargeSpecification
owl:disjointWith ns0:PaymentChargeSpecification .
ns0:PaymentChargeSpecification
metadata_def:mappingLoom "paymentchargespecification" ;
metadata_def:mappingSameURI ns0:PaymentChargeSpecification ;
metadata_def:prefLabel "Payment charge specification" ;
metadata:prefixIRI "gr:PaymentChargeSpecification" ;
a owl:Class ;
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 ns1:v1 ;
rdfs:label "Payment charge specification"@en ;
rdfs:subClassOf ns0:PriceSpecification ;
owl:disjointWith ns0:UnitPriceSpecification .
ns0:appliesToPaymentMethod
rdfs:domain ns0:PaymentChargeSpecification .