Re: [Crm-sig] Issue 407: Ordinal Property for E55 Type

[Martin Doerr]

On 6/11/2019 7:15 PM, Simon Spero wrote:
On Tue, Jun 11, 2019, 11:21 AM Martin Doerr > wrote:


Detail: from a maths point of view, partial ordering may be
allowed for: I.e.: not all value pairs can  be compared with
respect to the order relation. This happens in spaces with more
than one dimension, but does not affect transitivity. Any math
freak here to confirm?;-)


A partial order defined by < is transitive, irreflexive, and 
asymmetric (≤ is transitive, reflexive, and antisymmetric).


Also, there can be total orders on multi-dimensional spaces - e.g. 
museums ordered by distance from Bloomsbury, and partial orders on a 
single dimension - e.g. (proper) part-of on physical objects.


Simon


Some questions:

What about "If a ≤ b {\displaystyle a\leq b} a\leq b and b ≤ a 
{\displaystyle b\leq a} {\displaystyle b\leq a} then a = b 
{\displaystyle a=b} a=b;" if there are two museums at the same distance 
from Bloomsbury?


Why should "part-of" be one-dimensional? Do you have details?

Best,

Martin


--

 Dr. Martin Doerr

 Honorary Head of the
 Center for Cultural Informatics

 Information Systems Laboratory
 Institute of Computer Science
 Foundation for Research and Technology - Hellas (FORTH)

 N.Plastira 100, Vassilika Vouton,
 GR70013 Heraklion,Crete,Greece

 Vox:+30(2810)391625
 Email: mar...@ics.forth.gr
 Web-site: http://www.ics.forth.gr/isl

Re: [Crm-sig] Issue 407: Ordinal Property for E55 Type

[Simon Spero]

On Tue, Jun 11, 2019, 11:21 AM Martin Doerr  wrote:

Detail: from a maths point of view, partial ordering may be allowed for:
> I.e.: not all value pairs can  be compared with respect to the order
> relation. This happens in spaces with more than one dimension, but does not
> affect transitivity. Any math freak here to confirm?;-)
>

A partial order defined by < is transitive, irreflexive, and asymmetric (≤
is transitive, reflexive, and antisymmetric).

Also, there can be total orders on  multi-dimensional spaces - e.g. museums
ordered by distance from Bloomsbury, and partial orders on a single
dimension - e.g. (proper) part-of on physical objects.

Simon

>

[Crm-sig] HW: More CLP scope notes

[Martin Doerr]

Dear All,

Here more proposed scope notes for the redefined CLP properties:


*CLP43 **defines dimension (is defined for):*

Domain: F3 <#_F3_Manifestation_Product> Manifestation

Range: E54 <#_E54_Dimension_> Dimension

Quantification:  (1,n:1,1)

Scope note:   This property associates an instance of F3 
Manifestation with an instance of E54 Dimension characterizing aspects 
of the symbolic content, such as word counts, or of the physical form 
foreseen for the exemplars carrying this F3 Manifestation, such as 
number of pages. In case the F3 Manifestation is an abstraction of a 
singleton item, the property may describe dimensions of the actual 
physical form the F3 Manifestation is abstracted from. This logical 
inference is an induction along the path that can be modelled as: F3 
Manifestation R7i has example F5 Item P2 has type: E55 Type.


It can happen that a given exemplar, or subset of exemplars, originally 
produced, or intended to be produced, with that characteristic, 
accidentally lacks it. This fact should be recorded as a property of F5 
Item, and not of F3 Manifestation.


Examples: The publication entitled ‘Functional Requirements 
for Bibliographic Records: final report’, published by K. G. Saur in 
1998, identified by ISBN ‘3-598-11382-X’ (F3) CLP43 defines dimension 
height (E54): P90 has value ‘24’ (E60) and P91 has unit ‘cm’ (E58)


The jigsaw puzzle entitled ‘Map of the New York city subway system’, 
designed by Stephen J. Voorhies and released around 1954 by the Union 
Dimes Savings Bank (F3) CLP43 defines dimension length and height (E54) 
P3 has note ‘46 x 29 cm’ (E62)



*CLP46 **defines material part (defines part for)*

Domain: F3 <#_F3_Manifestation_Product> Manifestation

Range: F3 <#_F3_Manifestation_Product> Manifestation

Quantification:  (0,n:0,n)

Scope note:   This property associates an instance of F3 
Manifestation which prescribes that all its physical exemplars will 
contain as separatable parts an exemplar of the associated instance of 
F3 Manifestation. In case the F3 Manifestation is intended to be used 
and distributed in digital form, the property should describe the form 
in which a physical copy can be obtained. In case the F3 Manifestation 
is an abstraction of a singleton item, the property describes the actual 
physical form the F3 Manifestation is abstracted from. This logical 
inference is an induction along the path that can be modelled as: F3 
Manifestation R7i has example F5 Item P2 has type: E55 Type.


Examples: The publication product identified by ISBN 
‘0618260587’ and consisting of a 3-volume edition of J.R.R. Tolkien’s 
‘The Lord of the rings’ (F3) CLP46 defines material part the publication 
product identified by ISBN ‘0618260595’ and consisting of an edition of 
J.R.R Tolkien’s ‘The two towers’ (F3)


The publication product issued by Deutsche Grammophon in 1998 and 
consisting of a recording of Richard Wagner’s ‘Der fliegende Holländer’ 
as performed in 1991 by Plácido Domingo, Cheryl Studer et al., and 
conducted by Giuseppe Sinopoli (F3) CLP46 defines material part the 
publication product consisting of printed programme notes and libretto 
with French and English translations (F3)


*CLP57 defines number of parts**
***
Domain: F3 <#_F3_Manifestation_Product> Manifestation Product Type

Range: E60 <#_E60_Number_1> Number

Quantification:  (1,1:0,n)

Scope note:   This property associates an instance of F3 
Manifestation with an instance of E60 Number, which denotes the number 
of physical units all exemplars of that publication should consist of. 
In case the F3 Manifestation is intended to be used and distributed in 
digital form, the property should describe the form in which a physical 
copy can be obtained. In case the F3 Manifestation is an abstraction of 
a singleton item, the property describes the actual physical form the F3 
Manifestation is abstracted from. This logical inference is an induction 
along the path that can be modelled as: F3 Manifestation R7i has example 
F5 Item P2 has type: E55 Type.


Examples: The jigsaw puzzle entitled ‘Map of the New York 
city subway system’, designed by Stephen J. Voorhies and released around 
1954 by the Union Dimes Savings Bank (F3) CLP57 defines number of parts 
76 (E60)


The publication entitled ‘History of costume: in slides, notes, and 
commentaries’ by Jeanne Button, Patricia Quinn Stuart, and Stephen 
Sbarge, released by Slide Presentations (New York) ca. 1975 (F3) CLP57 
should have number of parts 1,491 (E60) [Number of physical units of the 
exemplar held by the Gelman Library of the George Washington University, 
as observed by a cataloguer from the Gelman Library of the George 
Washington University when he/she catalogued that particular exemplar 
and recorded the statement: ‘1,491 slides in 14 slide trays + 6 ring 
binders in cases (30 x 29 cm.)’]


--

 Dr. Martin 

Re: [Crm-sig] Issue 407: Ordinal Property for E55 Type

[Martin Doerr]

I agree.

Detail: from a maths point of view, partial ordering may be allowed for: 
I.e.: not all value pairs can  be compared with respect to the order 
relation. This happens in spaces with more than one dimension, but does 
not affect transitivity. Any math freak here to confirm?;-)


Martin

On 6/11/2019 12:43 PM, Robert Sanderson wrote:


Homework assigned to me to add a notion of concept schemes / context 
to the scope note.  Agreement at Paris SIG that this could go into 
CRMsci and thus “Oxx is conceptually greater than”


Proposed modification to the scope note:

This property allows an instance of E55 Type from a particular concept 
scheme or vocabulary to be declared as having an order relative to 
other instances of E55 Type in the same or other concept schemes, 
without necessarily having a specific value associated with either 
instance.  This allows, for example, for an E55 Type instance 
representing the concept of "good" in a conservation report vocabulary 
to be greater than the E55 Type instance representing the concept of 
"average" in the same vocabulary. This property is transitive, and 
thus if "average" is greater than "poor", then "good" is also greater 
than "poor". In the domain of statistics, types that participate in 
this kind of relationship are called "Ordinal Variables"; as opposed 
to those without order which are called "Nominal Variables". This 
property allows for queries that select based on the relative position 
of participating E55 Types.


Let me know if that does not fulfil the HW assignment ☺

Rob

*From: *Crm-sig  on behalf of Stephen 
Stead 

*Organization: *Paveprime Ltd
*Reply-To: *"ste...@paveprime.com" 
*Date: *Thursday, January 3, 2019 at 6:49 AM
*To: *'crm-sig' 
*Subject: *[Crm-sig] **NEW ISSUE** Ordinal Property for E55 Type

During the discussions at the CRM-SIG meeting during November 2018 in 
Berlin the problem of dealing with instances E55 Type that have 
ordinal relationships with other instances of E55 Type came up. There 
were a number of use cases explored including:-


  * Condition report status values like Excellent, Good, Average,
Poor, Critical where being able to query for all items that were
below “Average” or “Good” and above would be useful.
  * Map scales expressed as types
  * Fire Hazard Ratings

This lead Robert and I to suggest that a new property be created that 
allowed this kind of ordinal relationship to be expressed. The 
quantification allows for parallel hierarchies, e.g. if someone has a 
type that is “slightly better than average but not quite good”, then 
they could align that with an existing hierarchy of Good > Average by 
saying that it is greater than “Average” and that “Good” is greater 
than both it and Average.



  Pxx is conceptually greater than (is conceptually less than)

Domain: E55 Type

Range: E55 Type

Quantification: many to many (0,n:0,n)

This property allows instances of E55 Type to be declared as having an 
order relative to other instances of E55 Type, without necessarily 
having a specific value associated with either instance.  This allows, 
for example, for an E55 Type instance representing the concept of 
"good" to be greater than the E55 Type instance representing the 
concept of "average". This property is transitive, and thus if 
"average" is greater than "poor", then "good" is also greater than 
"poor". In the domain of statistics, types that participate in this 
kind of relationship are called "Ordinal Variables"; as opposed to 
those without order which are called "Nominal Variables". This 
property allows for queries that select based on the relative position 
of participating E55 Types.


Examples:

  * Good (E55)/is conceptually greater than/ Average (E55)

  * Map Scale 1:1 (E55) /is conceptually greater than/ Map Scale 
1:2 (E55)


  * Fire Hazard Rating 4 (E55)/is conceptually greater than/ Fire 
Hazard Rating 3 (E55)


Comments Welcome

SdS & Robert S


___
Crm-sig mailing list
Crm-sig@ics.forth.gr
http://lists.ics.forth.gr/mailman/listinfo/crm-sig



--

 Dr. Martin Doerr

 Honorary Head of the
 Center for Cultural Informatics

 Information Systems Laboratory
 Institute of Computer Science
 Foundation for Research and Technology - Hellas (FORTH)

 N.Plastira 100, Vassilika Vouton,
 GR70013 Heraklion,Crete,Greece

 Vox:+30(2810)391625
 Email: mar...@ics.forth.gr
 Web-site: http://www.ics.forth.gr/isl

Re: [Crm-sig] Issue 397

[Martin Doerr]

Dear Robert,

I may have lost the track. I had published my final version of the 
guidelines before January. A final approval may be pending, but I have 
elaborated in much details these properties. Yes, of course, they have 
to be defined, that was the idea of the deprecation. I thought it was 
accepted already...:-)


See:

"Whereas the CRM regards that intervals of primitive values are 
primitive values by themselves, there is currently no corresponding 
practice in RDF. Therefore, in analogy to the properties of E52 
Time-Span, we define in CRM RDFS two more subproperties of P90 has 
value: “P90a_has_lower_value_limit” and “P90b_has_upper_value_limit”. 
Even if we regard complex matrices of numbers as one value for an 
instance of E54 Dimension, such as RGB images, we can argue that minimal 
and maximal values exist as two separate matrices of the same structure. 
The precise guidelines for using these properties are given in the 
section “Guidelines for using P90a, P90, P90b” below."


"


 *Guidelines for using P90a, P90, P90b*

The CRM recommends to approximate numerical values of Dimensions with 
intervals. The range of the respective property "P90 has value" is 
defined in the CRM as E60 Number. Whereas the CRM regards that intervals 
of primitive values are primitive values by themselves, there is 
currently no corresponding practice in RDF. Therefore, in analogy to the 
properties of E52 Time-Span, we define in CRM RDFS two more 
subproperties of P90 has value: “/P90a_has_lower_value_limit/” and 
“/P90b_has_upper_value_limit/”.


The reasons for recommending this approximation are the following: All 
scientific measurements of non-discrete values are imprecise because of 
the tolerances of the measurement devices, shortcomings in applying the 
procedures and the indeterminacy of the measured effect itself. In 
natural sciences, important results of measurements are associated with 
possibly complex probabilistic distributions for the true value of the 
measured effect.


The most complex case relevant for cultural-historical data are the 
so-called “battleship curves” for calibrated C14 dating data. Many of 
these distribution models actually extend to infinity with non-zero 
probability, which is neither practical nor always justified. In the 
case of C14 however, the actual width of the distribution is often 
underestimated. Nevertheless, even data with a given probabilistic 
uncertainty to infinity are typically associated by scientists with 
narrower “confidence intervals” at one to three “standard deviations”, 
i.e., with a probability of some 68% – 99.7% for the value to be in the 
given range (https://en.wikipedia.org/wiki/Standard_deviation).


Whereas querying globally a very large aggregation of 
cultural-historical data by time intervals is highly relevant, querying 
and reasoning with different approximations of dimensions is normally 
restricted to quite narrow questions. For many cases, a medium value 
without explicit limits is sufficient for the application, such as the 
length of a museum object in millimeters for packaging it in a box. 
Nevertheless, querying explicit representation of actual outer limits or 
at least reasonably wide confidence intervals is computationally highly 
effective, and therefore a good way to ensure recall at query time, 
i.e., that the relevant results are contained in the answer to the 
query, even if it also contains irrelevant ones.


We therefore recommend to use /P90_has_value/ for documenting a medium 
value//or a value without error estimates, when the precision appears to 
be self-evident or irrelevant.


We recommend to use /P90a_has_lower_value_limit /for documenting the 
highest explicit lower limit available for the respective value, even if 
it provides very wide margins. It is an error to omit the lower limit 
even if it appears to be overly pessimistic.


We recommend to use /P90b_has_upper_value_limit /for documenting the 
lowest explicit upper limit available for the respective, even if it 
provides very wide margins. It is an error to omit the upper limit even 
if it appears to be overly pessimistic.


In case of approximating probabilistic distributions, we recommend to 
keep lower and upper limit at two standard deviations or enclosing the 
true value with 95% probability.


/P90a_has_lower_value_limit/ should always be used together with 
/P90b_has_upper_value_limit. /If they are used, the property 
/P90_has_value/ may be used as well or be omitted."



On 6/11/2019 12:56 PM, Robert Sanderson wrote:


Apologies for missing this back in February …

Before the deprecation of P83 and P84 in favor of P191, it was 
possible to say that a TimeSpan had a minimum duration of 2 days and a 
maximum duration of 4 days by using P83 and P84.


Now there is only a single Dimension related via P191, with the intent 
that the value can be an interval.


Given that in the RDF projection of CRM, the value of a Dimension is a 
single number (and 

Re: [Crm-sig] Issue 397

[Robert Sanderson]

Apologies for missing this back in February …

Before the deprecation of P83 and P84 in favor of P191, it was possible to say 
that a TimeSpan had a minimum duration of 2 days and a maximum duration of 4 
days by using P83 and P84.
Now there is only a single Dimension related via P191, with the intent that the 
value can be an interval.

Given that in the RDF projection of CRM, the value of a Dimension is a single 
number (and similarly, the dates are single dates), it is not possible to 
express the above without some additional constructions in that projection.

Thus it seems like we need at least to define P90a_has_minumum_value and 
P90b_has_maximum_value as properties of Dimension to be able to express the 
interval value. This would be more consistent, and provide access to the 
construction for other uses of Dimension, so I’m happy with the deprecation of 
the last SIG … but we need to follow through with the corresponding RDF 
definitions.

I propose the following properties, which could be defined in the same document 
as P81a/b and P82a/b:

P90a_has_minimum_value
This property allows the lowest possible value of an E54 Dimension to be 
approximated by an E60 Number primitive.

P90b_has_maximum_value
This property allows the greatest possible value of an E54 Dimension to be 
approximated by an E60 Number primitive.

Rob

From: Martin Doerr 
Date: Saturday, February 23, 2019 at 4:59 PM
To: Robert Sanderson , crm-sig 
Subject: Re: [Crm-sig] Issue 397

Dear Robert,

On 2/23/2019 1:09 AM, Robert Sanderson wrote:

This becomes problematic, unfortunately, in RDF which does not have a way to 
natively express a Number that is actually an interval.  The resolution would 
be to do the same as P81a/b … which would have the same effect as maintaining 
P83 and P84, just not in the model directly.

While I appreciate the theoretical consistency that this change would add, from 
an implementation perspective, this would bring more complexity than value.

I do not understand what increases the complexity: If I have in RDFS two paths  
P83-E54-P90 AND P83-E54-P90, and the ambiguity how to use P90a, P90b together 
with these paths, OR I have a single path Pxxx-E54 that splits into P90a, P90b, 
then, in the end I have again two paths: Pxxx-E54-P90a AND Pxxx-E54-P90b and no 
ambiguity to use P83 or P90a.

So where is the added complexity? I see it only reduced, but I may be wrong!

My second question was if, since we have bound the Dimension already to 
temporal durations in the definition of Pxxx, we should express that by a 
subclass of E54.

Best,



martin

Overall, I’m not in favor of the deprecation, but am not averse to adding 
had_duration separately, with the potential to deprecate 83 and 84 if a 
holistic approach to date and number intervals can be devised.

Thanks!

Rob

From: Crm-sig 
 on behalf 
of Martin Doerr 
Date: Friday, February 15, 2019 at 9:18 AM
To: crm-sig 
Subject: [Crm-sig] Issue 397


Dear All



As discussed in Berlin, I proposed to deprecate P83, P84, because in competes 
with an interval interpretation of P90, and :

Introduce instead Pxxx had duration, Domain:  E52 Time-Span, Range: E54 
Dimension
and use the P90, P90a, P90b as adequate

or introduce  an Exxx Temporal Duration , subclass of E54 Dimension, and define 
subproperties in RDFS ending in xsd:duration.



Here my definition:



Pxxx had duration (was duration of)

Domain:  E52 Time-Span

Range:E54 Dimension

Quantification:one to one (1,1:1,1)



Scope note: This property describes the length of time covered by an 
E52 Time-Span. It allows an E52 Time-Span to be associated with an E54 
Dimension representing duration (i.e. it’s inner boundary) independent from the 
actual beginning and end. Indeterminacy of the duration value can be expressed 
by assigning a numerical interval to the property P90 has value of E54 
Dimension.



Examples:

§  the time span of the Battle of Issos 333 B.C.E. (E52) had duration Battle of 
Issos minimum duration (E54) has unit (P91) day (E58) has value (P90) (E60)



In First Order Logic:

   Pxxx(x,y) ⊃ E52(x)

   Pxxx(x,y) ⊃ E54(y)



Comments?

--

See:

P83 had at least duration (was minimum duration of)

Domain:  E52 Time-Span

Range:E54 Dimension

Quantification:one to one (1,1:1,1)



Scope note: This property describes the minimum length of time covered 
by an E52 Time-Span.



It allows an E52 Time-Span to be associated with an E54 Dimension representing 
it’s minimum duration (i.e. it’s inner boundary) independent from the actual 
beginning and end.

Examples:

§  the time span of the Battle of Issos 333 B.C.E. (E52) had at least duration 
Battle of Issos minimum 

[Crm-sig] Issue 407: Ordinal Property for E55 Type

[Robert Sanderson]

Homework assigned to me to add a notion of concept schemes / context to the 
scope note.  Agreement at Paris SIG that this could go into CRMsci and thus 
“Oxx is conceptually greater than”

Proposed modification to the scope note:

This property allows an instance of E55 Type from a particular concept scheme 
or vocabulary to be declared as having an order relative to other instances of 
E55 Type in the same or other concept schemes, without necessarily having a 
specific value associated with either instance.  This allows, for example, for 
an E55 Type instance representing the concept of "good" in a conservation 
report vocabulary to be greater than the E55 Type instance representing the 
concept of "average" in the same vocabulary. This property is transitive, and 
thus if "average" is greater than "poor", then "good" is also greater than 
"poor". In the domain of statistics, types that participate in this kind of 
relationship are called "Ordinal Variables"; as opposed to those without order 
which are called "Nominal Variables". This property allows for queries that 
select based on the relative position of participating E55 Types.


Let me know if that does not fulfil the HW assignment ☺

Rob


From: Crm-sig  on behalf of Stephen Stead 

Organization: Paveprime Ltd
Reply-To: "ste...@paveprime.com" 
Date: Thursday, January 3, 2019 at 6:49 AM
To: 'crm-sig' 
Subject: [Crm-sig] **NEW ISSUE** Ordinal Property for E55 Type

During the discussions at the CRM-SIG meeting during November 2018 in Berlin 
the problem of dealing with instances E55 Type that have ordinal relationships 
with other instances of E55 Type came up. There were a number of use cases 
explored including:-

  *   Condition report status values like Excellent, Good, Average, Poor, 
Critical where being able to query for all items that were below “Average” or 
“Good” and above would be useful.
  *   Map scales expressed as types
  *   Fire Hazard Ratings
This lead Robert and I to suggest that a new property be created that allowed 
this kind of ordinal relationship to be expressed. The quantification allows 
for parallel hierarchies, e.g. if someone has a type that is “slightly better 
than average but not quite good”, then they could align that with an existing 
hierarchy of Good > Average by saying that it is greater than “Average” and 
that “Good” is greater than both it and Average.

Pxx is conceptually greater than (is conceptually less than)
Domain: E55 Type
Range: E55 Type
Quantification: many to many (0,n:0,n)

This property allows instances of E55 Type to be declared as having an order 
relative to other instances of E55 Type, without necessarily having a specific 
value associated with either instance.  This allows, for example, for an E55 
Type instance representing the concept of "good" to be greater than the E55 
Type instance representing the concept of "average". This property is 
transitive, and thus if "average" is greater than "poor", then "good" is also 
greater than "poor". In the domain of statistics, types that participate in 
this kind of relationship are called "Ordinal Variables"; as opposed to those 
without order which are called "Nominal Variables". This property allows for 
queries that select based on the relative position of participating E55 Types.

Examples:
  * Good (E55) is conceptually greater than Average (E55)
  * Map Scale 1:1 (E55) is conceptually greater than Map Scale 1:2 (E55)
  * Fire Hazard Rating 4 (E55) is conceptually greater than Fire Hazard Rating 
3 (E55)

Comments Welcome
SdS & Robert S