I agree. Here are some other options for Intent resource-related properties: name, image, imageList, note (sort of a duplicate of the as:content above but could have a detailed discription of the resource), resourceClassifiedAs. Offers/requests are the loosest and least understood as regards identifying resources. Some mutual aid kinds of apps just have a description and that’s it. I also do think an image would be good.
To at least partially clarify resourceConformsTo and resourceClassifiedAs, the first refers to the lowest level resource type needed to completely identify the resource in the use case, which might be more like “Schwinn bicycle model xyz123 blue” (or not). Using wikidata is misleading, which is our fault, as we use that as shorthand in VF examples. resourceConformsTo points to ResourceSpecification, which is actually defined within VF, so might not even be a uri. Wikidata could be more appropriate for resourceClassifiedAs, which for offers/requests could use an agreed upon taxonomy or set of categories for matching/search, or just tags, pretty loose depending on the app, and can be multiple. But still, it depends on the use case, and we don’t have a good understanding yet of the formality that people will want to coordinate their resource specifications (resourceConformsTo) across networks or the public, even just limited to marketplace type apps.