• Facets (new session)
• Description
• Metadata
• Settings
  • Rule: ActivityStreamsMapasEquivalentb3sb3sifpfacetshttp://www.w3.org/2002/07/owl#ldpoffers ontologyoplwebrel-me-authschema-oloskos-transurn:det:rdf:labelurn:rdfs:subclass:subproperty:inference:rulesvirtrdf-eturtle-containersvirtrdf-hashtagvirtrdf-ifpvirtrdf-labelvirtrdf-meta-entity-classvirtrdf-urlNone
    
  • Inverse Functional Properties: Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects
  • "Same As": Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects (recommended) Apply to subjects, objects and predicates (not recommended on big datasets) Apply to predicates only (special use cases only)

About: Payment charge specification     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : owl:Class, within Data Space : www.openlinksw.com associated with source document(s)

New Facet based on Instances of this Class

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.