Commerce & PaySwarm Vocabulary suggestions

Dear W3 Web Payments members,

I'm Hendy from Bippo Indonesia <http://www.bippo.co.id>. I'd like to
suggest a few things to Commerce & PaySwarm vocabularies:

1. range: Enumeration instead of Resource

e.g.

> 5.18 rateType
> The rate type property is used to specify whether the rate property of a
> Payee is a fixed amount, an inclusive percentage or an exclusive
> percentage. The rateType coupled with the currency, and rate specifies the
> exact monetary amount or calculation that must be employed during the final
> cost calculation among a list of Payees.
> Status
> unstable
> Attribute of
> Thing
> <http://schema.org/Thing>Typically used by
> Payee
> <https://w3id.org/commerce#Payee>Associated value must be a
> Resource
> <http://www.w3.org/2000/01/rdf-schema#Resource>Typical values are
> Cumulative <https://w3id.org/commerce#InclusivePercentage>, Deferred
> <https://w3id.org/commerce#ExclusivePercentage>, Tax
> <https://w3id.org/commerce#FlatAmount>

I would propose that associated value (property's range) is a RateType,
which is subclass of schema.org/Enumeration which lists the allowable
values.
i.e. similar to how http://schema.org/ItemAvailability works.

2. description instead of comment

e.g. in Payee there is comment. To align with Schema.org (
http://schema.org/description), "description" is better used, "comment"
tends to conflate with "comment from user" (http://schema.org/comment). I
understand there is rdfs:comment but in my personal opinion description
better describes this property's purpose.

Hendy


Hendy Irawan - on Twitter <http://twitter.com/hendybippo> - on LinkedIn
<http://id.linkedin.com/in/hendyirawan>
Web Developer | Bippo Indonesia <http://www.bippo.co.id/> | Akselerator
Bisnis | Bandung