Service user as an Agent?

This is an issue that came from a discussion between Geert Thijs and myself.

CPSV describes "uses" as follows:

The uses property links an Agent to a Public Service in which it plays the specific role of user, meaning that it provides the input and receives the output but does not play any direct role in providing the service. This will typically be an individual citizen or an outside organisation.

This caused for some confusion on my and Geert Thijs' side because PublicService describes the offering of the service rather than specific cases. I concluded that the "uses" relation was meant to keep track of who had made use of a service, as a very low detail way of keeping track of users. Further investigation led me to the use case of making a service catalog, now my current interpretation is that this attribute is meant to specify the target group for the service.

I envisioned a case where a service aimed at elderly people would have a "seniorCitizen" instance of a foaf:Person to indicate this, which I believed to barely fit in the description of foaf:Person, where they explicitely state it can deal with imaginary people. Geert countered this argument by saying that you are describing a category of Persons, which is very different from Person itself. He argues that this attribute should make use of a Code rather than an Agent.

An idea I had later was that foaf:Group could be used instead of foaf:Person to indicate the target group, but this still seems more complicated than using a codelist.

I believe this demonstrates that the "uses" relation deserves some additional clarification, even in the "v2.0 final draft", section 3.2.15,  hardly any explanation is present:

Service User [0..n]

This property links a Public Service to an Agent who uses the service.

Component

Category