<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Paul DiMarzio on Medium]]></title>
        <description><![CDATA[Stories by Paul DiMarzio on Medium]]></description>
        <link>https://medium.com/@ptdimarzio?source=rss-31dd98016a65------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*FJWqLPz837MwmsjQjEuSmg.png</url>
            <title>Stories by Paul DiMarzio on Medium</title>
            <link>https://medium.com/@ptdimarzio?source=rss-31dd98016a65------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:59:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ptdimarzio/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing the Workload Automation Publication]]></title>
            <link>https://medium.com/workload-automation/announcing-the-workload-automation-publication-885620717b12?source=rss-31dd98016a65------2</link>
            <guid isPermaLink="false">https://medium.com/p/885620717b12</guid>
            <category><![CDATA[mainframe-modernization]]></category>
            <category><![CDATA[workload-automation]]></category>
            <category><![CDATA[mainframe]]></category>
            <category><![CDATA[wla]]></category>
            <dc:creator><![CDATA[Paul DiMarzio]]></dc:creator>
            <pubDate>Tue, 15 Aug 2023 18:45:48 GMT</pubDate>
            <atom:updated>2023-08-15T18:45:48.667Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Get a mainframe perspective on multi-platform workload automation in this new publication</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1lLM7kFfPN7maO1QhicNBg.jpeg" /></figure><p>Whether you’re shopping, learning, communicating, planning, or working, chances are you’re utilizing digital services. Often, you’re not aware of it; even the act of physically going to a store and using your credit card for a purchase involves engaging with a digital network.</p><p>Digital transformation has become deeply embedded in nearly every facet of our daily lives. For IT staff tasked with meeting SLAs and ensuring the availability of business applications, this reality introduces fresh challenges. One of these challenges is managing workload processing across an increasingly diverse network of mainframes and distributed systems, residing on-premises and across hybrid cloud environments.</p><p><strong>Managing Workloads in Hybrid Environments</strong></p><p>Successfully orchestrating and managing business service workloads in such an environment can be challenging, to say the least. One key element of success lies in automating repetitive tasks within mission-critical workload processing. But to do this, you must be sure that all enterprise security standards are not compromised, automated tasks adhere to audit compliance protocols, and an end-to-end recovery process is maintained.</p><p>Schedulers offering workload automation are available on every platform. At Broadcom, our flagship schedulers for the mainframe are included in the <a href="https://www.broadcom.com/products/mainframe/workload-automation/esp-edition?utm_medium=article%20links&amp;utm_source=Medium&amp;utm_campaign=msd_fy23_cross_media&amp;utm_content=blog-announcing-the-workload-automation-publication">ESP Workload Automation Intelligence</a> and <a href="https://www.broadcom.com/products/mainframe/workload-automation/ca7?utm_medium=article%20links&amp;utm_source=Medium&amp;utm_campaign=msd_fy23_cross_media&amp;utm_content=blog-announcing-the-workload-automation-publication">CA 7 Workload Automation Intelligence</a> solutions. But there must be a point of integration across all schedulers in your hybrid cloud environment–one that can support the automation of multi-platform business processes. There is a wide range of products on the market built to manage workload automation across a diverse set of workload schedulers. At Broadcom, we offer <a href="https://www.broadcom.com/products/software/automation/automic-automation-intelligence?utm_medium=article%20links&amp;utm_source=Medium&amp;utm_campaign=msd_fy23_cross_media&amp;utm_content=blog-announcing-the-workload-automation-publication">Automation Analytics &amp; Analysis</a> (AAI), but you will find many other vendors offering their own products.</p><p><strong>Filling the Visibility Gap</strong></p><p>End-to-end visibility across the hybrid environment is critical for multi-platform automation, but achieving complete end-to-end visibility can be difficult, particularly when mainframes are part of the process. This isn’t at all due to mainframes themselves; rather, it happens because distributed workload automation tools are often developed by experts who are well-versed in distributed systems, but not in connecting to and coordinating with mainframe workload schedulers.</p><p>The technology is there; it only takes a little education to fill this visibility gap! That’s why we created this publication: to present articles that offer a mainframe perspective on multi-platform workload automation, along with a range of tips and techniques for enhancing mainframe involvement in end-to-end automation strategies.</p><p>As we embark on this journey, our first series of posts will delve into three major trends in workload management and automation:</p><ol><li><strong>Hybrid: Managing Workload in a Hybrid IT Environment<br></strong>Using agents to enable workload teams to connect mainframe native schedulers to SaaS applications without the need for custom scripting.</li><li><strong>Shift-Left: Empowering Developers to Address Their Requirements<br></strong>Expediting the development process by facilitating self-service of scheduling tasks.</li><li><strong>Observability: Utilizing Predictive Analytics and Modern UIs for Enterprise SLA Management<br></strong>Supplying data to the tools that utilize analytics to make informed end-to-end workload automation decisions.</li></ol><p>Transparency remains paramount and, once again, open APIs emerge as a critical component.</p><p><strong>Let’s Get this Journey Started!</strong></p><p>If you want to get right into the details of a specific topic of interest, this publication is for you. If you prefer a more guided path, Mike Kiehl’s <a href="https://mainframe.broadcom.com/blog/innovations-in-the-broadcom-workload-automation-portfolio?utm_medium=article%20links&amp;utm_source=Medium&amp;utm_campaign=msd_fy23_cross_media&amp;utm_content=blog-announcing-the-workload-automation-publication">Innovations in the Broadcom Workload Automation Portfolio</a> delivers a broad overview that will guide you to more detailed posts on the topics that have been covered here.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=885620717b12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/workload-automation/announcing-the-workload-automation-publication-885620717b12">Announcing the Workload Automation Publication</a> was originally published in <a href="https://medium.com/workload-automation">Workload Automation</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My new world view — helping make Ethereum a household word]]></title>
            <link>https://medium.com/@ptdimarzio/my-new-world-view-helping-make-ethereum-a-household-word-d54ddfcd6f3e?source=rss-31dd98016a65------2</link>
            <guid isPermaLink="false">https://medium.com/p/d54ddfcd6f3e</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[wifi]]></category>
            <category><![CDATA[eea]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Paul DiMarzio]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 14:30:43 GMT</pubDate>
            <atom:updated>2019-11-06T14:30:43.502Z</atom:updated>
            <content:encoded><![CDATA[<h3>My new world view — helping make Ethereum a household word</h3><h3>My new world view: helping make Ethereum a household word</h3><p>Around the middle of 2019, I was looking around for my next professional challenge. After having spent time working with most of the leading blockchain platforms while at Digital Asset and IBM I knew in my heart that it was time to give Ethereum a try (why? If there’s one thing I’ve learned over the years, it’s to always follow the developers!). But when the offer came in to join the <a href="https://entethalliance.org/">Enterprise Ethereum Alliance</a>, I wasn’t sure — having been product-focused for my entire career, did I really want to sign on with a non-profit industry standards organization? It didn’t take long at EEA to realize that I made the right decision. Here’s my story, and a glimpse into what EEA is doing to make a difference.</p><h3>What would you give up for a month rather than lose Wi-Fi access?</h3><p>I don’t do anything without research, and while I was researching the value of industry orgs, in general, I came across the results of a <a href="https://www.dailymail.co.uk/sciencetech/article-3585715/Would-sex-wifi-Study-reveals-d-without-stay-online.html">curious poll conducted in 2016</a>, where 1,500 U.S. adult smartphone users were asked what they would be willing to give up for a month rather than lose Wi-Fi access. The answers covered pretty much the entire range of life’s indulgences and pleasures, including wine, fast food, coffee, sex, friends, a partner, and showers. Thinking about how ubiquitous Wi-Fi had become in our lives, I could see where they would value it over some of the items in this list (coffee — never!).</p><p>But I’m old enough to remember a time when it wasn’t this way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*hBAQ74lyM7lSqSamGSTtHg.png" /><figcaption>My new home — 2000</figcaption></figure><p>Back in 2000, I was having my new family home built and I wanted it to be totally connected for data, voice, and video. So, one particularly freezing weekend during construction my pal and I ran 40 cables through the shell — two Cat 5 and two RG6 runs to twenty locations throughout the house (I really didn’t know where my connected devices would be, so most rooms had two runs in different areas). It was a real nightmare! But Wi-Fi at the time was not an option — it was unreliable, and support mainly limited to laptops. Being a laptop-wielding traveler in those days I can attest to the difficulty of actually connecting in those cases where a signal was available because of a lack of interoperability among different vendors’ equipment.</p><p>Although the IEEE had come up with a great technical standard (the original 802.11), as a Standards Developing Organization (SDO) they had no mission — and therefore no ability — to test product compliance to their standard. And so, any manufacturer could claim they were compliant or compatible with the spec, but reality showed that very few would have passed an actual certification test.</p><h3>Technology stewardship needs to be matched with market stewardship</h3><p>These days all but three of those wires are used — to feed the three wireless access points that envelope my home in a blanket of Wi-Fi that ‘just works’. What turned things around?</p><p>Just as I was building my house, an organization formed by a variety of players in the wireless industry — the Wireless Ethernet Compatibility Alliance — was just getting on its feet. Now known more appropriately as the Wi-Fi Alliance, this organization had the business savvy needed to convert the exceptional engineering of the IEEE into a technology with web-scale adoption.</p><p>Their formula was simple. First, use an understanding of what customers really want and derive an industry perspective from the work of the SDOs; with this industry perspective in mind, develop additional specifications as necessary to fill any gaps. Second, guarantee through certification programs that the products of member organizations would interoperate. It’s this combination of market-driven specifications and certification testing that ultimately drove the web-scale adoption of Wi-Fi, making it a household word and something that people value more than their morning cup of joe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/224/1*UsQI3_tRUi9jCpIvGhtUOg.png" /></figure><p>Of course, the Wi-Fi Alliance was not the only industry organization to make a market out of SDO specs. <a href="http://wimaxforum.org/">WiMAX Forum</a>, <a href="https://www.3gpp.org/">3GPP</a>, <a href="https://www.bluetooth.com/">Bluetooth Special Interest Group</a>, and the <a href="https://openconnectivity.org/">Open Connectivity Foundation</a> are similar examples from other industries. What I learned from this is that technology stewardship needs to be matched with market stewardship to bring the market for a new technology to life. Without such a transition from technical innovation to market receptivity, even the most ground-breaking technology will remain limited to a small cadre of enthusiasts and likely never achieve web-scale adoption.</p><h3>What would you give up for a month rather than lose Ethereum mainnet access?</h3><p>Sorry to say, but Ethereum is no-where near the tipping point of achieving this sort of adoption. Whenever I would discuss this job opportunity with anyone — even my tech-savvy colleagues — I was met with blank stares.</p><blockquote>Them: So, what’s the job about?</blockquote><blockquote>Me: A technology called Ethereum.</blockquote><blockquote>Them: What?</blockquote><blockquote>Me: Have you ever heard of blockchain?</blockquote><blockquote>Them: Oh, maybe. I think so.</blockquote><blockquote>Me: Have you ever heard of Bitcoin?</blockquote><blockquote>Them: Oh yeah!!!</blockquote><blockquote>Me: Well, it’s sorta something like that, but way better.</blockquote><blockquote>Them (hesitatingly): Oh…. Cool.</blockquote><p>And my friends only knew about Bitcoin due to all the stories of drug lords, kidnappers, and cyber-criminals that were being put out steadily by the press — not from personal experience.</p><p>Yup, the EEA was where I needed to be!!</p><h3>So, Paul, can you net out what the EEA is all about?</h3><p>Just like those other organizations that raised their target markets to new levels of mass adoption, the EEA was formed by stakeholders in the Ethereum community to do the same. We have a very diverse membership, drawing from organizations in the private sector (large and small, technology providers and technology consumers), government, academics, and civil society at large. In the EEA everyone has an equal voice. This allows us to develop a neutral, competitive, and credible market view.</p><p>Our vision, of course, is to empower enterprise Ethereum services everywhere for everyone. What do I mean by ‘enterprise’ Ethereum? It’s simply the use of Ethereum (the public mainnet or private permissioned networks) for business activities such as commerce, exchange, and trade. That’s it! We have a three-prong strategy for achieving that vision:</p><p>1. Achieve a commercially viable global ecosystem for all by publishing an open standards-based architecture and market-driven technical specifications</p><p>2. Build trust in services and solutions credentialed by EEA through cost-effective and timely testing and certification processes</p><p>3. Establish Ethereum as the worldwide market leader for enterprise blockchain solutions by heavily promoting the brand and technology</p><p>The core of the EEA architecture stack relies on the formal definition of the Ethereum protocol as published in the <a href="https://ethereum.github.io/yellowpaper/paper.pdf">Yellow Paper</a>, and core technologies that have been added to the mainnet since. Through open, member-driven workgroups, specs for additional capabilities demanded by the enterprise market are then layered on top. We have two published specifications to date: the <a href="https://entethalliance.org/wp-content/uploads/2019/11/EEA_Enterprise_Ethereum_Client_Specification_V4.pdf">EEA Client Specification</a>, and the <a href="https://entethalliance.org/wp-content/uploads/2019/11/EEA_Off-Chain_Trusted_Compute_Specification_v1.1.pdf">EEA Off-Chain Trusted Compute Specification</a>.</p><p>Although the EEA produces specs, not code, I find it interesting that code adhering to EEA specs is increasingly being adopted by Hyperledger as new projects. The Ethereum client formerly known as Pantheon was contributed to Hyperledger by PegaSys and is now the <a href="https://www.hyperledger.org/projects/besu">Besu project</a>. Similarly, a coded example of the Trusted Compute spec has been accepted by Hyperledger as the <a href="https://www.hyperledger.org/projects/avalon">Avalon project</a>. I think that this combination of specs and spec-based open source code can only help accelerate the market.</p><p>Although not quite ready for the public yet, all of the EEA’s specifications will be backed by a certification testing program designed to give consumers confidence that EEA-certified products deliver the interoperability they need, and capabilities they want. This is a core tenet of the EEA’s mandate. Look for this to become available sometime in 2020.</p><p>And marketing is, well, marketing!</p><h3>Riding the magic bus</h3><p>When the EEA was first formed, our members were focused on private, permissioned Ethereum networks for any sort of business opportunity. At the time the public Ethereum mainnet had, to put it kindly, a less than stellar perception as a business-friendly place. The three key deficiencies cited were in the areas of the ‘Three Ps’: privacy, permissioning, and performance. Everyone felt the need to conduct business in a locked-down space, and the current EEA specifications are mainly focused on addressing the three Ps.</p><p>But we think there’s a shift occurring in how people perceive Ethereum as a place for conducting business. Certainly, the impending shift towards Ethereum 2.0 technologies is helping here — but also there are an increasing number of enterprises doing just fine on the public mainnet. And so, the EEA has joined forces with the Ethereum Foundation and other groups to begin examining mainnet updates that would be beneficial to the enterprise. My colleague from EEA member ConsenSys calls the mainnet the ‘Magic Bus’ — a place where both business and peer-to-peer transactions can intermingle safely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*DOAxt7I41c4a4lJP0H0-dA.png" /></figure><p>Private networks won’t disappear — so we will continue writing specs for them — but I see an inevitable shift of some percentage of work towards the public mainnet, with strong, seamless connectivity between public and private deployments. Very much along the lines of how intranets co-exist with the public Internet today.</p><h3>Hello, I’m Paul, and I’m here to help</h3><p>I had the chance to present my story to a large group of Ethereum developers at Devcon 5 in Osaka this month — barely two months into the job! There was a lot of acceptance of what we’re doing, it was an exciting conference, and I’m now certain that I made the right decision!</p><p>My job as Director of Community for the EEA is to help make sure that all the various communities we serve know what we’re doing and have a chance to have their voices heard. I’m trying to make myself as easy to find as possible, here are some places you can engage me in dialog. I hope you’ve enjoyed this little piece and I look forward to working with you to the point where Ethereum is as important as wine, sex, and showers to the average consumer!</p><p>· Paul.DiMarzio@entethalliance.org</p><p>· @PaulD360 on Twitter</p><p>· @PTDiMarzio on Telegram</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d54ddfcd6f3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A critical problem with tokens and the industry-wide solution to solve it!]]></title>
            <link>https://medium.com/tokenhall/a-critical-problem-with-tokens-and-the-industry-wide-solution-to-solve-it-7c7fd8d39c5c?source=rss-31dd98016a65------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c7fd8d39c5c</guid>
            <category><![CDATA[token-economy]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Paul DiMarzio]]></dc:creator>
            <pubDate>Wed, 25 Sep 2019 17:56:32 GMT</pubDate>
            <atom:updated>2019-09-25T17:56:32.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bh2ojNE9RLhyYdxMbaZazw.png" /></figure><h3>You are already familiar with tokens, whether you realize it or not</h3><p>The topic of tokens can be mystifying when couched in the language of cryptography, blockchains, and that sort of technological talk. But understanding the value and purpose of tokens is actually quite straightforward — a token is just a representation of, or substitute for, something of real value. The value might be physical (a bar of gold), digital (a share of stock — most exchanges are now fully dematerialized), a promise (a seat on an airplane), a proof (college degree), an authorization (access to medical records) … there are many items of value that are represented by tokens today. In order for a token to be a valid substitute for the item of value it must be nearly impossible to fake, and it must have an owner (whether or not ownership can be passed is a function of a particular token — more on that later).</p><p>You already use tokens every day! If you own a house, the value of that house is represented by a property deed recorded in the clerk’s office. Paper currency represents the value of a specific amount of money. Checks (does anyone still write checks?) are another form of fiduciary token. The certified value of a diamond may be represented by a certificate from a gemological institute. UPC codes are an interesting form of token — a UPC represents a particular product type but can be reproduced across hundreds or even thousands of copies of that product (each UPC ‘token’ being equivalent in value — ‘fungible’). Seats on plans and in theaters are represented by tickets. Degrees and certificates represent demonstrated knowledge in particular areas. Your passwords are tokens that give you access to the value or personal information in your accounts.</p><h3>What is the difference between a digitized and digital token?</h3><p>Tokens are very familiar indeed. And many of them are, in fact, already digitized today. As mentioned earlier, dematerialized stock markets don’t issue certificates anymore — your ownership is a digital record that is no longer backed by a physical certificate. Many forms of physical tickets have been replaced by Q-codes on your smart device. But these digital representations are only that — representations. They do not encode behaviors. For example, if you want to sell your share of stock, you still have to work through a broker and a whole series of traditional transactions must be set into motion to match you up with a buyer, obtain the agreed-upon equivalent in funds, and move those funds to your account. Sometimes these processes are still very manual.</p><p>The true value of digital tokens is the ability to encode all of the behaviors and rules directly into the digital token itself in order to greatly simplify, unify, and streamline the use of these tokens. In such a world, for example, if I want to sell my share of stock I would invoke a ‘sell’ method on the stock token, which would then directly manage the work of exchanging my share for the agreed-upon equivalent in financial tokens (written in software called smart contracts) — which I could then exchange for fiat currency if I wished.</p><p>The goal here isn’t so much about removing intermediaries in transactions (although that can happen); it’s about having all parties in a token-based transaction share a mutualized, decentralized, and trusted infrastructure for the execution of that transaction.</p><p>It’s fairly straightforward to come up with a definition of digital tokens in this context. A digital token would reside on a shared, distributed ledger — the mutualized infrastructure. It doesn’t really matter if the underpinning of that ledger is a blockchain, a database, or something else as long as all parties agree that what they see on that ledger is truthful and immutable. Cryptography is the technology used to secure ownership, ensure authenticity, and prevent tampering with digital tokens — fraud-proofing is a requirement of tokens in general. And all of the behaviors and rules that govern what can be done with a token, and by who, are agreed-to in advance by all parties and baked into the shared decentralized ledger (via smart contracts).</p><p>Many digital tokens that fit this description exist today. But the world of tokens is far from optimal.</p><h3>The token tower of Babel</h3><p>The problem is there is no common language for defining the properties, behaviors, and control messages associated with tokens. Sure, there are emerging standards for how token contracts need to interact with their mutualized infrastructure — ERC-20, for example, is a well-known standard for describing the basic interfaces a token must have for running on the Ethereum network. But describing all of the myriad rules of behavior for ERC-20 tokens is totally up to the developer. As of April 16, 2019, there were <a href="https://www.investopedia.com/news/what-erc20-and-what-does-it-mean-ethereum/">more than 181,000 ERC-20-compatible tokens</a> on the Ethereum mainnet. They all implement the six functions required by ERC-20, but nothing else is standardized. And that’s just the developer view; how do you help a businessperson, consumer, auditor, or a regulator, understand what these tokens are actually doing without a common language? The current language around tokens is, unfortunately, steeped in blockchain terminology — understandable since digital tokens first gained mass popularity on public blockchain networks, but this linkage catastrophically adds to the confusion that developers and business people attempting to develop tokens for their use case have when trying to parse the token ecosystem.</p><p>If you have no common means of defining and triggering token behaviors, how then can you begin to write contracts that trade tokens of different types produced by different development teams? Let’s say, for example, that I want to introduce a token for seating at a sporting event, and I’d like the purchase contract to be able to accept a hypothetical dollar token as payment. Not too much trouble to work that out. But what if I represent 10 such venues, each with its own independently developed seating token, and want to be able to accept 15 different payment tokens and cryptocurrencies from various platforms? Without common controls, each pairwise combination of venue and payment token would require a unique contract — that’s 150 contracts in this case. And if I want to be really flexible and accept combinations of payments for a seat, the number of contracts required can increase exponentially.</p><p>Without standard controls, even simple token exchanges can require an excessively large number of contracts. And this is holding up the advancement of digital tokens in the industry.</p><h3>How do we fix this problem?</h3><p>In looking across the vast array of digital tokens already defined for various platforms, we find three common characteristics shared by all:</p><p>• Digital tokens are comprised of properties and behaviors (use case and instructions on how the token is used) that are interacted with using standard control messages</p><p>• All tokens have a common set of base token properties and a collection of non-behavior related properties</p><p>• Tokens differentiate themselves in the market based on the desirability of their particular combination of behaviors and property sets in that market (its use case)</p><p>With these characteristics in mind, we can greatly advance the state of the art for digital tokens by creating a common taxonomy (universal language) that clearly defines and organizes these behaviors and properties in a standardized way.</p><p>And that is, very simply put, what the <a href="https://tokentaxonomy.org/">Token Taxonomy Initiative</a> is all about. The TTI is an independent, member-led organization formed to develop a modular, industry-neutral, and technology-neutral Token Taxonomy Framework (TTF) (universal language) that will set the standard for tokenizing anything of value.</p><p>Since the TTI is a member-driven organization, the TTF is being designed by a diverse set of individuals representing both business and technical expertise based on their own real-world projects and requirements. The TTF is intended to represent the best that the market has to offer to define a token for any use case, and will drive business-level interoperability amongst tokens by being neutral to the underlying technical across different networks and platforms.</p><p>The TTF achieves a level of precision by allowing someone without technical expertise to use and contribute to a repository of artifacts (ingredients), formally described in JSON. These JSON artifacts can contain links to actual code examples in a variety of languages, as well as links to business descriptions that lay out the functioning of the artifact in plain language. The availability of this repository should greatly simplify the task of defining and implementing new tokens — and it is also a great educational tool for developers designing their first tokens.</p><h3>How a token taxonomy framework works</h3><p>To understand better how the TTF works, it’s helpful to take a deeper look at what makes a token a token. As already mentioned, not all tokens are the same but they break down into a set of standard behaviors, properties, and controls. There are hundreds of these elements, and more being defined all the time, but to give a few small examples:</p><p><strong>Value</strong>. The value of tokens is usually described as being fungible (where two tokens of the same type are interchangeable because they have no difference in value) or non-fungible (the value identified by a token instance is unique). Paper currency, when created (in TTF language mintable‘mintable’) — is a good example of fungible tokens since any paper currency is indistinguishable value-wise from any other of the same denomination. Land titles are non-fungible; the title to my property is completely different from the title to yours. Some tokens can also be hybrids of the two; for example, my token to a general-admission movie theater is non-fungible in terms of its date, time, and location but fungible in terms of precisely which seat I purchased.</p><p><strong>Properties and behaviors </strong>explain how a token reacts to a control message. If a token represents a barrel of oil, and that barrel is consumed, the behavior of that token would destroy the token upon verified receipt of consumption (in TTF language burnable).‘burnable’). Conversely, a paper currency used in exchange for its equivalent in coins (TTF language ‘sub-dividabledividable’) simply passes ownership and is not destroyed.</p><p><strong>Transfer of ownership</strong>. Some tokens like paper currency are transferrable without restriction, others cannot be transferred at all (such as airplane tickets, for security reasons).</p><p>The TTF was initially populated by looking at a wide variety of existing tokens, decomposing them, and identifying those reusable parts. From this work a composition framework was built that could contain the various types of parts; the base set of token types was defined; the known set of behaviors identified; and all of these parts neatly categorized and loaded into the framework. By design, the TTF will never be complete: as new properties, behaviors, and controls for any use case are identified, they are loaded back into the TTF for future use.</p><p>If this all still sounds confusing, let me offer a very simple analogy — baking a cake. Doing so requires a bunch of ingredients — eggs, flour, sugar, etc. — and a recipe that explains how much of each to use, when to add them, and how to control the process. If you think about the TTF as containing the ingredients (called artifacts) and recipes (called templates) — you’ve got it! It’s your responsibility to gather the artifacts/ingredients, choose the template/recipe, then bake/code your token class. Individual tokens are instances of that class, just as slices of cake are servings from the whole!</p><p>If you want your cake to have slightly different properties, such as a little more sweetness, you would adjust the recipe accordingly. If you wanted to bake a carrot cake instead of a pumpkin pie, you would use a different set of ingredients and a different recipe. Same with tokens. You have complete control over which artifacts and templates you use to create your tokens for any use case.</p><h3>A token-based economy can (literally) change the world</h3><p>We know how to create digital tokens today. What we don’t do very well at all is deliver a means for tokens to seamlessly interact with each other, or provide a consistent model for defining tokens. A common taxonomy and framework for token development has the potential to bring amazing new efficiencies to a wide array of today’s business interactions. But it also could form the basis of a solution to some of the world’s most intractable problems.</p><p>How about this one:</p><blockquote><em>Over 1 billion people worldwide are unable to prove their identity through any recognized means. As such, they are without the protection of law, and are unable to access basic services, participate as a citizen or voter, or transact in the modern economy. Most of those affected are children and adolescents, and many are refugees, forcibly displaced, or stateless persons.</em></blockquote><blockquote><a href="https://id2020.org/manifesto">https://id2020.org/manifesto</a></blockquote><p>A common language for tokens (TTF) will speed this process.</p><p>Digital tokens have the potential to mitigate some of the issues with digital identity — but only if all involved entities have the ability to understand and interact with these tokens. A standard token taxonomy such as the TTF can accelerate the ability of these entities to overcome issues such as technical design patterns and interoperability standards — paving the way towards development of a private, portable, persistent, and verifiable global identification system that empowers and protects all individuals.</p><h3>Let’s get it done!</h3><p>The first version of the TTF is now available. For any business to contribute to the TTF they would be asked to join our TTI Initiative. Being a member of the TTI ensures your ability to be at the cutting edge of the token-based economy — either as a consumer or produce of digital tokens. Visit The first version of the TTF is now available. For any business to contribute to the TTF they would be asked to join our TTI Initiative. Being a member of the TTI ensures your ability to be at the cutting edge of the token-based economy — either as a consumer or produce of digital tokens. Visit <a href="http://www.tokentaxonomy.org/">www.tokentaxonomy.org</a> for more information. Or send email to for more information, or send email to <a href="/service/mailto:info@tokentaxonomy.org">info@tokentaxonomy.org</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c7fd8d39c5c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/a-critical-problem-with-tokens-and-the-industry-wide-solution-to-solve-it-7c7fd8d39c5c">A critical problem with tokens and the industry-wide solution to solve it!</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>