W3C home > Mailing lists > Public > public-webpayments@w3.org > February 2012

Re: Agenda: Web Payments Telecon - Friday, February 10th, 2012

From: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Mon, 13 Feb 2012 14:08:26 +0100
Message-ID: <CAKaEYhKFYKXYm0ArVha1M9HE100c2_sewyCzQRX8S=MUJ88FFA@mail.gmail.com>
To: opentransact@googlegroups.com
Cc: Web Payments <public-webpayments@w3.org>, Manu Sporny <msporny@digitalbazaar.com>
On 12 February 2012 07:11, David Nicol <davidnicol@gmail.com> wrote:
> On Wed, Feb 8, 2012 at 10:55 PM, David Nicol <davidnicol@gmail.com> wrote:
>> The wire-level format for data transmitted within Payswarm is JSON
>> (Javascript Object Notation.) Invariant key/value pairs and key names have
>> been selected to conform with JSON-LD, and a schema document parseable with
>> JSON-LD tools has been registered with purl.org.
> Melvin Carvalho has proposed that the word meaning "within the context of
> this protocol, these strings are always present, like this, exactly" might
> be changed from "invariant" to either "universal" or "uniform."

On reviewing the normative document on Web Architecture


I think perhaps the best language to use is in section 2.1 "Benefits
of Using URIs" [in this case as keys]

"The choice of syntax for global identifiers is somewhat arbitrary; it
is their global scope that is important."

So what we would like to convey in the sentence is that the keys have
global scope.

The web arch document goes into great detail about the advantages of
this, and how it lead to the WWW.  One immediate advantage I can see
is to make the key terms non colliding between different systems and
another is that they can be (and in this case are) self documenting.

> --
> on the outside of the bottom of the barrel, that's how much of an outlier it
> is.
Received on Monday, 13 February 2012 13:08:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:20 UTC