> As you know we do/try not to add classes to the model unless it forms an
> anchor for some properties or is structurally necessary.
> So what are the new properties that justify the proposed new sub-class?

Pxx_has_found:
  domain: Exx Discovery
  range: E77 Persistent Item
  subprop of: P12i_was_present_at
Pyy_found:
  domain: Exx Discovery
  range: E39 Actor
  subprop of: P14_carried_out_by 

In case you object that one could simply use P12i and P14, 
please note that exactly the same pattern is used e.g. for the four 
class-specific subprops of P1: P78, P87, P102, P131

> The alternative is just to type an instance of E7 Activity.

CRM does not (and I guess never will) standardize P2_has_type values.
I think it's appropriate to standardize this concept that is important in the 
domain addressed by CRM (archaeology) and for FR search.

Best regards! V

Reply via email to