Page History

CTS2 1.1 JSON.png

...

• Entities returned in JSON moving from lower to upper case top level element
  • returned under an “entityDirectory” in CTS2 1.0 
  • as an “EntityDirectory” in CTS2 1.1.

JSON associated with the CTS2 1.0 implementation in LexEVS 6.1

 (Not an official specification)

Image Added

CTS2 1.1 JSON 

Implemented in LexEVS 6.2

Image Added

CTS2 Model Changes

While there is an extensive list of model changes, few will affect end users.  We've listed one change that some REST interface users will see and followed up with a link to the complete change reference.

• Any URIAndEntityName references should all be changed to EntitySynopsis
• Link to complete model change reference 

Summary

...

A mapping of changes a REST interface user is likely to come across. 

 

CTS2 1.0	CTS2 1.1
entityDirectory	EntityDirectory
entryList	entry
knownEntityDescriptionList	knownEntityDescription
iteratableResolvedValueSet	IteratableResolvedValueSet
URIAndEntityName	EntitySynopsis

A Summary of  Objects Mapped To LexEVS

This gives some context for the LexEVS user who wants to take advantage of the REST api over LexEVS and gives a sense of what the current object set is that might be returned by a rest call.  (And parsed from XML or JSON into Java objects)

A Summary of CTS2 Objects