In the 55th joint meeting of the CIDOC CRM and SO/TC46/SC4/WG9; 48th FRBR/LRMoo SIG meeting, the SIG decided to start a new issue where to discuss some unresolved comments on the Scope note writing guidelines (see table of comments). These comments will be discussed independently in the current issue (topics it involves are: substance/identity/unity criteria for defining classes, examples of scope notes that follow the guideline <or improving the existing scope-notes>).
HW for MD, CEO, WS, TV and RS
Belval, December 2022
In the 60th joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 53rd FRBR/LRMoo SIG, WS volunteered to revisit the comments left on the guidelines for writing scope notes and report back to the SIG
Bern, April 2025
In the 61st joint meeting of the CIDOC CRM and ISO/TC46/SC4/WG9 & 54th FRBR/LRMoo SIG, the group resolved to adopt the proposal by WS and close issue 629, on the grounds that the points raised in the issue (see here) form either marginal points, or need to be discussed in separate issues.
On his part, noted that he would prefer to start editing the CRM where it doesn’t conform to the guidelines than continue commenting on the guidelines. And he agrees that the SIG should try to ensure that new scope notes do conform to guidelines.
Since at least GB & DO seemed eager to work towards creating a couple of use cases of scope notes annotated for substance/identity/… criteria (also including fixed expressions used to reference each criterion in the scope notes), with links to easily accessible examples, they can discuss this among themselves and WS, set a time frame for this work, and start the designated issues on the listserv.
For the details of the proposal and points raised at the meeting, see here.
Issue closed
Heraklion, October 2025