Re: Web Payments Architecture Summary?

Hmm... or publish right away to help reduce confusion for new people and
update as needed if we find problems.  Since the process is light-weight
updating should be as simple as merging a PR - right?

On Tue, Jul 5, 2016 at 3:17 PM, Adrian Hope-Bailie <adrian@hopebailie.com>
wrote:

> +1 to publish via light-weight process but with a caveat that if we
> publish a document that is the "entry-point" for the WG's work we shouldn't
> take this lightly and need to give it due diligence before we publish.
>
> On 5 July 2016 at 14:49, Telford-Reed, Nick <
> Nick.Telford-Reed@worldpay.com> wrote:
>
>> Manu
>>
>> I think there is a lot of value in this doc as an explainer. I'd be +1 to
>> there being a place for this to be read and maintained.
>>
>> I'm happy to consider this for the agenda slot on Day 2 as you suggest
>> and we can talk more about this in the administrivia sessions on either day.
>>
>> Thanks
>> Nick
>>
>> --
>> Nick Telford-Reed
>> e: nick.telford-reed@worldpay.com | m: +447799473854 | t: +44 203 664
>> 5069
>>
>> > -----Original Message-----
>> > From: Manu Sporny [mailto:msporny@digitalbazaar.com]
>> > Sent: 05 July 2016 14:30
>> > To: Web Payments WG <public-payments-wg@w3.org>
>> > Subject: Re: Web Payments Architecture Summary?
>> >
>> > On 07/04/2016 11:32 PM, Michael[tm] Smith wrote:
>> > > There are lots of other ways to publicize a document like this without
>> > > needing to initiate the (relatively heavyweight) WD publication
>> > > process just to make it widely available for readers.
>> >
>> > Let me rephrase, then:
>> >
>> > I'd like us to publish this document as soon as possible at a
>> long-lived URL in
>> > W3C space and make it an entry point into our other specs. I was
>> guessing
>> > that the vehicle would be an FPWD for a NOTE (I thought FPWD wasn't
>> > specific to REC-track stuff).
>> >
>> > For example, if the WG decides to publish it as a NOTE that we will
>> update
>> > from time to time, without a great deal of process involved to update
>> the
>> > document, that would meet all of the requirements AFAICT.
>> >
>> > +1 for doing this in the most lightweight (but meaningful) way possible.
>> >
>> > -- manu
>> >
>> > --
>> > Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
>> > Founder/CEO - Digital Bazaar, Inc.
>> > JSON-LD Best Practice: Context Caching
>> > https://manu.sporny.org/2016/json-ld-context-caching/
>>
>> This e-mail and any attachments are confidential, intended only for the
>> addressee and may be privileged. If you have received this e-mail in error,
>> please notify the sender immediately and delete it. Any content that does
>> not relate to the business of Worldpay is personal to the sender and not
>> authorised or endorsed by Worldpay. Worldpay does not accept responsibility
>> for viruses or any loss or damage arising from transmission or access.
>>
>> Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority
>> No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct
>> Authority No: 504504), Worldpay AP Limited (Company No: 05593466 /
>> Financial Conduct Authority No: 502597). Registered Office: The Walbrook
>> Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial
>> Conduct Authority under the Payment Service Regulations 2009 for the
>> provision of payment services. Worldpay (UK) Limited is authorised and
>> regulated by the Financial Conduct Authority for consumer credit
>> activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam,
>> the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence
>> from and is included in the register kept by De Nederlandsche Bank, which
>> registration can be consulted through www.dnb.nl. Worldpay, the logo and
>> any associated brand names are trade marks of the Worldpay group.
>>
>
>


-- 
Shane McCarron
Projects Manager, Spec-Ops