We are designing best practices for using OAGIS components in a REST based API

We had an excellent Mobile, Cloud, and JSON Working Group meeting last week.  We were discussing using OAGIS in the JSON format using REST-based processing.  Some of our members are already doing this and they are sharing their experiences with the Working Group.

We are looking at using the 4 regular verbs for REST processing GET, PUT, DELETE, and POST.  We are thinking we may need to augment them with some of the existing OAGIS Verbs also, but that decision has not been made.

We have also declared that the highest form of content will be the OAGIS Noun and the lowest could be even at the Element level.  The componentization of the OAGIS architecture really lays a strong foundation for this new use of OAGIS.

Remember it is the content that is important and the more ways we can use the content the more useful the common data model will be of users of OAGIS.