improve 'name' data property

[StroemPhi]

At the moment names of events, series, organizations and people are all lumped together under the aeon:'name' data property. This needs to be cleaned up.

We need to have a way of describing that

1. an event or event series

   2. must have an official name, which may be in multiple languages
   3. often has an acronym
   4. can have one or more alternative names
   5. sometimes can have a former name (e.g. when two series merged into one)

2. names of organizations an people should not be defined in AEON. But we need to reuse them in order to properly describe the contributors (organizer, maintainer, speaker etc). Just having a PID would fall short of the fact that there are contributors who do not yet have a PID

[StroemPhi]

The current design decision is to have the class aeon:'planned process name' as a subclass of iao:identifier, similar to pno:'personal name', with the restriction that it is equivalent to identifier and (denotes only 'planned process').

This way we are able to have instances of academic event or series names with which we can express the fact that events and series are sometimes called differently on different plattforms.

The data property aeon:'planned process acronym', defined as a subproperty of iao:'has representation' restricted to the domain of planned process and the range of xsd:string, can be used to provide the acronym of an academic event or series.

As can be seen from the example individuals for the VIVO 2020 conference and its series, preferred and alternative names can be provided by annotating the corresponding planned process name instance using skos:prefLabel and skos:altLabel. For translated event or series names it seems best to use skos:altLabel with the respective language tag.