Consider a contact mechanism for Agent

[azaroth42]

This could be metadata, if we want to have multiple ways with labels in different languages to be seen by humans but less likely to be processed by machines:

"metadata": [
  {"label": {"en": ["Contact Us"]}, 
"value": {"en": ["feedback@example.org"]}}
]

Or a specific property, such as contact which we would need to define exactly what the value and processing model would be. It could be a URL, allowing either a mailto: or https: URL to be given, but the client would be responsible for rendering/using it:

"contact": "mailto:feedback@example.org"

(From Tom, Rob re Patrick Cuba's suggestion)

[azaroth42]

After lunch discussion, some considerations:

• If the manifest or other resource is re-aggregated, the contact information might still be right, but it could also easily be wrong depending on the reason for getting in touch
• metadata might mean that there's arbitrary amounts of information to be presented, which might make viewer UI harder for Agent, whereas a contact can't have specific labels (and thus shouldn't be repeatable) but doesn't provide an open bucket for arbitrary stuff.