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

 

Scope note of E62 String

398
2018-11-07
3 - Changes in the CIDOC CRM model
Done
2018-11-28

Posted by Martin on 7/11/2018


Continuing issue 363,

I propose the following:

Current:

E62 String

Subclass of:         E59 Primitive Value

 

Scope Note:        This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.

 

E62 String is not further elaborated upon within the model

Examples:          

§  the Quick Brown Fox Jumps Over the Lazy Dog

§  6F 6E 54 79 70 31 0D 9E

 New scope note:

"This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces different from that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date, but different strings."

Posted by Richard Light on 8/11/2018

On 07/11/2018 17:47, Martin Doerr wrote:
>
> Current:
>
> E62 String
>
> Subclass of:         E59 Primitive Value
>
> 
>
> Scope Note:        This class comprises the instances of E59 Primitive Values used for documentation such as free text strings, bitmaps, vector graphics, etc.
>
> 
>
> E62 String is not further elaborated upon within the model
>
> Examples:         
>
> §  the Quick Brown Fox Jumps Over the Lazy Dog
>
> §  6F 6E 54 79 70 31 0D 9E
>
>  New scope note:
>
> "This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces different from that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date, but different strings."

I would suggest:

"... but consist of different strings."

Otherwise, good!

posted by Martin on 8/11/2018

OK, I improve:

"This class comprises coherent sequences of binary-encoded symbols. They correspond to the content of an instance of E90 Symbolic object. Instances of E62 String represent only the symbol sequence itself. They may or may not contain a language code. In contrast, instances of other subclasses of E59 Primitive value represent entities in mathematical spaces different from that of symbol sequences, by using binary-encoded symbols, such as date expressions or numbers in decimal encoding. For instance, different syntactic forms of a date expression may represent the same date, but consist of different strings."

Question: A language code can be regarded either as a kind of classification going beyond the pure symbol sequence, or actually as a part of the determination of the symbols themselves. It appears practical to allow for rdf:langString, but are there other kinds of classifications, that one may not want to exclude?

In the 42nd joined meeting of the CIDOC CRM SIG and ISO/TC46/SC4/WG9 and the 35th FRBR - CIDOC CRM Harmonization meeting, MD’s attempt at a new scope note for E62 string was accepted by the crm-sig. The issue is closed.

Berlin, November 2018

 

363   Form and persistence of RDF identifiers

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