Issue 198: Change Scope note and Example of E32

ID: 
198
Starting Date: 
2011-05-17
Working Group: 
3
Status: 
Done
Closing Date: 
2011-11-17
Background: 

Issue 1 in FRBRoo: In joined crm-sig, frbr-sig harmonization meeting in Crete May 2011, the FRSAD entities Thema, Nomen and the relationship has appellation/is appellation of with CRM, we wondered about generalizing the authority document definition in CRM and include the FRSAD Scheme or any KOS, the harmonizing group decided two actions. 

Action: New scope note proposal for E32, based on KOS (c.e.s by end of July) 

Action: Change range of P71 to E1 CRM Entity. (see CRM issue 182)
 


Posted by Christial Emil Ore on 10/11/2011

The scope-note of E32 to be extended to cover KOS. The term KOS,Knowledge Organizing Systems is very wide. KOS is the system or method for organizing information and not the information itself. Thus KOS and SKOS are instances of E29 design or procedure. The content of a database using SKOS is an instance of E31 Document and may bbe an instance of E32 Authority Document. Thus instances of KOS need not necessarily be confined to E32. We may use E31. Since the issue was to extend E32, I give a draft scope note below. It should however, be discussed if the E31 should be used instead.

New scope note:

E32 Authority Document
Subclass of: E31 Document

Scope note: This class comprises encyclopaedia, thesauri, authority lists, documents and instances of knowledge organizing systems that define terminology or conceptual systems for consistent use.

Examples: 
- Webster's Dictionary 
- Getty Art and Architecture Thesaurus
- the CIDOC Conceptual Reference Model 
- the GeoNames geographical database

Properties:
P71 lists (is listed in): E1 CRM Entity 
 


Posted by Joao Oliveira Lima on 10/11/2011 

Dear Christian-Emil, 

My first suggestion is to replace: 
"thesauri, authority lists, documents and instances of knowledge organizing systems that define terminology or conceptual systems for consistent use." 
by 
"thesauri, authority lists, instances of knowledge organizing systems and documents that define terminology or conceptual systems for consistent use." 

Justification: 
It seem that the expression "that define terminology or conceptual systems for consistent use" was a restriction specific to the "document" scope because the others elements ( encyclopaedia, thesauri, authority lists and also KOS ), by definition, are linked with the terminology or conceptual system idea. 

The second suggestion is to replace the term "encyclopaedia" by "encyclopedia". 
Justification: 
According Google Books Ngram Viewer (link below), since the 1900s, the use of the term "encyclopedia" is more common than "encyclopaedia". 
http://books.google.com/ngrams/graph?content=encyclopaedia%2Cencyclopedia&year_start=1800&year_end=2000&corpus=0&smoothing=3 
or 
http://bit.ly/sNa2RR

Current Proposal: 

E32 Authority Document
Subclass of: E31 Document

Scope note: This class comprises encyclopaedia, thesauri, authority lists, documents and instances of knowledge organizing systems that define terminology or conceptual systems for consistent use.

Examples: 
- Webster's Dictionary 
- Getty Art and Architecture Thesaurus
- the CIDOC Conceptual Reference Model 
- the GeoNames geographical database

Properties:
P71 lists (is listed in): E1 CRM Entity

Outcome: 

The CRM-SIG decided to leave the scope note and the example as it is since KOS in the narrower sense has been defined in FRBRoo

CRM-SIG, Amsterdam, 17-11-2011