Function calls can be made.

[kekyo]

Actually, I mean any instance call that implements a unified interface. In the background, support for a plugin system like functionality that acts on behalf of the oEmbed API calls.

• What to do with the syntax?
  • ex: {oEmbed https://api.example.com/foo/bar/baz}
  • Is one argument sufficient? If more than one argument is needed, it affects the syntax. It may be better to consider a syntax that can handle multiple arguments from the beginning.
• The format of the interface.
• Asynchronous (performance related)
• Concurrent callability (performance related)

The current syntax separates keyword names and parameters with :, example {date:yyMMdd}. This follows the .NET formatting string, but given the above, spaces are preferable. NET dwellers can accept the use of parentheses, commas, etc., but the general public may find the formatting strange and cumbersome, so we prefer to avoid it.