Bytes not infosets
Security is the one area where the WS-* world has developed a set of standards that provide significantly more functionality than has so far been standardized in the REST world. I don't believe that this is an inherent limitation of REST; I'm convinced there's an opportunity to standardize better security for the REST world. So I've been giving quite a lot of thought to the issue of what the REST
XML and JSON
I've had some useful feedback on my previous post. I need to take a few days to get clearer in my own mind what exactly it is that I'm trying to achieve and find a crisper way to describe it. In the meantime, I would like to offer a few thoughts about XML and JSON. My previous post came off much too dismissive of JSON. I actually think that JSON does have real value. Some people focus on the abili
Do we need a new kind of schema language?
What's the problem? I see the real pain-point for distributed computing at the moment as not the messaging framework but the handling of the payload. A successful distributed computing platform needs a payload formata way to express a contract that a payload must meeta way to process a payload that may conform to one or more contractsthat is suitable for average, relatively low-skill programmers,
derivativeアルゴリズムについて(1) - ものがたり(旧)
冬休みに入ってからしばらくはRELAX NGまわりをいじり直していた。まず長いこと懸念していたバグ潰しがようやく実行に移せた。そして直ったと思ったら、今度はパフォーマンスに（relaxng.rngを解析できないほどの）致命的な問題が生じて、最適化をいくつか実装する必要があった。結論から言えばwhitespaceの扱いがおかしかっただけなのだけど。そして今日、ようやく3年前にやっつけたwhitespaceまわりの問題を全て解消した（はず）。 僕の知る限り、現時点でバグの原因は3種類だけだ: 1) XLink section 5.4の制約が未実装であること、2) XML Schema datatypesのfacetが上手く機能していない（場合がある?）こと、3) exceptを子にもつname classをexceptにもつname classのanalysisに失敗すること。 というわけで、
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
OSDIR
Integrity without confidentiality
