Update README.md

Readme for v1.0

README.md

@@ -1,5 +1,50 @@
 # EBUCorePlus
 
+<p >
+EBUCorePlus is an ontology for media enterprises, developed as an open source project. It follows-up on two long-standing EBU ontologies: EBUCore and CCDM (Class Conceptual Data Model). The two were merged and thoroughly revisioned. The result is EBUCorePlus, the new standard that can fully replace its predecessors. It inherits both the long-lasting reliability of EBUCore and the end-to-end coverage of the media value chain of CCDM. 
+</p>
+<p >
+EBUCorePlus is strictly semantic. It avoids ambiguities that were introduced when using EBUCore and CCDM classes in one graph. It has its own, new name space therefore it is not backward compatible, but can be mapped to its predecessors. It provides complete documentation of all entities in English, French and German (English being normative).
+</p>
+<img width="1440" alt="EBUCore_plus-Overview-Review-2023-03-16" src="https://user-images.githubusercontent.com/32091198/225752320-1ac90d9c-70b4-4b69-b1d9-6e60f47e6b66.png">
 
-![EBUCore_plus-Overview-Review-2023-03-16](https://user-images.githubusercontent.com/32091198/225748467-7b702fbc-b1d6-47b4-9fd6-9f15c093cc88.png)
+</p>
+One major problem of EBUCore and CCDM was the use of ranges: semantically similar object properties needed to be defined in parallel for each class that the property referred to. Another case was the use of multi-range properties, leading to insufficient type safety. EBUCorePlus now uses class restrictions instead, leading to less and more coherent properties. 
+</p>
+<p >
+EBUCorePlus aims to serve as a plug and play framework. It can be used out of the box, either in its entirety or just a subset of its elements. But it may also be adapted and extended to enterprise-specific needs. It is not required to adopt the ontology completely. The benefit from using EBUCorePlus arises from combining well-defined modelling proposals with your use case specific decisions. Especially for system integration tasks and defining requirements, projects benefit from EBUCorePlus as a business – not technology – oriented language. 
+</p>
+<p >
+The ontology is developed by the EBU Metadata Modelling Working Group as an open source project on github. Requests for changes and improvements can be submitted by EBU Members, media organizations or anybody else from the media community. The EBUCorePlus Editorial Committee reviews requests and implements changes. 
+</p>
+<p >
+The EBU Metadata Modelling Working Group provides access, upon request, to a cloud hosted demonstration kit to explore and better understand the whole EBUCorePlus model.
+</p>
+
+## How we use annotation properties for definition, examples and description
+
+Starting with dcterms:description
+The preceding ontologies EBUCore and CCDM annotated their entities with the property dcterms:description. The Literals were filled with descriptive text, mostly explaining, what the entity’s intended use was:
+isBrand: dcterms:description = “To identify a brand”
+Or they reused the term itself to be described:
+Person: dcterms:description = “A Person”
+
+## Applying guidelines
+While the dcterms:descriptions are useful in many circumstances, they seemed insufficient to us. We wanted to achieve the best possible precision and common understanding for EBUCorePlus entities. So, we applied the “Guidelines for writing definition in ontologies” (https://philpapers.org/archive/SEPGFW.pdf), a great paper by Seppälä, Ruttenberg and Smith.
+
+## Using skos:definition and skos:examples
+SKOS provides the annotation properties skos:definition and skos:example that match our intended use perfectly. The Literals in these annotations are created according to the guidelines of the paper. E.g. 
+Person: skos:definition = “an individual Agent”
+In this case it is stated that “Person” is a sub-class of “Agent” and representing an indivisible human being.
+
+The Literals in skos:example list representatives that are most common, but sometimes also most rare, in order to enlighten the borders of the defintion’s scope:
+Person: skos:example = “	- Alfred Hitchcock (director)
+- James Bond (character)
+- Sean Connery (actor)
+- John Ford (pseudonym used by the director John Martin Feeney)” 
+
+## Examining annotations
+We consider skos:definition to provide the normative text for defintions and skos:example as a way to simplify understanding of the definitions, because sometimes the definitions are very formal. However, we have not yet equipped all entities with skos:definitions yet and we understand that dcterms:descriptions are covering almost all entities and therefore are still helpful, even if they might be unprecise, outdated or even wrong (e.g because the meaning of an entity has changed from EBUCore to EBUCorePlus). So, when examining the annotations, be aware that skos:definition is normative but may be lacking and dcterms:description is complete but to be interpreted carefully.
+Translations to French and German
+EBUCorePlus aims to provide full documentation in 3 languages: English, French and German. We hope to lower the barriers for non-native English speakers. To accomplish this in due time, we made heavy use of automatic translations from English to French and German. Be aware, that automatic translation is varying in quality. But so are many English texts in EBUCore and CCDM, because they were created by non-native speakers. The EBU working group is editing and improving the Literals in EBUCorePlus step by step.