Resource (Class), ResourceType (Class) and particular resource (instance)
In this comment I rashly claimed that "among people who have worked with this set of concepts a lot, there is general agreement." By that I mean the distinctions that REA makes between ResourceType and Resource as an instance of a ResourceType (although they will usually have different names for that same distinction).
Documenting some evidence for that claim: http://www.productontology.org/#faq http://www.heppnetz.de/ontologies/goodrelations/v1.html#Individual http://dip.semanticweb.org/documents/hepp-truecomplexity-ECIS2006.pdf
Excerpt:
3.3 Scope of Product Properties When part of a product description, assertions assign properties to products. Such properties can be (1) valid for every make and model that falls into a specific product category, (2) vendor- or modelspecific, or (3) characteristics of single product instances. In other words, the scope of a property must be observed, because this determines where and how respective statements shall be stored and how frequently the statements need to be updated. For example, model-specific properties will be assigned in a vendor-specific product model ontology, while properties of product categories will rather be part of the TBox part of a domain ontology. Additionally, some product properties may be dynamic, others may be static. Properties of Product Categories: Prominent content standards like eCl@ss and ETIM provide attributes that help describe product properties. This allows parametric search, i.e. searching for a product that meets a set of property constraints (e.g. class=TV set with screen size < 11 inches and color=true). Properties of Product Models: In this category of properties fall most of the product attributes that popular content standards (e.g. eCl@ss and the eOTD) offer for the description of products. Typical examples are weight, diameter, color, dimensions, etc. Both eCl@ss and the eOTD contain a relation between product classes and such attributes. The eOTD link table between classes (EGIS) and attributes (EGAS) is just a rather inconsistent recommendation (Hepp 2003), while the respective “attribute lists” in eCl@ss are well-defined sets of attributes with industry-wide consensus. Properties of Product Instances: Some properties are valid only for a single instance of a specific product, e.g. the sales location of a specific car, the expiry date of a perishable food, a serial number, or, for a used car, the previous owner. Those properties can also be important for reasoning about alternative offers. For example, a reliable company instead of an unknown individual as the previous owner of a used car might fit to our preferences better, and whether a food product that will expire soon (but is available at a reduced price) is a good deal depends on the actual situation. Multi-dependent Properties: Leukel et al. have already pointed out that there