Update README.md

update covering the new example
minor additions in comment fields
some additions as bulleted ideas
This is an experimental CV version that uses BFO 2.0 as top level ontology instead of BiotopLight.

I still like to expresses my doubts on a potential switch to BFO, as
* BFO is a Top level ontology and does not provide an intuitive bio upper level, making the semantic gap between the re-binned classes quite large at times. The only way to circumvent this is the import of an intermediate bio layer from e.g. OBI and others.
* BFO classes are not intuitive to our users ( e.g. dependent continuant, or the distinctions fiat object to object to object aggregate). The geek factor is too high and the gap to the PSI CV design principles will be enlarged even more.
* BFO and OBI complex setup, e.g. reliance on external scripts and dependency on further artefacts like IAO, OBI to be usable.
* The geek factor of BFO together with IAO and OBI is quite high and this is exactly what CVs don't need. These are Description logics focused and lack ergonomy to serve as communication channel. The overhead of constructs, that we are not requiring for our scope, is quite high.

Please all look at this version and compare to the nmrCV under (btl2) in terms of intelligibility to a biologist.

Here the single changes I made while re-binning under BFO2.0:
BFO 2.0 (Graz version) is  imported from http://www.ifomis.org/bfo/ (outdated?)
Some required re-binning ...
btl2:information object subclasses were moved under bfo:generically dependent continuant
or import IAO to close gap (is there a version for BFO2.0?)?
software moved from btl2:plan to bfo:realizable entity. (Obi or IAO needed to close gap?)
data transformation moved from btl2:plan execution to bfo:process
chemical compound and instrument were put under bfo:object aggregate (do we expect that our users will be able to distinguish these form objects and fiat objects ?)

all namespace references and an orphan btl2 relation (is bearer of) were deleted from this file.
some rewordings, formattings and additions
Improve pynmrML readme
Reorganize
Add var2nmrML bin
Fix adding annotation example
Add more data
Minimal metadata additions were made. elsewise I copied the content of the previous nmrCV_BFO.owl into this nmrCV.owl to retain file and log history. nmrCV_BFO.owl was deleted. The log file of this is the same:

* This is an experimental CV version that uses BFO 2.0 as top level ontology instead of BiotopLight.

I still like to expresses my doubts on a potential switch to BFO, as
* BFO is a Top level ontology and does not provide an intuitive bio upper level, making the semantic gap between the re-binned classes quite large at times. The only way to circumvent this is the import of an intermediate bio layer from e.g. OBI and others.
* BFO classes are not intuitive to our users ( e.g. dependent continuant, or the distinctions fiat object to object to object aggregate). The geek factor is too high and the gap to the PSI CV design principles will be enlarged even more.
* BFO and OBI complex setup, e.g. reliance on external scripts and dependency on further artefacts like IAO, OBI to be usable.
* The geek factor of BFO together with IAO and OBI is quite high and this is exactly what CVs don't need. These are Description logics focused and lack ergonomy to serve as communication channel. The overhead of constructs, that we are not requiring for our scope, is quite high.

Please all look at this version and compare to the nmrCV under (btl2) in terms of intelligibility to a biologist.

Here the single changes I made while re-binning under BFO2.0:
BFO 2.0 (Graz version) is  imported from http://www.ifomis.org/bfo/ (outdated?)
Some required re-binning ...
btl2:information object subclasses were moved under bfo:generically dependent continuant
or import IAO to close gap (is there a version for BFO2.0?)?
software moved from btl2:plan to bfo:realizable entity. (Obi or IAO needed to close gap?)
data transformation moved from btl2:plan execution to bfo:process
chemical compound and instrument were put under bfo:object aggregate (do we expect that our users will be able to distinguish these form objects and fiat objects ?)

all namespace references and an orphan btl2 relation (is bearer of) were deleted from this file.
Minor alteration of the following versioning section:
"The nmrCV should be dynamically maintained via the COSMOS nmrML mailing lists (https://groups.google.com/forum/?hl=en#!forum/nmrml/join ) that allows any user to request new terms in agreement with the community involved. Once a consensus is reached among the community the new terms are added within few days. If there is no obvious consensus, the CV coordinators should vote and make a decision. A new nmrCV.owl should then be released by updating the file on the github without changing the name of the file (this would alter the propagation of the file to ontology services that rely on file stable URI). For this reason an internal version number (owl:versionInfo, with two decimals (x.y.z) should be increased:
•	x should be increased when a first level term are renamed added deleted or rearranged in the structure. Such rearrangement is supposed to be rare and is very likely to have repercussion on the mapping.
•	y should be increased when any other term except the first level one is altered.
•	z should be increased when there is no term addition or deletion but just editing on the definitions or other minor changes.
"
responed to some comments
added cryoprobe and inverse detection NMR probes and added multiple parenthood to 5mm inverse detection cryoprobe
some typos corrected
worked on issues 84 to 89, i.e. chebi compliance and moved parameter subclasses to object aggregate, mainly chemical compounds, solutions, ...
moved all NMR classes from object aggregate to object.
new merged version with the first third done, rest needs to be merged form commented versions....
Merge pull request #80 from LuisFF/master

update in the nmrML example file. Generated with the Java converter.
preparation for another nmRIO FID test case