- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 19 Jan 2015 13:38:11 -0500
- To: public-webpayments@w3.org
- Message-ID: <54BD4F13.4000501@openlinksw.com>
On 1/19/15 3:47 AM, Anders Rundgren wrote: > On 2015-01-18 22:37, Kingsley Idehen wrote: >> On 1/18/15 6:00 AM, Anders Rundgren wrote: >>> On 2015-01-17 23:57, Kingsley Idehen wrote: >>>> On 1/17/15 12:44 PM, Anders Rundgren wrote: >>>>> > <snip> > > >> W3C isn't supposed to be producing prospective standardization specs. It >> is supposed to be producing specs that standardize what exists. > > And in the context of web payments that means...? I don't know, and therein lies the big problem, from my vantage point. Prescribing standards is dead-on-arrival. Standardizing what's in use, so that implementation details are uniform and preserved forever (e.g., Internet RFCs from IETF) . Getting this right is critical. Getting is wrong is tragic, as exemplified by RDF. What is RDF, actually? A retrospective standardization of entity relations representation. By that I mean, from the onset the notion of entity relations has been part of HTML (via <link/> and HTTP (via "Link:"), but none of this factors into conventional RDF narratives. Instead, RDF was promoted using a poor narrative that was all about RDF/XML (specifically) as THE standard data representation notation and across-the-wire serialization format. Even as a write, document content notations and across-the-wire serialization format specificity related squabbles continue to obscure what RDF is actually all about :( > > Anders > > > -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog 1: http://kidehen.blogspot.com Personal Weblog 2: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen Personal WebID: http://kingsley.idehen.net/dataspace/person/kidehen#this
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 19 January 2015 18:38:33 UTC