Source: Mayo Clinic ( Davide Sottara)
The terms may be confusing, and implementers may 'misplace' important pieces of information
'uri' is meant to be an 'individual/instance' URI, that identifies the entity represented by the MVF element
(e.g. an individual Community - mapped by a mvf:Community, or an individual Concept - mapped by a mvf:MVFEntry)
'externalReference', which only applies to MVFEntry, may be better called 'semanticReference', and be exepcted to resolve to a definitional resource such as an ontology (class/expression)
'reference' seems to hold more descriptive/informative links such as web pages or other web resources.
Maybe it could be called 'descriptiveReference' - in contrast with 'semanticReference'?
Reported: MVF 1.0b1 — Fri, 31 Mar 2023 18:42 GMT
Disposition: Resolved — MVF 1.0
Rename properties as proposed
Rename MVFEntry::externalReference to semanticReference
Rename MVFElement::reference to descriptiveReference
Update the metamodel and ontology diagrams and document text referencing these names, as given below in Revised Text.
Updated: Mon, 2 Oct 2023 12:57 GMT
- MVF Entry Class Diagram.png 95 kB (image/png)
- MVF Entry Class Diagram.svg 864 kB (image/svg+xml)
- MVF-enhanced.xmi 70 kB ()
- MVF-mvf.xmi 36 kB ()
- MVF.mdxml 362 kB ()
- MVF.mdzip 83 kB ()
- MVF.xmi 43 kB ()
- MultipleVocabularyFacility.rdf 21 kB (application/rdf+xml)
- class__MVF__MVF.png 120 kB (image/png)
- class__MVF__MVF.svg 1.25 MB (image/svg+xml)