Meeting 2017 04 19

Minutes

Participants:

• Mirko Jalava
• Martin Alvarez
• Andy Robinson
• Andy Weir

Charter

No changes in charter so we will continue with the work.

Discussion about the document on Github

• Martin: I’ve been creating examples and use cases for entities to check its completeness. You can see one athlete modelled there.
• Andy: My main worries are about the complexity of the new model. We would need to have a simpler version of JSON schema to give organisers. Easier to implement.
• … [Mentioned the example of vertical jumps, that are officially represented in centimetres]
• … Why we don’t represent this just a pair (e.g., “height" : “205”)?
• Martin: Main differences are the ’nesting’ of concepts. This is important to create the final vocabulary or schema because we will need to define classes about concepts (Person, Event, etc.) and properties (relations among instances of entities). Some of the already declared properties are taken from schema.org. The same example of height would be defined as a QuantitativeValue to be compatible with the existing implementations (‘height’: {value:’205’, ‘unit’:’CMT’}).
• … This is important for interoperability
• Andy: Proposal: Creating a reduced version of a JSON schema that could be used to simplify the model for our purposes. This will be subsequently mapped with the final vocabulary.
• Martin: Good idea. Your tools could implement following a simpler version, the only requirement is that the final published information adopts the vocabulary we will produce.
• … Now we have to check if both models are too different. And why?
• … I’ll continue developing examples and use cases comparing with your existing model.

About URIs and IDs

• Andy: Sometimes we have multiple ids. For instance, Estonian IDs and Opentrack IDs have different values.
• Martin: We can declare more than one but in order to have a unique URI identifying concrete things we need to choose just one.
• Andy: Should we create URI schemes as recommendations to help people to create their own URLs.
• … I’ll have this for competitions, athletes, events.
• Andy: Experts in countries will be able to help us creating the IDs and using these ID on the patterns.
• Martin: OK. This is another thing we can produce in the group. This could be published as a reference.

Naming athletes

• Mirko: We need more 'alternate names’, sometimes is important having them in other languages. Athletes in Spain and Portugal have two surnames.
• Martin: Linked Data, (we will create examples, at least in JSON-LD) will give us the possibility of having multilingual descriptions directly. So multilingual names are in the model.
• Mirko: Fields for surnames is important. Also alternative names.
• Martin: The current model supports multiple alternative names, we can define as many as we need.
• Andy: We need to have a list of previous names (e.g. before the Married Name).
• Martin: Is it important? Just for searching but if we have unique identifiers for athletes we can identify these records.
• Mirko: Sometimes we found results confusing. For instance, officials control the official name but in the passport, they have the married name. A proposal: adding a new property different that ‘alternate name’.

Roles of persons

• Andy: A Person could have different roles.
• Martin: A person is the parent of Athletes so we can add different roles such as Coach, Official.

Next meeting

• None responded the doodle. In the meantime, next Wednesday same hour. Wed 26 Apr, 08:00-09:00 GMT.