Issue 398: Scope note of E62 String
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