You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As is mentioned in #90 JSON is an important interfacing format to support. We already make the Message object JSON-serializable for interfacing with any other languages. It will be better to have general JSON support in form of a platform.
JSON-LD looks a promising direction.
The text was updated successfully, but these errors were encountered:
HTML + RDFa: machine readable linked data. e.g. for search engines.
JSON: common interfacing format. Problem is that there is no common agreement of the meaning of attributes. We find this especially true with the experience in developing SNSAPI.
JSON-LD: use @context to make the meaning of fields unambiguous. Other specifiers: @id, @type, ...
The idea of JSON-LD is self-descriptive. @context can be put in the JSON file or in a separate .jsonld file. Current examples extensively refers to http://schema.org/ . e.g. ReplyAction. The definition looks too detailed and overwhelming to new users. We may want to maintain a snsapi-message context
As is mentioned in #90 JSON is an important interfacing format to support. We already make the
Message
object JSON-serializable for interfacing with any other languages. It will be better to have general JSON support in form of a platform.JSON-LD looks a promising direction.
The text was updated successfully, but these errors were encountered: