Hi @krishnan

Hi @krishnan

Thank you for the help. I am revisiting your sample schema.

I understand the first part, and I rewrote it to the below working query.

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

it works pretty well.

So with this, for any attribute XXX, I just need to attach a relation called attributed-XXX and then I can define the attribution. Very neat.

I am also wondering, should

attributed-ipo-date

attributed-ipo-date

uses

relate

relate

for ipo-date, so that when ipo-date attribute got deleted/changed, this relation

attributed-ipo-date

attributed-ipo-date

can be deleted as well? I want the attribution go away with the referenced ipo-date attribute and referenced entity instance go away.

============

But I don't understand the second example. I kept getting error with the second approach in your comment.

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

Can I have a full, working implementation of the second approach? I am not sure if I understand this.

Hi @krishnan

Hi @krishnan

Thank you for the help. I am revisiting your sample schema.

I understand the first part, and I rewrote it to the below working query.

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

define attribute ipo-date, value datetime;
relation attributed-ownership @abstract, relates source;
entity data-source plays attributed-ownership:source;
relation attributed-ipo-date sub attributed-ownership, owns ipo-date;

it works pretty well.

So with this, for any attribute XXX, I just need to attach a relation called attributed-XXX and then I can define the attribution. Very neat.

I am also wondering, should

attributed-ipo-date

attributed-ipo-date

uses

relate

relate

for ipo-date, so that when ipo-date attribute got deleted/changed, this relation

attributed-ipo-date

attributed-ipo-date

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

define AttributedOwnership owns AttributedValue;
attribute AttributedDateValue  @abstract, sub AttributedValue , value date;

relation AttributedDateOwnership @abstract, sub AttributedOwnership, owns AttributedDateValue as value;
relation AttributedIPODate sub AttributedDateOwnership;

Can I have a full, working implementation of the second approach? I am not sure if I understand this.

Hi @krishnan

Hi @krishnan

Similar Threads

Similar Threads

Similar Threads