compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
I don't believe any of the problems reported on that page are fixed by BM

To cater to these inconsistencies, the FRs loop by (P9,P10,skos:broader)* which means:
{info}
If present at an event, a thing is considered to also be present at:
- sub-events (P9)
- super-periods (P10)

But as you see, the hierarchy is navigated *up and down*, which violates principles of covariance.
{warning:title=If someone does the CRM property}
If a data provider uses P9_consists_of (instead of skos:broader) to connect Periods, the following false inference will result:
- GAA42731 was present at Ancient Egypt, therefore it was present at all sub-period thereof, eg 26th Dynasty
{warning}

{section}
{column}
In 2 above we have asked the production sub-events to be directly connected to the object:.
Then we'd navigate upward and the P9 link is never used:
!FR12_was_present_at_data1.png!
Then we'd navigate upward and the P9 link is never used
{column}
{column}