But the object does not "refer to" the scriptwriter. In fact the link to the script writer is purely in the documentation of the object. This is the same as rendering a person as a scriptwriter or architect. They were not born as scriptwriters or archtitects it was a role they played in particular event(s).
Stephen Stead Tel +44 20 8668 3075 Mob +44 7802 755 013 E-mail [email protected] LinkedIn Profile http://uk.linkedin.com/in/steads -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Vladimir Alexiev Sent: 09 July 2012 15:25 To: 'crm-sig' Subject: Re: [Crm-sig] ISSUE: P62 needs a parent and a sibling > I think the simple answer is we saw P62 used in actual data models. > We have not seen the others and so had no justification for creating them. Are the examples provided sufficient justification? > The example of the drawing of an actress having further details in > unstructured data would need to have a series of intermediary nodes > introduced to complete the path to the script writer from the drawing... > FRBRoo events (for instance the F27 Work Conception... The structured BM data (table Associated Person) says the physical object is somehow related to the script writer (who comes from a thesaurus). We cannot create a precise path involving FRBRoo because the relation is explaned in a mere note. > There is no conceivable shortcut that could provide a link directly. Sure there is: P67a_refers_to that's just like P67 but has physical domain. We're currently doing: <obj> P62_depicts <thes/people/Some-Actress>; P128_carries <obj/concept>. <obj/concept> P67_refers_to <thes/people/Some-Script-Writer>. We'd like to get rid of the parasitic (empty) node <obj/concept> and just do this: <obj> P62_depicts <thes/people/Some-Actress>; P67a_refers_to <thes/people/Some-Script-Writer>. _______________________________________________ Crm-sig mailing list [email protected] http://lists.ics.forth.gr/mailman/listinfo/crm-sig
