Modelling relation between Agent and Location
On that, Im just wondering though, why does Agent have primaryLocation? What if an Agent has multiple locations? Could it be one-to-many?
I imagine there will be a need for multiple locations for an agent. In fact, wouldn't it really be a many-to-many? There also I expect will be a need to have more information on the relationship to qualify it. We haven't spent much time on that, partly hoping to piggy back on TransforMap or others who have agents related to locations as part of their core.
One thing we did talk about was changing the name vf:Location to vf:Place (assuming it is vf:). Should we do that?
Paul, let's minimally do what you need; and if we want to really nail it down now, I'd be willing to do some research on standard models for agent - location relationships. And see if @almereyda can help us out with at least the requirements from his side, understanding it has been hard to standardize on the actual model.
Continuing the tangent on vf:Location, which probably deserves its own thread:
Agents may have a primary personal physical mailing address, where they receive physical mail (less important than it used to be). That may or may not be their residential address, and their residential address may or may not be one of the main centers (or regions) of their activity.
Agents also may have one or more physical offices, often (but not always) associated with specific roles/positions they have in a network or organization,
Ultimately, I think that physical addresses (and any sub-types) need to be distinguished from any other locations or (preferably IMO) regions/areas which an agent desires to list for their general or specific activities.