https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Mlee22W3C Wiki - User contributions [en]2024-03-19T12:31:51ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=Blockchain_CG_member_proposals_and_reports&diff=99873Blockchain CG member proposals and reports2016-09-17T12:57:00Z<p>Mlee22: </p>
<hr />
<div>= Proposals =<br />
* UberLedger framework proposal at 17/Sep/2016 : http://uberledger.io/<br />
* Open Stamps proposal at 15/Sep/2016 : https://petertodd.org/2016/opentimestamps-announcement<br />
* Stampery Blockchain Timestamping Architecture (BTA) proposal at 8/Sep/2016 : https://s3.amazonaws.com/stampery-cdn/docs/Stampery-BTA-v5-whitepaper.pdf<br />
* Weighted Centrality of Blockchain at 22/Aug/2016 : https://docs.google.com/document/d/14TB-ika57VP45cATE8f-SfdEbAGklcZbYoQiyiExN0s/edit?usp=sharing<br />
* Flex Ledger proposal at 7/Aug/2016 : http://web-payments.github.io/flex-ledger/<br />
* BSafe proposal at 28/Jul/2016 : https://docs.google.com/presentation/d/1VU-NTTxHHak_GAsscI5DE9A8YS1QXC2OvFj_lY_1tiM/edit?usp=sharing<br />
* On Scaling Decentralized Blockchains position paper at 9/Jun/2016 : http://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf<br />
* Blockchain Standardization proposal at 19/May/2016 : https://docs.google.com/document/d/1xtfK1C7JbOLx-YztqEDloKBRXWwtFBaLm9pcSwLygAg/edit#heading=h.ie9haz2a79hp<br />
* UseCase proposal at 19/May/2016 : https://docs.google.com/document/d/1JiGV7IUt1PTZg3JvBp9Cr0V7RyosOB_w-z6mMh87ktk/edit?usp=sharing<br />
* Open Contracts proposal at 16/May/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObGtCYzRRSll1T2tBYmo5N0NDZjUzS28yU3Yw/view?usp=sharing<br />
* Open Key Chain Proposal at 12/Apr/2016 : https://github.com/shepelt/openkeychain-spec<br />
<br />
= Shared Infomations =<br />
* W3C Working Group Formation checklist as shared info at 13/Sep/2016 : http://manu.sporny.org/2016/rebalancing/#checklist<br />
* NFTA Proposal for a new field of technical activity at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObnNzc25LbklPM2lGb0Z1X3Z2bmNZaG1yMTVB/view?usp=sharing<br />
* Blockchain & Electronic Distributed Ledger Technologies at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOMmpXXzMwOTZqcmd3S0tlcE0yeFBQdHgxV3c0/view?usp=sharing<br />
* FCC fact sheet at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOXzFZOTJVWldDN01YTTJudE43R25oNXA5bjNn/view?usp=sharing<br />
* Benefits of Standard as shared info at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOQlZzaEhvb2NnbDB4eVFVb1J4SjlDQkJJaUFr/view?usp=sharing<br />
* Blockchain Workshop news link at 7/Jul/2016 : http://www.coindesk.com/w3c-events-industry-begins-long-road-blockchain-standards/<br />
* Graphic Record of Blockchain CG at 1/Jul/2016 : http://prezi.com/wt2ioyhm-spn/?utm_campaign=share&utm_medium=copy&rc=ex0share<br />
* Issue Tracker proposal at 23/Jun/2016 : https://blockchaincg.atlassian.net<br />
* What is Blockchain shared info at 19/Jun/2016 : https://drive.google.com/file/d/0B5927lxY5x0IVTNxVnozcHQtYXc/view<br />
* ISO20022 info shared from Swift at 1/Jun/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOUTB5cEs1QVZrRlE/view?usp=sharing<br />
* Shared Article of HBR at 11/May/2016 : https://hbr.org/2016/05/the-impact-of-the-blockchain-goes-beyond-financial-services?utm_source=twitter&utm_medium=social&utm_campaign=harvardbiz<br />
<br />
= Reports =<br />
* Blockchain Workshop Report at 25/Aug/2016 : https://www.w3.org/2016/04/blockchain-workshop/report.html<br />
* CG's first workshop report at 25/Mar/2016 : https://www.w3.org/community/blockchain/2016/03/23/workshop-details-at-25mar2016/</div>Mlee22https://www.w3.org/wiki/index.php?title=Blockchain_CG_member_proposals_and_reports&diff=99872Blockchain CG member proposals and reports2016-09-17T12:53:50Z<p>Mlee22: </p>
<hr />
<div>* UberLedger framework proposal at 17/Sep/2016 : http://uberledger.io/<br />
* Open Stamps proposal at 15/Sep/2016 : https://petertodd.org/2016/opentimestamps-announcement<br />
* Stampery Blockchain Timestamping Architecture (BTA) proposal at 8/Sep/2016 : https://s3.amazonaws.com/stampery-cdn/docs/Stampery-BTA-v5-whitepaper.pdf<br />
* W3C Working Group Formation checklist as shared info at 13/Sep/2016 : http://manu.sporny.org/2016/rebalancing/#checklist<br />
* NFTA Proposal for a new field of technical activity at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObnNzc25LbklPM2lGb0Z1X3Z2bmNZaG1yMTVB/view?usp=sharing<br />
* Blockchain & Electronic Distributed Ledger Technologies at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOMmpXXzMwOTZqcmd3S0tlcE0yeFBQdHgxV3c0/view?usp=sharing<br />
* FCC fact sheet at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOXzFZOTJVWldDN01YTTJudE43R25oNXA5bjNn/view?usp=sharing<br />
* Benefits of Standard as shared info at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOQlZzaEhvb2NnbDB4eVFVb1J4SjlDQkJJaUFr/view?usp=sharing<br />
* Blockchain Workshop Report at 25/Aug/2016 : https://www.w3.org/2016/04/blockchain-workshop/report.html<br />
* Weighted Centrality of Blockchain at 22/Aug/2016 : https://docs.google.com/document/d/14TB-ika57VP45cATE8f-SfdEbAGklcZbYoQiyiExN0s/edit?usp=sharing<br />
* Flex Ledger proposal at 7/Aug/2016 : http://web-payments.github.io/flex-ledger/<br />
* BSafe proposal at 28/Jul/2016 : https://docs.google.com/presentation/d/1VU-NTTxHHak_GAsscI5DE9A8YS1QXC2OvFj_lY_1tiM/edit?usp=sharing<br />
* Blockchain Workshop news link at 7/Jul/2016 : http://www.coindesk.com/w3c-events-industry-begins-long-road-blockchain-standards/<br />
* Graphic Record of Blockchain CG at 1/Jul/2016 : http://prezi.com/wt2ioyhm-spn/?utm_campaign=share&utm_medium=copy&rc=ex0share<br />
* Issue Tracker proposal at 23/Jun/2016 : https://blockchaincg.atlassian.net<br />
* What is Blockchain shared info at 19/Jun/2016 : https://drive.google.com/file/d/0B5927lxY5x0IVTNxVnozcHQtYXc/view<br />
* On Scaling Decentralized Blockchains position paper at 9/Jun/2016 : http://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf<br />
* ISO20022 info shared from Swift at 1/Jun/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOUTB5cEs1QVZrRlE/view?usp=sharing<br />
* Blockchain Standardization proposal at 19/May/2016 : https://docs.google.com/document/d/1xtfK1C7JbOLx-YztqEDloKBRXWwtFBaLm9pcSwLygAg/edit#heading=h.ie9haz2a79hp<br />
* UseCase proposal at 19/May/2016 : https://docs.google.com/document/d/1JiGV7IUt1PTZg3JvBp9Cr0V7RyosOB_w-z6mMh87ktk/edit?usp=sharing<br />
* Open Contracts proposal at 16/May/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObGtCYzRRSll1T2tBYmo5N0NDZjUzS28yU3Yw/view?usp=sharing<br />
* Shared Article of HBR at 11/May/2016 : https://hbr.org/2016/05/the-impact-of-the-blockchain-goes-beyond-financial-services?utm_source=twitter&utm_medium=social&utm_campaign=harvardbiz<br />
* Open Key Chain Proposal at 12/Apr/2016 : https://github.com/shepelt/openkeychain-spec<br />
* CG's first workshop report at 25/Mar/2016 : https://www.w3.org/community/blockchain/2016/03/23/workshop-details-at-25mar2016/</div>Mlee22https://www.w3.org/wiki/index.php?title=Blockchain_CG_member_proposals_and_reports&diff=99871Blockchain CG member proposals and reports2016-09-17T12:37:46Z<p>Mlee22: Created page with "= Blockchain CG Member proposals and reports = * UberLedger framework proposal at 17/Sep/2016 : http://uberledger.io/ * Open Stamps proposal at 15/Sep/2016 : https://petertodd..."</p>
<hr />
<div>= Blockchain CG Member proposals and reports =<br />
* UberLedger framework proposal at 17/Sep/2016 : http://uberledger.io/<br />
* Open Stamps proposal at 15/Sep/2016 : https://petertodd.org/2016/opentimestamps-announcement<br />
* Stampery Blockchain Timestamping Architecture (BTA) proposal at 8/Sep/2016 : https://s3.amazonaws.com/stampery-cdn/docs/Stampery-BTA-v5-whitepaper.pdf<br />
* W3C Working Group Formation checklist as shared info at 13/Sep/2016 : http://manu.sporny.org/2016/rebalancing/#checklist<br />
* NFTA Proposal for a new field of technical activity at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObnNzc25LbklPM2lGb0Z1X3Z2bmNZaG1yMTVB/view?usp=sharing<br />
* Blockchain & Electronic Distributed Ledger Technologies at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOMmpXXzMwOTZqcmd3S0tlcE0yeFBQdHgxV3c0/view?usp=sharing<br />
* FCC fact sheet at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOXzFZOTJVWldDN01YTTJudE43R25oNXA5bjNn/view?usp=sharing<br />
* Benefits of Standard as shared info at 8/Sep/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOQlZzaEhvb2NnbDB4eVFVb1J4SjlDQkJJaUFr/view?usp=sharing<br />
* Blockchain Workshop Report at 25/Aug/2016 : https://www.w3.org/2016/04/blockchain-workshop/report.html<br />
* Weighted Centrality of Blockchain at 22/Aug/2016 : https://docs.google.com/document/d/14TB-ika57VP45cATE8f-SfdEbAGklcZbYoQiyiExN0s/edit?usp=sharing<br />
* Flex Ledger proposal at 7/Aug/2016 : http://web-payments.github.io/flex-ledger/<br />
* BSafe proposal at 28/Jul/2016 : https://docs.google.com/presentation/d/1VU-NTTxHHak_GAsscI5DE9A8YS1QXC2OvFj_lY_1tiM/edit?usp=sharing<br />
* Blockchain Workshop news link at 7/Jul/2016 : http://www.coindesk.com/w3c-events-industry-begins-long-road-blockchain-standards/<br />
* Graphic Record of Blockchain CG at 1/Jul/2016 : http://prezi.com/wt2ioyhm-spn/?utm_campaign=share&utm_medium=copy&rc=ex0share<br />
* Issue Tracker proposal at 23/Jun/2016 : https://blockchaincg.atlassian.net<br />
* What is Blockchain shared info at 19/Jun/2016 : https://drive.google.com/file/d/0B5927lxY5x0IVTNxVnozcHQtYXc/view<br />
* On Scaling Decentralized Blockchains position paper at 9/Jun/2016 : http://fc16.ifca.ai/bitcoin/papers/CDE+16.pdf<br />
* ISO20022 info shared from Swift at 1/Jun/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwOUTB5cEs1QVZrRlE/view?usp=sharing<br />
* Blockchain Standardization proposal at 19/May/2016 : https://docs.google.com/document/d/1xtfK1C7JbOLx-YztqEDloKBRXWwtFBaLm9pcSwLygAg/edit#heading=h.ie9haz2a79hp<br />
* UseCase proposal at 19/May/2016 : https://docs.google.com/document/d/1JiGV7IUt1PTZg3JvBp9Cr0V7RyosOB_w-z6mMh87ktk/edit?usp=sharing<br />
* Open Contracts proposal at 16/May/2016 : https://drive.google.com/file/d/0B7ecK_oVsnwObGtCYzRRSll1T2tBYmo5N0NDZjUzS28yU3Yw/view?usp=sharing<br />
* Shared Article of HBR at 11/May/2016 : https://hbr.org/2016/05/the-impact-of-the-blockchain-goes-beyond-financial-services?utm_source=twitter&utm_medium=social&utm_campaign=harvardbiz<br />
* Open Key Chain Proposal at 12/Apr/2016 : https://github.com/shepelt/openkeychain-spec<br />
* CG's first workshop report at 25/Mar/2016 : https://www.w3.org/community/blockchain/2016/03/23/workshop-details-at-25mar2016/</div>Mlee22https://www.w3.org/wiki/index.php?title=User:Mlee22&diff=99869User:Mlee222016-09-17T11:58:09Z<p>Mlee22: </p>
<hr />
<div>[[Electronic Commerce Interoperability Standard]]<br />
<br />
[[Blockchain CG member proposals and reports]]</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=78377Electronic Commerce Interoperability Standard2014-10-27T12:44:37Z<p>Mlee22: /* Author */</p>
<hr />
<div>[[File:UA Central ECIS mechanism.png|thumbnail|User Agent Central ECIS Mechanism]]<br />
ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== What is ECIS? ==<br />
* stands for Electronic Commerce Interoperability Standard<br />
* it organize multiple e-commerce services with user agent centric mechanisms<br />
* multiple service providers has their own service mechanism as an island<br />
* user agent is the central point for multiple connectivities and inter-operations between service providers<br />
* ECIS make connectivity to each service providers<br />
** adding standard way to initiate e-commerce service request<br />
** adding standard way to get response from service provider<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Who is Service Provider ==<br />
* Banking Web Service<br />
* Mobile App<br />
* Identity Web Service<br />
* Delivery Web Service<br />
* Currency Exchange Web Service<br />
* Shopping Web Service<br />
<br />
== Data Formats for ECIS ==<br />
* JSON/XML messages can be used for ECIS<br />
** example) IETF ECML (http://tools.ietf.org/html/rfc4112)<br />
<br />
== Protocols with ECIS ==<br />
* Any protocols which is handling message based data are available<br />
** HTTP Request/Response<br />
** Custom URI Scheme<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Centralized by User Agent ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Central<br />
** User Agent is the central point organizing decentralized operations<br />
[[File:UA_Central_ECIS_mechanism.png]]<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
* SAML : http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language<br />
* OpenID : http://en.wikipedia.org/wiki/OpenID<br />
* OAuth : http://en.wikipedia.org/wiki/OAuth<br />
<br />
== Author ==<br />
[[User:Mlee22|Mountie Lee]] ([[User talk:Mlee22|talk]]) 12:44, 27 October 2014 (UTC)<br />
PayGate (www.paygate.net)</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=78376Electronic Commerce Interoperability Standard2014-10-27T12:41:05Z<p>Mlee22: </p>
<hr />
<div>[[File:UA Central ECIS mechanism.png|thumbnail|User Agent Central ECIS Mechanism]]<br />
ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== What is ECIS? ==<br />
* stands for Electronic Commerce Interoperability Standard<br />
* it organize multiple e-commerce services with user agent centric mechanisms<br />
* multiple service providers has their own service mechanism as an island<br />
* user agent is the central point for multiple connectivities and inter-operations between service providers<br />
* ECIS make connectivity to each service providers<br />
** adding standard way to initiate e-commerce service request<br />
** adding standard way to get response from service provider<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Who is Service Provider ==<br />
* Banking Web Service<br />
* Mobile App<br />
* Identity Web Service<br />
* Delivery Web Service<br />
* Currency Exchange Web Service<br />
* Shopping Web Service<br />
<br />
== Data Formats for ECIS ==<br />
* JSON/XML messages can be used for ECIS<br />
** example) IETF ECML (http://tools.ietf.org/html/rfc4112)<br />
<br />
== Protocols with ECIS ==<br />
* Any protocols which is handling message based data are available<br />
** HTTP Request/Response<br />
** Custom URI Scheme<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Centralized by User Agent ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Central<br />
** User Agent is the central point organizing decentralized operations<br />
[[File:UA_Central_ECIS_mechanism.png]]<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
* SAML : http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language<br />
* OpenID : http://en.wikipedia.org/wiki/OpenID<br />
* OAuth : http://en.wikipedia.org/wiki/OAuth<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate (www.paygate.net)</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=78375Electronic Commerce Interoperability Standard2014-10-27T12:37:21Z<p>Mlee22: </p>
<hr />
<div>[[File:UA Central ECIS mechanism.png|thumbnail|User Agent Central ECIS Mechanism]]<br />
ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== What is ECIS? ==<br />
* stands for Electronic Commerce Interoperability Standard<br />
* it organize multiple e-commerce services with user agent centric mechanisms<br />
* multiple service providers has their own service mechanism as an island<br />
* user agent is the central point for multiple connectivities and inter-operations between service providers<br />
* ECIS make connectivity to each service providers<br />
** adding standard way to initiate e-commerce service request<br />
** adding standard way to get response from service provider<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Who are Service Providers ==<br />
* Banking Web Service<br />
* Mobile App<br />
* Identity Web Service<br />
* Delivery Web Service<br />
* Currency Exchange Web Service<br />
* Shopping Web Service<br />
<br />
== Data Formats for ECIS ==<br />
* JSON/XML messages can be used for ECIS<br />
** example) IETF ECML (http://tools.ietf.org/html/rfc4112)<br />
<br />
== Protocols with ECIS ==<br />
* Any protocols which is handling message based data are available<br />
** HTTP Request/Response<br />
** Custom URI Scheme<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Decentralized by User Central ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Centralized<br />
** User Agent is the central point organizing decentralized operations<br />
[[File:UA_Central_ECIS_mechanism.png]]<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
* SAML : http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language<br />
* OpenID : http://en.wikipedia.org/wiki/OpenID<br />
* OAuth : http://en.wikipedia.org/wiki/OAuth<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate Co., Ltd.</div>Mlee22https://www.w3.org/wiki/index.php?title=File:UA_Central_ECIS_mechanism.png&diff=78374File:UA Central ECIS mechanism.png2014-10-27T12:34:38Z<p>Mlee22: Mlee22 uploaded a new version of &quot;File:UA Central ECIS mechanism.png&quot;</p>
<hr />
<div></div>Mlee22https://www.w3.org/wiki/index.php?title=File:UA_Central_ECIS_mechanism.png&diff=78373File:UA Central ECIS mechanism.png2014-10-27T12:29:33Z<p>Mlee22: Mlee22 uploaded a new version of &quot;File:UA Central ECIS mechanism.png&quot;</p>
<hr />
<div></div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=78372Electronic Commerce Interoperability Standard2014-10-27T12:28:05Z<p>Mlee22: </p>
<hr />
<div>[[File:UA Central ECIS mechanism.png|thumbnail|User Agent Central ECIS Mechanism]]<br />
ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== What is ECIS? ==<br />
* stands for Electronic Commerce Interoperability Standard<br />
* it organize multiple e-commerce services with user agent centric mechanisms<br />
* multiple service providers has their own service mechanism as an island<br />
* user agent is the central point for multiple connectivities and inter-operations between service providers<br />
* ECIS make connectivity to each service providers<br />
** adding standard way to initiate e-commerce service request<br />
** adding standard way to get response from service provider<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Who are Service Providers ==<br />
* Banking Web Service<br />
* Mobile App<br />
* Identity Web Service<br />
* Delivery Web Service<br />
* Currency Exchange Web Service<br />
* Shopping Web Service<br />
<br />
== Data Formats for ECIS ==<br />
* JSON/XML messages can be used for ECIS<br />
** example) IETF ECML (http://tools.ietf.org/html/rfc4112)<br />
<br />
== Protocols with ECIS ==<br />
* Any protocols which is handling message based data are available<br />
** HTTP Request/Response<br />
** Custom URI Scheme<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Decentralized by User Central ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Centralized<br />
** User Agent is the central point organizing decentralized operations<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
* SAML : http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language<br />
* OpenID : http://en.wikipedia.org/wiki/OpenID<br />
* OAuth : http://en.wikipedia.org/wiki/OAuth<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate Co., Ltd.</div>Mlee22https://www.w3.org/wiki/index.php?title=File:UA_Central_ECIS_mechanism.png&diff=78371File:UA Central ECIS mechanism.png2014-10-27T12:16:13Z<p>Mlee22: </p>
<hr />
<div></div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=78370Electronic Commerce Interoperability Standard2014-10-27T12:15:22Z<p>Mlee22: </p>
<hr />
<div>ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== What is ECIS? ==<br />
* stands for Electronic Commerce Interoperability Standard<br />
* it organize multiple e-commerce services with user agent centric mechanisms<br />
* multiple service providers has their own service mechanism as an island<br />
* user agent is the central point for multiple connectivities and inter-operations between service providers<br />
* ECIS make connectivity to each service providers<br />
** adding standard way to initiate e-commerce service request<br />
** adding standard way to get response from service provider<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Who are Service Providers ==<br />
* Banking Web Service<br />
* Mobile App<br />
* Identity Web Service<br />
* Delivery Web Service<br />
* Currency Exchange Web Service<br />
* Shopping Web Service<br />
<br />
== Data Formats for ECIS ==<br />
* JSON/XML messages can be used for ECIS<br />
** example) IETF ECML (http://tools.ietf.org/html/rfc4112)<br />
<br />
== Protocols with ECIS ==<br />
* Any protocols which is handling message based data are available<br />
** HTTP Request/Response<br />
** Custom URI Scheme<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Decentralized by User Central ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Centralized<br />
** User Agent is the central point organizing decentralized operations<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
* SAML : http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language<br />
* OpenID : http://en.wikipedia.org/wiki/OpenID<br />
* OAuth : http://en.wikipedia.org/wiki/OAuth<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate Co., Ltd.</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69200Electronic Commerce Interoperability Standard2013-10-17T17:08:42Z<p>Mlee22: </p>
<hr />
<div>ECIS stands for E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why ECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for ECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== ECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Decentralized by Centralized ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Centralized<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate Co., Ltd.</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69199Electronic Commerce Interoperability Standard2013-10-17T17:07:24Z<p>Mlee22: </p>
<hr />
<div>DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== DECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]<br />
<br />
# User(UA) send request payment to Shopping Mall<br />
# shopping mall response request-token as XHTML/JSON format<br />
#* the request-token can be signed by merchant<br />
#* the token data can be formatted by ECML or JSON Web Token or others<br />
# UA redirect the request-token to Payment Processor<br />
# Payment processor response request-token to UA<br />
#* Payment processor need to identity user but they are unable to identity user.<br />
# UA redirect the request-token of payment processor to Identity Provider<br />
# Identity Provider identify user<br />
#* depends on ID providers<br />
# Identity Provider response result as XHTML or JSON format<br />
#* the result can be signed by Identity Provider<br />
# UA redirect the result to Payment Processor<br />
# Payment Processor verify the result<br />
#* normally XML Signature verification can be used<br />
# Payment Processor process payment with User<br />
# Payment Processor response payment result <br />
#* the result can be signed by payment processor<br />
#* the formats can be XHTML or JSON<br />
# UA redirect the result to Shopping Mall<br />
# Shopping Mall verify the result sent from Payment Processor<br />
# Shopping Mall deliver product/service to User<br />
<br />
== Decentralized by Centralized ==<br />
* between multiple service providers, the mechanism is de-centralized<br />
* but it is User Centralized<br />
<br />
== Considerations ==<br />
* Timeouts<br />
** Shopping Mall can not wait too much time<br />
** but user know what is under processing<br />
* Trust-Anchor between service providers<br />
** Trust Each Other<br />
** Use PKI<br />
<br />
== References ==<br />
* ECML : http://tools.ietf.org/html/rfc4112<br />
* SAML : http://en.wikipedia.org/wiki/SAML<br />
* XML Encryption : http://en.wikipedia.org/wiki/XML_Encryption<br />
<br />
== Author ==<br />
Mountie Lee (mountie@paygate.net)<br />
PayGate Co., Ltd.</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69198Electronic Commerce Interoperability Standard2013-10-17T16:47:51Z<p>Mlee22: </p>
<hr />
<div>DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== DECIS Sequence Diagram ==<br />
[[= De-centralized E-Commerce Interoperability Standard =<br />
<br />
DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== Considerations ==<br />
= De-centralized E-Commerce Interoperability Standard =<br />
<br />
DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== DECIS Sequence Diagram ==<br />
[[File:DECIS-Sequence-Diagram_v0.1.png]]</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69197Electronic Commerce Interoperability Standard2013-10-17T16:45:47Z<p>Mlee22: </p>
<hr />
<div>DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== DECIS Sequence Diagram ==</div>Mlee22https://www.w3.org/wiki/index.php?title=File:DECIS-Sequence-Diagram_v0.1.png&diff=69196File:DECIS-Sequence-Diagram v0.1.png2013-10-17T16:44:05Z<p>Mlee22: </p>
<hr />
<div></div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69195Electronic Commerce Interoperability Standard2013-10-17T16:43:41Z<p>Mlee22: </p>
<hr />
<div>DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
= Why DECIS is required? =<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
= Data Formats for DECIS =<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
= Exchanging mechanisms =<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
= Considerations =</div>Mlee22https://www.w3.org/wiki/index.php?title=Electronic_Commerce_Interoperability_Standard&diff=69194Electronic Commerce Interoperability Standard2013-10-17T16:42:40Z<p>Mlee22: Created page with "= De-centralized E-Commerce Interoperability Standard = DECIS stands for Decentralized E-Commerce Interoperability Standard. an interoperability standard between service provid…"</p>
<hr />
<div>= De-centralized E-Commerce Interoperability Standard =<br />
<br />
DECIS stands for Decentralized E-Commerce Interoperability Standard.<br />
<br />
an interoperability standard between service providers in decentralized web environment<br />
<br />
== Why DECIS is required? ==<br />
<br />
* no standard method to exchange data between multiple service providers on the web<br />
* no standard framework to exchange data between multiple service providers on the web<br />
* because of above absent, current E-Commerce interoperation need complex integration and more resources.<br />
* when user access shopping service provider(merchant)<br />
** merchant provide their service on their own way<br />
** merchant integrate their backend service providers internally<br />
** no standard to inter-operate/exchange services between multiple providers.<br />
<br />
* a new standard is required<br />
** de-centralized<br />
** interoperabilitable<br />
** between multiple service providers including payment and identity service providers.<br />
<br />
== Data Formats for DECIS ==<br />
* JSON Web Token<br />
* IETF ECML<br />
<br />
== Exchanging mechanisms ==<br />
* SAML<br />
* OpenID<br />
* OAuth<br />
<br />
== Considerations ==</div>Mlee22https://www.w3.org/wiki/index.php?title=User:Mlee22&diff=69190User:Mlee222013-10-17T16:07:45Z<p>Mlee22: </p>
<hr />
<div>[[Electronic Commerce Interoperability Standard]]</div>Mlee22https://www.w3.org/wiki/index.php?title=User:Mlee22&diff=69189User:Mlee222013-10-17T16:07:29Z<p>Mlee22: Created page with "[Electronic Commerce Interoperability Standard]"</p>
<hr />
<div>[Electronic Commerce Interoperability Standard]</div>Mlee22https://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=69091TPAC/2013/SessionIdeas2013-10-14T12:05:13Z<p>Mlee22: /* Web Payments */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Web Payments ===<br />
<br />
* Proposed by: Manu Sporny<br />
* Summary: Discuss the role of W3C in the creation of a set of value-exchange (payment / crowdfunding / P2P finance) standards for the Web, consider PaySwarm, Bitcoin, Ripple and other emerging technologies.<br />
* Session: Short 15 minute intro on the topic followed by open discussion<br />
* Goals<br />
** See if a Web Payments Workshop or Working Group is needed<br />
** Educate and organize people around the Web Payments work<br />
** Determine the path forward<br />
** Establish E-Commerce Interoperability standard<br />
* Interested : Mountie Lee at paygate dot net<br />
<br />
=== How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested:<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services (training and validator suite)<br />
* Type: Presentation and discussion<br />
* Goals: The new services team would like to provide an update on these new existing services. We will be happy to answer your questions related to these new W3C services and what are the W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Prefered date: Thursday morning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: ddavis<br />
<br />
=== W3C Data ===<br />
<br />
* Proposed by: Ian Jacobs (Need to get Ted Guild on board!)<br />
* Summary: Data needs <br />
* Goals: Share information about what plans are for exposing and documenting W3C Data<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session''' Natasha Rooney, Virgnie Galindo<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
=== Security roadmap ===<br />
<br />
* Proposed by: Virginie GALINDO<br />
* Summary: Discuss the security roadmap of W3C by presenting the existing work done in WebAppSec and Web Crypto Working Group, reminding the existence of the Web Security Interest Group and collecting the current security challenges that the members are facing to create the security roadmap of W3C. <br />
* Session: Short 10 minute intro on the topic followed by open discussion<br />
* Goals<br />
** Educate people on the security feature under development in W3C<br />
** Collect the wish list in terms of security of the attendees<br />
** Build the priority topics that should be discussed in Web Security Interest Group<br />
*** JS sandboxing / integrity checking / encryption / signature verification / obfuscation<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow, Natasha Rooney, Mountie Lee<br />
<br />
=== Update on Offline ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Natasha Rooney<br />
* Summary: We had a great Offline Breakout at last year's TPAC and a lot has happened since then. We have seen work in App Cache, Manifest files and now ServiceWorker. This session will give an overview of what is going on and give everyone a good opportunity to ask the experts questions and have some useful discussions on the topic which might bring about some issues which can be considered for future work. <br />
* Type: Presentation and discussion<br />
* Goals: Bring everyone up to a similar level of understanding, raise important issues to all W3C members, and to help those working on solutions.<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow<br />
<br />
=== Moving Forward on Geolocation API ===<br />
<br />
* Proposed by: Giri Mandyam<br />
* Summary: Discuss a next version of the Geolocation API. This will include enhancements to the existing API (e.g. indoor location, geofencing, etc.), testing and conformance, and the status of the existing specifications from the Geolocation Working Group (e.g. DeviceOrientation).<br />
* Session: 15 minute intro followed by open discussion<br />
* Goals<br />
** Determine interest in reopening the Geolocation Working Group<br />
** Itemize desired enhancements from member companies for existing geolocation specifications<br />
* Interested: '''People will put names here if interested in attending this session:'''</div>Mlee22https://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=69090TPAC/2013/SessionIdeas2013-10-14T12:04:34Z<p>Mlee22: /* Security roadmap */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Web Payments ===<br />
<br />
* Proposed by: Manu Sporny<br />
* Summary: Discuss the role of W3C in the creation of a set of value-exchange (payment / crowdfunding / P2P finance) standards for the Web, consider PaySwarm, Bitcoin, Ripple and other emerging technologies.<br />
* Session: Short 15 minute intro on the topic followed by open discussion<br />
* Goals<br />
** See if a Web Payments Workshop or Working Group is needed<br />
** Educate and organize people around the Web Payments work<br />
** Determine the path forward<br />
** Establish E-Commerce Interoperability standard<br />
* interested : Mountie Lee at paygate dot net<br />
<br />
=== How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested:<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services (training and validator suite)<br />
* Type: Presentation and discussion<br />
* Goals: The new services team would like to provide an update on these new existing services. We will be happy to answer your questions related to these new W3C services and what are the W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Prefered date: Thursday morning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: ddavis<br />
<br />
=== W3C Data ===<br />
<br />
* Proposed by: Ian Jacobs (Need to get Ted Guild on board!)<br />
* Summary: Data needs <br />
* Goals: Share information about what plans are for exposing and documenting W3C Data<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session''' Natasha Rooney, Virgnie Galindo<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
=== Security roadmap ===<br />
<br />
* Proposed by: Virginie GALINDO<br />
* Summary: Discuss the security roadmap of W3C by presenting the existing work done in WebAppSec and Web Crypto Working Group, reminding the existence of the Web Security Interest Group and collecting the current security challenges that the members are facing to create the security roadmap of W3C. <br />
* Session: Short 10 minute intro on the topic followed by open discussion<br />
* Goals<br />
** Educate people on the security feature under development in W3C<br />
** Collect the wish list in terms of security of the attendees<br />
** Build the priority topics that should be discussed in Web Security Interest Group<br />
*** JS sandboxing / integrity checking / encryption / signature verification / obfuscation<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow, Natasha Rooney, Mountie Lee<br />
<br />
=== Update on Offline ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Natasha Rooney<br />
* Summary: We had a great Offline Breakout at last year's TPAC and a lot has happened since then. We have seen work in App Cache, Manifest files and now ServiceWorker. This session will give an overview of what is going on and give everyone a good opportunity to ask the experts questions and have some useful discussions on the topic which might bring about some issues which can be considered for future work. <br />
* Type: Presentation and discussion<br />
* Goals: Bring everyone up to a similar level of understanding, raise important issues to all W3C members, and to help those working on solutions.<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow<br />
<br />
=== Moving Forward on Geolocation API ===<br />
<br />
* Proposed by: Giri Mandyam<br />
* Summary: Discuss a next version of the Geolocation API. This will include enhancements to the existing API (e.g. indoor location, geofencing, etc.), testing and conformance, and the status of the existing specifications from the Geolocation Working Group (e.g. DeviceOrientation).<br />
* Session: 15 minute intro followed by open discussion<br />
* Goals<br />
** Determine interest in reopening the Geolocation Working Group<br />
** Itemize desired enhancements from member companies for existing geolocation specifications<br />
* Interested: '''People will put names here if interested in attending this session:'''</div>Mlee22https://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=69089TPAC/2013/SessionIdeas2013-10-14T11:59:59Z<p>Mlee22: /* Security roadmap */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Web Payments ===<br />
<br />
* Proposed by: Manu Sporny<br />
* Summary: Discuss the role of W3C in the creation of a set of value-exchange (payment / crowdfunding / P2P finance) standards for the Web, consider PaySwarm, Bitcoin, Ripple and other emerging technologies.<br />
* Session: Short 15 minute intro on the topic followed by open discussion<br />
* Goals<br />
** See if a Web Payments Workshop or Working Group is needed<br />
** Educate and organize people around the Web Payments work<br />
** Determine the path forward<br />
** Establish E-Commerce Interoperability standard<br />
* interested : Mountie Lee at paygate dot net<br />
<br />
=== How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested:<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services (training and validator suite)<br />
* Type: Presentation and discussion<br />
* Goals: The new services team would like to provide an update on these new existing services. We will be happy to answer your questions related to these new W3C services and what are the W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Prefered date: Thursday morning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: ddavis<br />
<br />
=== W3C Data ===<br />
<br />
* Proposed by: Ian Jacobs (Need to get Ted Guild on board!)<br />
* Summary: Data needs <br />
* Goals: Share information about what plans are for exposing and documenting W3C Data<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session''' Natasha Rooney, Virgnie Galindo<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
=== Security roadmap ===<br />
<br />
* Proposed by: Virginie GALINDO<br />
* Summary: Discuss the security roadmap of W3C by presenting the existing work done in WebAppSec and Web Crypto Working Group, reminding the existence of the Web Security Interest Group and collecting the current security challenges that the members are facing to create the security roadmap of W3C. <br />
* Session: Short 10 minute intro on the topic followed by open discussion<br />
* Goals<br />
** Educate people on the security feature under development in W3C<br />
** Collect the wish list in terms of security of the attendees<br />
** Build the priority topics that should be discussed in Web Security Interest Group<br />
*** JS sandboxing / integrity checking / encryption / signature verifycation / obfuscation<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow, Natasha Rooney, Mountie Lee<br />
<br />
=== Update on Offline ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Natasha Rooney<br />
* Summary: We had a great Offline Breakout at last year's TPAC and a lot has happened since then. We have seen work in App Cache, Manifest files and now ServiceWorker. This session will give an overview of what is going on and give everyone a good opportunity to ask the experts questions and have some useful discussions on the topic which might bring about some issues which can be considered for future work. <br />
* Type: Presentation and discussion<br />
* Goals: Bring everyone up to a similar level of understanding, raise important issues to all W3C members, and to help those working on solutions.<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow<br />
<br />
=== Moving Forward on Geolocation API ===<br />
<br />
* Proposed by: Giri Mandyam<br />
* Summary: Discuss a next version of the Geolocation API. This will include enhancements to the existing API (e.g. indoor location, geofencing, etc.), testing and conformance, and the status of the existing specifications from the Geolocation Working Group (e.g. DeviceOrientation).<br />
* Session: 15 minute intro followed by open discussion<br />
* Goals<br />
** Determine interest in reopening the Geolocation Working Group<br />
** Itemize desired enhancements from member companies for existing geolocation specifications<br />
* Interested: '''People will put names here if interested in attending this session:'''</div>Mlee22https://www.w3.org/wiki/index.php?title=TPAC/2013/SessionIdeas&diff=69088TPAC/2013/SessionIdeas2013-10-14T11:35:58Z<p>Mlee22: /* Web Payments */</p>
<hr />
<div>We encourage attendees to start brainstorming [[TPAC2013]] session ideas in advance of the meeting. <br />
<br />
See the [http://www.w3.org/wiki/TPAC2013/FAQ TPAC 2013 FAQ] for more information.<br />
<br />
== How to use this page ==<br />
<br />
Please use this page to:<br />
<br />
* Propose sessions you wish you lead<br />
* Propose sessions you wish others to lead<br />
* Indicate whether you plan to attend a session (helps with scheduling)<br />
<br />
== How to propose a session ==<br />
<br />
Please provide:<br />
<ul class="show_items"><br />
* session name (as a === subhead === )<br />
* session proposer (optional: name a desired session leader, can be yourself)<br />
* one sentence session summary<br />
* type of session: (e.g.: talk, panel, open discussion, etc.)<br />
* goals of session<br />
* additional speakers/panelists<br />
</ul><br />
<br />
And feel free to simply add them here at the top. See [[#Site Redesign|site redesign below]] as a template for new entries.<br />
<br />
== Suggestions for Tuesday Morning AC Meeting ==<br />
<br />
The Tuesday morning of the AC Meeting is optional. It is intended for informal discussion among Chairs, AC, TAG, AB, Offices, and Team.<br />
<br />
=== Notes from the Team ===<br />
<br />
* Introduction to W3C's IPR Policies<br />
<br />
=== Notes from the Program committee ===<br />
<br />
* EME<br />
* Schema.org<br />
* Boundaries of W3C work in technology/policy areas<br />
* Improving remote participation in W3C meetings<br />
* Focus AC agenda on TPWG progress; use breakout for broader discussion of Web privacy.<br />
<br />
=== Notes on breakout rooms ===<br />
<br />
* We will seek three breakout rooms + the main room.<br />
* However groups will be meeting in many of the available rooms.<br />
* Therefore, if we can't arrange for 3 distinct rooms, we'll grab corners of the main room.<br />
<br />
== Suggestions for Wednesday Breakouts ==<br />
<br />
Note: For 2013 we invite the Advisory Committee to use the Wednesday breakouts for AC-type topics as well.<br />
<br />
=== Web Payments ===<br />
<br />
* Proposed by: Manu Sporny<br />
* Summary: Discuss the role of W3C in the creation of a set of value-exchange (payment / crowdfunding / P2P finance) standards for the Web, consider PaySwarm, Bitcoin, Ripple and other emerging technologies.<br />
* Session: Short 15 minute intro on the topic followed by open discussion<br />
* Goals<br />
** See if a Web Payments Workshop or Working Group is needed<br />
** Educate and organize people around the Web Payments work<br />
** Determine the path forward<br />
** Establish E-Commerce Interoperability standard<br />
* interested : Mountie Lee at paygate dot net<br />
<br />
=== How to Effectively "listen" to activity ===<br />
<br />
* Proposed by: Al Villarica (Smart Communications) & Alan Bird (W3C and Smart's MRM)<br />
* Summary: W3C has a lot of different activities going on at any given point in time. For a member with a smaller amount of resource it's a challenge to find out what's going on that isn't on our current "radar". We're assuming that members that have been with W3C for a longer period of time may have some "best practices" they could share to help newer, smaller members. <br />
* Type: Discussion<br />
* Goals: Open discussion to provide members with ideas they can implement to gain more value from their W3C Membership by being aware of areas that might be in their organizations longer term objectives. <br />
* Interested:<br />
<br />
=== Notes from the Team ===<br />
<br />
* Anniversary planning<br />
<br />
=== New W3C Services ===<br />
* Proposed by: Marie-Claire Forgue and Bernard Gidon<br />
* Summary: W3C is introducing new services (training and validator suite)<br />
* Type: Presentation and discussion<br />
* Goals: The new services team would like to provide an update on these new existing services. We will be happy to answer your questions related to these new W3C services and what are the W3C Members benefits. We are also interested in finding new ways to promote these new services through the members' networks of developers and customers.<br />
* Prefered date: Thursday morning<br />
<br />
=== Site Redesign ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Ian Jacobs<br />
* Summary: W3C is redesigning its web site. In 2013 we surveyed the public, groups, and Members and created a plan based on the priorities we heard. Come to this session to hear about our progress and provide feedback to help ensure the site meets your needs.<br />
* Type: Presentation and discussion<br />
* Goals: Ian wants to use this opportunity to share progress and get feedback on a the site redesign, including the vision for the site, information architecture, and implementation plans. <br />
* Interested: ddavis<br />
<br />
=== W3C Data ===<br />
<br />
* Proposed by: Ian Jacobs (Need to get Ted Guild on board!)<br />
* Summary: Data needs <br />
* Goals: Share information about what plans are for exposing and documenting W3C Data<br />
<br />
=== How we can be better Chairs ===<br />
Summary: Chairs are one of the key components in a Working Group, and they can make a big positive or negative difference to the effectiveness of their group. This session is intended for active chairs and people who expect to be or would like to be chairs<br />
<br />
* Proposed by: Chaals<br />
* Type: Open Discussion<br />
* Goals: Share experience and learn from each other. Look at the resources available in the chairs' [http://www.w3.org/guide Guide] and propose necessary changes.<br />
* Interested: '''People will put names here if interested in attending this session''' Natasha Rooney, Virgnie Galindo<br />
<br />
Some potential topics:<br />
* dealing with trolls<br />
* Tools: github, tracker, bugzilla, lc-track, ...<br />
* Meetings - when to have them, how to plan them, how to get the best out of them<br />
* Editors, authors, and one-man bands<br />
<br />
=== Rec track process ===<br />
Summary: Looking at how to make the Recommendation track meet the needs of our stakeholders<br />
<br />
* Proposed by: Chaals<br />
* Type: Discussion and presentation<br />
* Goals: Work out who are our stakeholders, and what do they need from our specs. Explain the AB's proposed changes for the Process document<br />
* Interested: '''People will put names here if interested in attending this session'''<br />
<br />
=== Security roadmap ===<br />
<br />
* Proposed by: Virginie GALINDO<br />
* Summary: Discuss the security roadmap of W3C by presenting the existing work done in WebAppSec and Web Crypto Working Group, reminding the existence of the Web Security Interest Group and collecting the current security challenges that the members are facing to create the security roadmap of W3C. <br />
* Session: Short 10 minute intro on the topic followed by open discussion<br />
* Goals<br />
** Educate people on the security feature under development in W3C<br />
** Collect the wish list in terms of security of the attendees<br />
** Build the priority topics that should be discussed in Web Security Interest Group<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow, Natasha Rooney<br />
<br />
=== Update on Offline ===<br />
<br />
<em>Use this as a template for describing your session</em><br />
<br />
* Proposed by: Natasha Rooney<br />
* Summary: We had a great Offline Breakout at last year's TPAC and a lot has happened since then. We have seen work in App Cache, Manifest files and now ServiceWorker. This session will give an overview of what is going on and give everyone a good opportunity to ask the experts questions and have some useful discussions on the topic which might bring about some issues which can be considered for future work. <br />
* Type: Presentation and discussion<br />
* Goals: Bring everyone up to a similar level of understanding, raise important issues to all W3C members, and to help those working on solutions.<br />
* Interested: '''People will put names here if interested in attending this session:''' Art Barstow<br />
<br />
=== Moving Forward on Geolocation API ===<br />
<br />
* Proposed by: Giri Mandyam<br />
* Summary: Discuss a next version of the Geolocation API. This will include enhancements to the existing API (e.g. indoor location, geofencing, etc.), testing and conformance, and the status of the existing specifications from the Geolocation Working Group (e.g. DeviceOrientation).<br />
* Session: 15 minute intro followed by open discussion<br />
* Goals<br />
** Determine interest in reopening the Geolocation Working Group<br />
** Itemize desired enhancements from member companies for existing geolocation specifications<br />
* Interested: '''People will put names here if interested in attending this session:'''</div>Mlee22