Page History

Discussion Points: 

• This discussion is a follow-on to the addition of property qualifiers feature we added to LexEVS.

• Proposed changes will require substantial changes. No changes to the queries.
• JSON-LD was noted - it represents triples in JSON.
• It is unsure how much OWL needs to be presented in LexEVS.
• Consider removal of anonymous nodes.
• Complex Classes need to be addressed somehow - LexEVS or not.
• LexEVS should not continue extending field sizes to accommodate these complex classes.
• Suggested that the EVS API should not define a model specific to OWL.
• Current CTS2 service doesn't provide this type of search.
• There is an existing issue for OBIB that would be addressed by proposed representation.

  • Jira
    server NCI Tracker serverId 7954a81f-12da-3366-a0ef-97c806660e7c key LEXEVS-3613

• Maps, value sets, MetaT representation, are in LexEVS that cannot be represented easily in triple store.
• Micro services should be considered for providing services to provide OWL content (micro service using the triple store)
  • LexEVS API model would need to be updated to support this.

Decision Points:

• Complex Classes need to be addressed somehow - LexEVS or not.
• Micro services should be considered for providing services to provide OWL content (micro service using the triple store)