tibonto / aeon

The Academic Event Ontology (AEON) can be used to represent information regarding academic events.
https://tibonto.github.io/aeon/
Creative Commons Attribution 4.0 International
14 stars 4 forks source link

remove unecessary subobjects annotations #30

Closed andrecastro0o closed 4 years ago

andrecastro0o commented 4 years ago

@StroemPhi

I noticed that there were a few subobject annotations, when they are not need. In essence in SMW we use subobject if we need:

To assign more than 1 value to the same property, in 1 page, we do not need subobjects.

At the moment I see no need for the subobjects:

    Subobject AdditionalProcessName (BFO 0000015)
    Subobject Relation (event)
    Subobject Deadline
    Subobject Contributor
    Subobject Committee
   Subobject Sponsor
  Subobject AdditionalProcessName

But correct me if I wrong.

If you agree with this, keep the issue open, and don't clean anything yet. I will add more properties where subobject is not required, as I implement it in MW

https://github.com/tibonto/aeon/blob/f8ddc03977aa088e40d826b89eb9113b8adc2640/aeon.ttl#L530

StroemPhi commented 4 years ago

@andrecastro0o I agree and will wait until you give me the go to get rif of them.

StroemPhi commented 4 years ago

Although the sponsor subobject is aeon:has_sponsor && aeon:sponsor_type.

andrecastro0o commented 4 years ago

oh, but Sponsor_type does not have domain:BFO 0000015 so how can i nfer that it should be within the BFO 0000015/Process template? https://www.confident-conference.org/r/vanilla/Property:Sponsor_type https://www.confident-conference.org/r/vanilla/Help:All_Properties#Domain:BFO_0000015_.28Process.29

andrecastro0o commented 4 years ago

updated issue with

Although I understand the logic, which is the the has committee member properties, because they are such a small number of properties, it is ok to leave them in the form, outside a subobject. See https://www.confident-conference.org/r/vanilla/Special:FormEdit/Event/Test