Skip to main content

User account menu

  • Log in
Home
CIDOC CRM

Cidoc Horizontal Menu

  • Home
    • About & Info
    • Use & Learn
    • Issues
    • Mappings
    • Compatible Models
    • Use Cases
    • Best Practices
  • Activities
  • Resources
  • Community
  • News

Issues

  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG archive

Choose a shortcut

Compatible models & Collaborations
Link to old CIDOC CRM website
Next meeting
Use cases
CIDOC CRM Tutorial
CIDOC CRM Website designs and logos 
CRM SIG mailing list
Editorial Suggestions
Site Support

 

Content of Symbolic Object

207
2011-11-14
1 - Editorial changes
Done
2011-11-20

On 14/11/2011 in 24th CIDOC SIG meeting and the 18th FRBR -CIDOC CRM Harmonization meeting, discussing about FRSAD Nomen F35 Nomen Use statement and F12 Nomen, it is decided that any instance/subclass of Nomen should foresee a content string that completely represents the identity of a Nomen instance regardless of the semantics of the structural components it is built from and a nomen identity may not extend to the interpretation of equivalence of structural components. The occurrence of structural tags in the nomen string is regarded as part of the content symbols.
Finally we came to the conclusion that 

(1) we need to define a content model taking into account the syntax, type, serialization. Also we noticed that this property should have as property Rxx.1 encoding: E55 Type and 

(2) we need to open a CIDOC CRM Issue about the content of the symbolic object and to add a note about the content to the scope note of P3.

Martin Doerr will formulate the second decision above.

Heraklion, Crete, 3/05/2012

Posted by Martin Doerr 13/11/2012 
Dear All, 

I suggest to add to the scope note of E90 Symbolic Object the following text: 

In some cases, the content of an instance of E90 Symbolic Object may completely be represented by a serialized digital content model, such as a sequence of ASCII-encoded characters, an XML or HTML document, or a TIFF image. The property P3 has note allows for the description of this content model. In order to disambiguate which symbolic level is the carrier of the meaning, the property P3.1 has type can be used to specify the encoding (e.g. "bit", "Latin character", RGB pixel).

The CRM SIG accepted the proposal. 
Amersfoort 20/11/2012

THE MODEL

  • About & Info
  • Short Intro
  • Scope
  • Recommendations
  • References
  • Critics
  • Important Theories
  • Use&Learn
  • Short Intro
  • User Guidance
  • Methodology
  • Tutorials
  • Functional Overview
  • Last Official Release
  • Concept Search
  • Issues
  • Short Intro
  • Issue Formulation
  • Issue Processing
  • CRM SIG Archive
  • Mappings
  • Short Intro
  • Mapping Methods
  • Mapping Tools
  • Mapping Memory
  • Reports about Mappings
  • Compatible Models
  • Short Intro
  • Models
  • Use Cases
  • Short Intro
  • Use Cases

RESOURCES

  • Related Activities
  • Versions
  • References
  • Presentations
  • Technical Papers
  • Tutorials
  • Critics
  • Important Theories
  • Publications
  • Mappings
  • Compatible Models
  • Translations
  • Best Practices
  • Meeting Contributions
  • Minutes
  • Issues
  • CRM SIG Archive
  • Meeting Contributions

ACTIVITIES

  • Short Intro
  • SIG Meetings
  • Minutes
  • Workshops
  • Related Activities

PEOPLE

  • Short Intro
  • Related Stakeholders
  • SIG Members
  • Hosts

NEWS

HOME

 

 

Copyright © 2025 Company Name - All rights reserved

Developed & Designed by Alaa Haddad