R3 semantics phone call
Present: Michael, John, Maurice, Karen
will distribute minutes of mtg. DONE
will develop draft list of Ontology resource attributes, based off MMI
ORR. Post off CIAD APP Resource
confluence page. Target: 12/21
will develop draft list of Attribute resource attributes (say that 3
times fast), based off existing Filemaker content. Post off CIAD APP Resource
. Target: 12/21
Karen and John
will initiate draft list of Assoc
iation resource attributes.
will develop a list of existing resource attributes to expose in the ION
will provide information on the inferencing engine and related tools
used by MMI ORR. Target: ??
will add content to the “Semantic page on arch” (Question:
?). Based on notes from today, plus perhaps diagram
and further detail. Target: LCO
s 2 and 3 together will complete Karen’s Jira task 627.
use them in services
represent them in UI
Will add 3 new resource types to describe semantic assets:
MMI ORR provides an initial set of
attributes for consideration
can be a pointer to information in external repository, or internal
representation (e.g. RDF or similar)
needs to define attribute’s meaning, and/or also the
Initial content will be derived f
rom the fields in the current Attribute
the attribute concept may be supported by an ontology
the allowable content for an attribute may also be supported by an
ontology (So CV could be an attribute “type”)
both of the above are concepts
needs to define meaning,
as well as constraints (one to one, one to
look at existing systems for models (sim to RDF,e.g.)
System functions related to semantics
i.e. pull back all “temp
erature” records even if have different param
similar to above
the system gives the user a set of alternatives. I.e. do you want
to drill down/limit by certain types of items. Needs knowledge that items
participate in same ca
tegory. Comes out of ontologies and inference, but can
also be authored. R2 resources such as Catalog and View not implemented
this way yet, but structured in this direction.
low level function that helps search/nav to work
e.g. for importing external data that has a different known
vocabulary into our terminology. Or unit conversion. Transform of resources
based on ontology. Implicit or explicit.
e.g. presenting our metadata in standard formats such as
O. Can be relabeling names, or converting units, etc.
identification of versioning (at uri/concept level)
inspiration is MMI. Latest
version, current version, history, etc. Must be able to go back to identity of
that concept at the time applied. Not c
lear how back end would support this
current resource framework does not hold history.
versioning applies to the definition level, and the content level, of a
resource. Is it imp to know prior values of the resource? Def need to
know prior definition of
the definition. (Could push versioning into
the ontology representation world…but…)
Will need to create an “ION Resource Ontology” based on our attribute terms.
And later may decide to map this to external ontologies. This can be
extracted from the YML attributes and associations and converted to OWL.
will identify the first set
of terms to expose, based on how user
they are (at present will focus on most user
We will want to perform inferences, and cache them for faster access. But
that cache is likely not a first class resource.
Linked data: there are
considerations regarding how far OOI wants to go
with respect to exposing content via Linked Data.
Parameters: consider parallels. Parameters are like attributes. Parameter def
is like attribute def. Parameter dict is similar to object type.
May need t
an inference engine.
probably not a repository
would do as interface.
May need analytic store (i.e. to store an external ontology).
May also consider a semantically
enabled data store (BigData?...tools
exist that may help).
Note that one
existing tech may serve all 3 needs
MMI has a solution;
will provide further info.