usage examples of client level data conforming to human services ontologies

We've been using Apache Marmotta behind an authentication gateway to store
RDF conforming to human services ontologies.

Read more at:
https://github.com/hserv/entity-tracking/wiki/How-to-Use-Linked-Data-Platform-APIs-(LDP)-in-Apache-Marmotta

Right now, the main application for this in HSLynk is for storing random
bits of information we haven't implemented with a traditional schema
and convenience
APIs <http://docs.hslynk.com>.  This includes tags, case management,
service codes, etc..   However, I can see a future, where these rigid
schemas go away in favor of self-describing RDF and ontologies.  We've
already seen this happen with FHIR in health care, where an ontology
controls the semantics, and the database (as implemented by open source
HAPI FHIR servers) simply is a bag of resources conforming to that
ontology definition (accessible via https://www.hl7.org/fhir/rdf.html).
Why can't all human services work the same way?  The portability of the
data would be greatly enhanced, and thereby the ability to help people.
Convenience APIs can still exist as well, but waiting for them to be
specified is not critical.


Eric Jahn
CTO/Data Architect
Alexandria Consulting LLC
St. Petersburg, Florida
727.537.9474
alexandriaconsulting.com