So, the point seems to be whether the attribute identifiers should be opaque or not. I am not so sure where the example like OpenSocial or OpenGraph or Poco are using opaque identifier. In my example, an OpenSocial API Call like: GET /rest/people/34KJDCSKJN2HHF0DW20394/@self?fields=name,gender&format=xml HTTP/1.1 HOST api.example.org Authorization: hh5s93j4hdidpola can be trivially converted to GET /rest/people/34KJDCSKJN2HHF0DW20394/@self?fields=name%23ja_Hani_JP,gender&format=xml HTTP/1.1 HOST api.example.org Authorization: hh5s93j4hdidpola for Japanese Kanji name instead of (probably) English name. Same kind of procedures can be applied to OpenGraph, OpenID AX, etc. Are you suggesting that we need to fix those protocols instead? Well, true. It may be a quick hack, but it seems to be somewhat more realistic than fixing all those protocols. (2010/07/06 22:08), Scott Cantor wrote:
Why would it be a disaster? Could you elaborate more?
You're turning an opaque identifier into a semantic key that eventually will get overloaded to handle whatever kinds of variability people come up with. This happens in databases all the time, and it leads to maintenance problems.
Your solution also doesn't work with existing standards for the representation of attributes, which include the use of opaque URNs to identify attributes that have unambigious names.
The problem here is the protocol, so that's where the solution needs to be. Your protocol needs to be fixed to handle the extensibility you need in negotiating information release.
-- Scott
-- Nat Sakimura (n-sakimura@nri.co.jp) Nomura Research Institute, Ltd. Tel:+81-3-6274-1412 Fax:+81-3-6274-1547 本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ございませんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。 PLEASE READ: The information contained in this e-mail is confidential and intended for the named recipient(s) only. If you are not an intended recipient of this e-mail, you are hereby notified that any review, dissemination, distribution or duplication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete your copy from your system.