Issue 240: New "encoding" property for E90 Symbolic Object

Starting Date: 
Working Group: 
Closing Date: 

Posted by Martin, 6/02/2014 

Dear All, 

I wonder if E90 Symbolic Object should have a property "encoding" or "employed symbol set". I think of various old and modern scripts and digital encodings. Think of Japanese texts in Romaji, Kanji-Katakana, or Katakana only, Turkish in Arabic or Latin scripts, ancient Egyptian in Hieroglyphic or Hieratic, etc. 

One could think of using just "has type", but may be reference to explicit symbol sets or multiple symbol sets is not adequate for a E55 Type? Anyway, in FRBRoo the issue appeared as a question of identity of the symbolic object itself: 

Properties*:*R33 <#_R33_has_content>has content: E62 <#_E62_String>String 

(R33.1 has encoding: E55 <#_E55_Type_>Type)

Current Proposal: 

In 31st joined meeting of the CIDOC CRM SIG, ISO/TC46/SC4/WG9 and the 24th FRBR - CIDOC CRM, resolving this issue, the sig decided to define a property P166 of E90 that allows to specify which interpretation of the symbols in an E90 provide identity to the content represented by some carrier or content encoding, not only an E62, such as “latin alphabet and punctuation symbols” “words of the English language”. Also it is needed to be defined a Symbolset and to expand scope note of E90 to define “content representation” , a sort of “representative Item”. Christian Emil will elaborate this issue.


Heraklion, Crete, October 2014


In the 42nd joined meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9 and the 35th FRBR - CIDOC CRM Harmonization meeting, the crm-sig decided to close this issue since it is the same with 395. It is agreed that P2 “has type” is sufficient to capture the different kinds of encoding. 

The issue is closed

Berlin, November 2018

Reference to Issues:

Meetings discussed: