Dear Maximilian,
I had been a bit shorthand.
I referred to a knowledge graph theoretically, as CRM instance, without
a quad feature, or looking at it as being a Named Graph. Of course
current systems have these features built in.
The reason being, that only separating the Graph from the data
Dear Martin,
My "recommendation" was just putting into question an aspect of
Florian's suggestion, and not meant to replace it in a final way.
Regarding your points: The practical cases I am familiar with would use
the E13 on the whole triple, i.e. the link/property-type including a
specific
Dear Maximilian,
This makes sense to me, but I do not agree with your recommendation as a
general rule.
There is a fundamental epistemological problem, which has nothing to do
with quantitative evidence. The latter,
by the way, cannot detect an endless recursion anyhow, because people
would
ng team are therefore not neutral to the validity
of the assertion.
All best,
Florian
From: Crm-sig on behalf of Martin Doerr
Date: Friday, March 16, 2018 at 1:05 PM
To: crm-sig
Subject: Re: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
Here the old scope note:
E13 Attribu
he assertion.
All best,
Florian
From: Crm-sig on behalf of Martin Doerr
Date: Friday, March 16, 2018 at 1:05 PM
To: crm-sig
Subject: Re: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
Here the old scope note:
E13 Attribute Assignment
Subclass of: E7 Activity
Superc
dicate
>> that we are aware of it and to allow people to find it even when they search
>> based on outdated knowledge. We as the maintaining team are therefore not
>> neutral to the validity of the assertion.
>>
>> All best,
>>
>> Florian
>>
>
rian
From: Crm-sig on behalf of Martin Doerr
Date: Friday, March 16, 2018 at 1:05 PM
To: crm-sig
Subject: Re: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
Here the old scope note:
E13 Attribute Assignment
Subclass of: E7 Activity
Superclass of: E14 Condition Asses
05 PM
> To: crm-sig
> Subject: Re: [Crm-sig] ISSUE: E13 Attribute Assignment
>
> Dear All,
>
> Here the old scope note:
> E13 Attribute Assignment
> Subclass of: E7 Activity
> Superclass of: E14 Condition Assessment
> E15 Identifier Assignment
> E
PM
*To: *crm-sig
*Subject: *Re: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
Here the old scope note:
E13 Attribute Assignment
Subclass of: E7 <#_E7_Activity> Activity
Superclass of: E14 <#_E14_Condition_Assessment> Condition Assessment
E15 <#_E15_Identi
;
P140_assigned_attribute_to _:production_of_painting .
Asserting that the production of the painting activity was carried out by
Rembrandt.
Rob
From: Crm-sig on behalf of Martin Doerr
Date: Friday, March 16, 2018 at 1:05 PM
To: crm-sig
Subject: Re: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
Here the old scope note:
E13 Attribute Assignment
Subclass of: E7 <#_E7_Activity> Activity
Superclass of: E14 <#_E14_Condition_Assessment> Condition Assessment
E15 <#_E15_Identifier_Assignment> Identifier Assignment
E16 <#_E16_Measurement> Measurement
E17 <#_E17_Type_Assignm
ype in E13.
Best,
Martin
Thanks!
Rob
*From: *Crm-sig on behalf of Martin
Doerr
*Date: *Tuesday, February 13, 2018 at 2:48 AM
*To: *crm-sig
*Subject: *[Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
The scope note of E13 must be updated:
A) the property type it refers to should be
Doerr
Date: Tuesday, February 13, 2018 at 2:48 AM
To: crm-sig
Subject: [Crm-sig] ISSUE: E13 Attribute Assignment
Dear All,
The scope note of E13 must be updated:
A) the property type it refers to should be described by P2 has type of the E13
instance. Then it is
isomorphic with an RDF
Dear All,
The scope note of E13 must be updated:
A) the property type it refers to should be described by P2 has type of
the E13 instance. Then it is
isomorphic with an RDF reification statement.
B) The epistemology should be described more precisely: It describes
that the maintainers of th
14 matches
Mail list logo
