A White Paper on Product Identifiers
Table of Contents
Press play to have the following section narrated.
Revisiting the past.
The past thirty years have seen unprecedented growth as well as unfortunate setbacks for the promise of a decentralized Internet. For most of us, our internet experience is built around brokered services and tools, created to help manage our individual user IDs, account names, images, rich media posts and other information and combine them into branded services we call social media.
The internet was designed to be the premier network for the distribution of communications and was adopted for public use from its ARPANET roots, founded in the military and regional academic institutes. In the early 90’s Companies like AOL, Compuserve and Netscape released competing internet browsers, which was supposed to encourage the dissemination of free thought and sharing of ideas.
These applications were intended to build a hedge against any one company or entity from being allowed to place too many restrictive controls against its users and protect them from political or nationalistic / fascist views by creating a socially monitored network for the free flow of ideas and information in a public forum.
Those founding principles, used in the creation of Internet policy are even more critical today, and must not cave to pressure imposed by a few authoritarian business models or political views that are again being used to suppress free thought, open dialogue, or political discourse. Let’s remember, the founders created entitlements to enable the free flow of ideas and information as a hedge against those who would prevent legally protected content from appearing on their public platforms. We may not agree with or even like what we see or hear, but if it doesn’t violate law, it should be protected as free speech.
How did we get here?
The innovations behind the creation of the Internet are a combination of complex systems that take years of acquired skills to master. The reason for the explosive growth of social media platforms is because they were designed to simplify the users ability to express their views while providing the network and content management layers for uploading, sharing, and viewing rich media assets including graphics, video, text, data, as well as manage the back and forth communications between parties.
For the very same reasons we are all not masters at the skills required to launch and run a successful IP based Internet services, we still have a strong desire to tap into that social pool where as humans, we find the support and nurture often lacking in the real world. Each of us want to collectively share our insights into what we see and experience in our day to day lives with others who may also share those similar interests in the human experience. Sometimes that means as responsible parties, we must push the pre-narrative envelope of what may or may not be socially acceptable at the time, but becomes the new normal for the future observer.
We are emotional creatures and adept to finding acceptance from our peers when the restrictions of a technical learning curve is replaced with personal enriching experiences. The complexity behind delivering a competing experience is too difficult for most individuals to want to recreate. It’s always the early market leaders that generally get to create the rules and it’s technology innovation that drives adoption. This should not preclude us from enforcing and ratifying our inherent rights to free speech and expression, whichever side of the political divide we reside.
Press play to have the following section narrated.
A platform to set your marketing free.
The desire of the human condition to be understood and recognized through the posting of personalized content gave rise to centrally managed services in the early 90’s like AOL and CompuServe, and have grown today into huge media platforms like Facebook, Snapchat, Twitter, YouTube, Alphabet, Tik-tok, and many more. Advertising revenue is one of the major contributors that enable companies like these to grow into massive corporations where policy and rights to platform access blur into this kind of digital hegemony, due to the cycle between capitalization and the capital raise required to build the organization to profitability. This means the platform becomes the tool to drive the social narrative, usually driven by or influenced by the financiers who control their investors funds and the board members who control the narrative.
Until Xerial, a brand marketer was required to be tied to one of these platforms advertising models and was the only way to reach their users. Something we see as horribly limiting for the brand holder wanting to reign in control over their marketing assets and brand messaging. These are issues that affect both parties to any view and are dangerous because of social trends. The Xerial platform, has been developed as a social media alternative to deliver on the promise of a decentralized Internet platform. In creating Xerial, a company’s marketing assets are no longer tied to the social media platform and the marketing /brand messaging is set free.
Let’s make it abundantly clear, it is easy for opposing voices in the community to get buried under the hypocrisy of dogma or the motion of a pendulum, whether swinging to the left or right on any social issue. Therein lies the danger for any groups opinion or belief system to get buried in a changing of views or culture. This is a platform designed to protect each voice whether Straight, LGBTQ, Hispanic, Christian, Jewish, Black, Brown, White – whatever. The tools that make up Xerial use a cloud-based architecture to connect the customer directly to brands content, specific to an individual or group of products that is managed by the manufacturer or agency charged with the management of that messaging.
At datamazing, we believe all voices should be heard and that information should be shared with the brand holder to help them grow their market placement. This collection of voices are important and having a community share and understand different points of view should be protected at all costs, because they are all critical to the creative process and are used to build a more diverse and stronger community as a whole.
The Xerial platform can simplify the placement and delivery of the brand holders marketing, messaging, and customer retention, because that data is linked using object recognition and product identifiers to locate and manage messaging and services directly between the brand holder and the customer. It is the way to set your brand free.
Great questions you can ask your IT (Information Technology) department. See if your marketing assets are protected against service interruptions or other unforeseen QoS (quality of service) related failures, through the 3rd party social media platform.
- Is your company in control of its marketing and information assets?
- Is your IT department able to rapidly transfer the company’s assets to a competing service provider?
- Is it good policy to leave that data and content at the mercy of a third party?
- Does your company have a contingency plan to maintain communications and information delivery to customers, in case of a service failure?
Xerial Enterprise Resource Platform Extensions
Xerial ERP extensions provide solutions to centralization issues for brand holders wanting to extend brand reach directly with their customer. The platform is built on top of server side applications connected to the mobile UI through a series of custom API’s that were created to simplify the management and dissemination of marketing assets with features that secure, enhance, as well as prevent counterfeiting of a manufacturers brand assets.
Xerial modules are built using an extensible framework, designed to future proof the delivery of marketing assets against future versions of enhanced services and features. Think of it as alway ready for the next big thing. Product data is put together from simple to use, form-based inputs that are tied directly to the data store through identifiers called Product Identifying Xerial Codes. These codes are essentially links directly to the product through the code being printed directly on product packaging and are generated to provide a unique identifier to the product at the individual or SKU level.
Xerial also incorporates the use of Machine Learning, Artificial Intelligence enhanced tags built around shelf edge technologies associated with the product within the retail environment. Xerial automates the assembly into managed and trackable data stores of information that are assembled right at the client’s mobile smart device. The Xerial platform manages all aspects of network performance, content streaming, data handlers, and data management to give your end-user a world-class service experience through an incredible UI, or mobile app interface created specific to the brand holder/client.
Xerial dramatically changes the flow of information through the development of smart applications that detect what server resources are being leveraged to create a minimum quality of service. This managed layer creates lower overall resource loads by enabling them to run from their own protected memory space and in keeping services separated, the platform helps to prioritize resource heavy, on-demand services such as streaming video, while still making smaller loads such as text or data related services to remain unaffected.
Learn more about these platform extensions below.
Product Information Management Layer
The Xerial product management layer, has the primary task of creating, managing and routing product information and rich media content that is created for each product. Each unique product ID is written to master data record, and is identified by linking that product ID back to the data-store created to hold the information specific to that product. When a mobile user scans the product identifier, the Xerial App can locate the data-store and start delivering the data to the device requesting the product data instantly.
Additional layers of content can be simultaneously streamed to the requestor using algorithms designed to measure specific server loads, and when they reach a predefined marker for any specific resource load, such as a spike in user demand for a video stream, the server instantly replicates and pushes the profile and content to servers located in higher-demand regions. This creates a Qos or Quality of service that rivals major on demand video services.
As an example, if the data stream using h.264 compressed 4k videos, streaming to 4 million users at varying start and stop times, will require more resources to handle server loads. The program’s algorithms will replicate the video stream for each client starting at a different time. To create a visual for you, It’s the difference between a cable channel starting a video broadcast at one time always, or what they brand as on-demand, where you choose when to start the video.
Xerial is an E R P or “Enterprise Resource Platform extender” that link cloud-based information services to the existing POS system using a platform, that combines SKU’s and inventory to a B-Channel of information solutions. In its simplest form, the platform ties the organic link between the product and client managed information stores for delivering that data to a client. The content can easily be delivered to mobile, stationery, and desktop devices including consumer television and direct to vehicle, in-motion systems. New delivery options are virtually unlimited.
Companies like IBM first popularized the client server model, using terminals that would link back to the central host server, to run data from the server directly on the terminal machine. Xerial extensions run in much the same way, where the terminal client is the mobile app with the exception that data is separated into manageable service profiles, where the program queries data based on resource usage profiles. It’s a novel approach, but when you are no longer tied to the limitations of a centralized service platform, you find the freedom and capabilities that until now, were nearly impossible to obtain, outside of the platform’s policies.
Welcome to what’s next.
Xerial is an Enterprise Resource Platform extender, which links information stored in cloud-based data-stores to application services designed as an extension to the existing POS system using a platform that combines SKU’s and inventory with product specific promotions, advertisements, information stores and a large knowledge base of information to a B-Channel for delivering content. . . In its simplest form, the platform ties the organic link between the product and new information stores for delivery to the client.
Data management and content reporting features.
Press play to have the following section narrated.
User actions are captured through CRM triggers while a user interacts with your content. The trigger results are stored directly in the product database and are retrievable through the platforms reporting features. Xerial can pull datapoints and break them into report elements that are measured only when a user hits them within the product presentation. The generated reporting features inform you which videos, graphics, content, coupons and shares to which products anywhere on the globe, at any point during the day, and even which time zone city and country the user is activating the data. The goal is to be able to measure the effectiveness of the content to help the brand holder build better usage and psychographics views about the general consumer. This data is always protected and is authorized by the user prior to capture.
Xerial enterprise extensions enable you to place your brand materials, and the CRM tools into places never thought of before, using our IoT software extensions. The company founder Michael Wright finished working on the methods and filed for Patent protection in 2014. The technology used in Serial and ERPe extensions were granted a US Patent in 2018. The methods are used in the Serial enterprise server software, desktop and mobile app using the methods as outlined in the Approved Patent. In providing this novel approach for identifying products in the wild, we can simultaneously capture data about those products over multiple channels in a true omni channel experience.
The way the technology works and the patent works, it’s much like how a scanner recognizes barcodes through a (Point of Sale) system.
Instead of exclusively tracking the Stock Keeping Units or SKUs for inventory purposes, we also focus on delivering media assets and information assets over the Internet by comparing the (PISC) Product Identifying Serial Codes as the product identifier to give the mobile app the datastore location in the cloud. This method is about as organic a link back to the product as you can get.
Counterfeit protection
Press play to have the following section narrated.
Xerial has been designed with enhanced security feature automation where the algorithm is written to identify whether a PISC Product Identifying Xerial Code is a replicant, counterfeit, or expired, or decommissioned product identifier. At a scan point, meaning when a user scans a product identifier, your item’s serial code is sent to the serial server for validation to its master record securely stored in that products database and records the systems transaction file. If the serial code matches, the system triggers an automatic response to the mobile device indicating that the item is active, registered to the system and allows the logic to follow the next predefined set of instructions that make up part of the security algorithms.
If it doesn’t match after several attempts at scanning, a pre-programmed response is executed while the system blocks and reports the code attempt. This allows the system to report the attempt and location of the tag for followup. For example: Xerial Codes provide links to UI elements that tell your customer they can be confident in their purchase of that item. If the code doesn’t match the files data record, the item scan triggers a rejection notification that displays within a modal window on the mobile user’ device that the item being scanned is not a registered serial code, and subsequently limits user interactions to a predefined set of instructions, prior to gaining access to that items master data store.
Because the algorithms are run server-side, prior to the establishment of a connection to the data store, SQL data injection scripts can’t be processed by the server, because these transactions aren’t stored within the same node. Unless the client knows how to crack a blockchain, at each connection between shards within the system. Let’s just say offering natural immunity from a host of potential threats
Even in the case of a bad actor gaining a user administrative role to create a data store related to a PISC, there are zero assets on the client device to run malicious code from a precompiled app. Even so, in the unlikelihood of that event taking place, that action is limited to only one PISC data store and is never given access over the core functions of the platform, further limiting potentially malicious content loads.
AP (Access Point) load balancing with on-demand resource allocation.
Press play to have the following section narrated.
As a product brand’s viewer base grows, the data schema might need to evolve to support those users in certain situations. Xerial runs industry leading data handlers using our own custom designed extensions and modules in the background to enable our tools to manage the integration and delivery of content to each client, freeing our clients’ resources and repurposing them to develop a better user experience.
For example, as you build your service profile, you may have designed it to store user profiles and emails in the same area of your database. As your user base grows, you must integrate more resources like larger storage drives to support that growth, and it takes more resources and time to manage.
When dealing with aging infrastructure, problems like this are one of many root causes of downtimes to the service, especially when you must remap the user modules to the new data-store structure to correct demand on limited resources. Xerial is built on top of over 35 fully customizable APIs and hundreds of open-source extensions, separated into service profiles, each running within a protected memory space. Each API connects the user experience to the core enterprise software dynamically, when building their mobile or desktop experience.
Each profile assembles resources to efficiently deliver the user experience from that resource’s data stores as set by the client. Xerial also integrates hundreds of open-source modules, which make up the Xerial enterprise framework. The framework is built around an extensible architecture, meaning new extensions are added to future proof the marketplace’s standards.
Your services shouldn’t pay for things like video streaming performance and other things because you’re on the same network as a 100-Million users gaming platform which uses a larger number of resources to run its service profile. Server resources and data are never shared in the popular pooled service profiles which tax server resources while your brand experience pays the price. Performance is key to a great user experience. This is where Xerial Platform excels.
Xerial use advanced techniques to distribute resources across the platform through access points while maintaining secure links to information profiles about a specific product or series of products. The distribution of data to many points across nodes are somewhat automated based upon server’s resources utilization. The platform is constantly measuring bandwidth and additional resources to alleviate the server load by transferring resources to nodes throughout a global network of data centers. As changing demand builds for one set of resources, network bottlenecks are minimized by sharing the server load in heavy use areas throughout the nodes.
When resource use increases due to an influx of AP Traffic, patterns emerge that enable our services to store data across multiple data partitions based upon ai-based predictive modeling built around user interaction.
Press play to have the following section narrated.
Database sharding on Xerial, is a pattern where a datastore is likely to need to scale beyond the resources available to a single storage node modeled from access point data usage and is used to improve performance by reducing contention in the data store. For example, let’s say you’re designing the next Apple iTunes®, you’ll need to store and provide low latency leads to a vast number of audio and text-based information files. In this case, you might want to shard by the genre of the artists.
You’ll want to create replicas of the individual shards to provide on-demand availability. The primary focus of Sharding is to improve performance and scalability. Still, it can also improve availability as a by-product because of data partitioning.
So the process of sharding is to multiply the number the number of starting nodes on any set of data streams by increasing the starting points of operators based upon direct filenames that are each held within their own protected memory space and/or physical data store. To test these points, we built our very own tune player solution called Songtracks. We built Songtracks to hold song files or MP3/M4a files. Mpeg video, H.264 Video in 4k as well as photographic data, graphics and a communications layer, all within the same data stream being dynamically assembled in the viewer app.
A catastrophic event in one partition doesn’t prevent an application from accessing data held in other sections. . .
An operator can perform maintenance or recovery of one or more areas without making the entire data for an application inaccessible. . .
Xerial's use of a Hyper-ledger Fabric and Blockchain
Secure transaction utilize the ERC20 compliant smart contracts between parties to simplify the distribution of Tokens for services rendered in up to 9 decimals points, which enable a far larger number of service providers to provide scaled services as well as primary party positions in each payment ledger. When using smart contracts, the process for reporting transactions to the ledger to complete terms between parties is massively simplified.
The platform extensions do things like license validation between distributor and client nodes, as well as using dynamic shift on asset utilization throughout our network of MSC Nodes using IoT for things like load monitoring and QoS performance classes, while hyperledger creates the transparency between parties to conduct the business of things. This creates a unique, ground breaking, Hybrid Technology platform built around open standards and transparency between all parties involved. Reporting to standards associations such as MRC (Formerly SoundScan) keep all parties aware of actual listener and physical merchandise sales in a platform design with audit trails to every aspect of artists content. With each party to the smart contract capable of real-time reporting from never before accessible layers of revenue, traditionally utilized by the Label/Distributor.
Xerial is designed to record a Blockchain as an added security layer for securing the connection between each node used while assembling the user experience. The cost for storing transactions are relatively small (.20 apiece) and can be combined to cover transaction such as recording the purchase of a song, video, rental, or other protected data streams.
How XerialOS uses #blockchain .
Secure transactions built using Xerial technology utilize a #hyperledgerfabricto complete transactions between nodes, as well as between parties or organizations and parties and nodes.
Picture it like this –
1. Between nodes: Two example nodes within an application could be a stream request and the database where the content resides that will be streamed. The transaction speeds (~ 15 per second) are sluggish, but create an unaltered record which can be used to validate say a data shard within the nodes.
2. Parties and Organizations: defined as billing and licensing between the service provider and the recipient of the service provided.
3. Parties and nodes: A feature built into the framework where the recipient interacts with a module to login to a service record where the app checks to make sure there are no forks or branches in the ledger, prior to authorizing a function.
Xerial is designed to request a Blockchain to be stored in an Linux Foundation’s Hyperledger blockchain with a secure connection between the licensing node of the application and the viewer of the content. This is simply done by “receiving the original data from the transaction and using it to secure an unaltered license built off the transaction. The cost for storing transactions are relatively small (.20 apiece) and can be combined to cover transaction such as recording the purchase of a song, video, rental, or other protected data streams.
When Xerial assembles each of a data store’s contents on the client app, the stored data is is licensed by the end-user and becomes a “Party” in the hyper-ledger fabric recorded ledger transaction, prior to the unlocked view or licensed stream is opened. The recorded transaction becomes part of a collection of transactions stored in the ledger and are used to show that the parties transaction is validated. When a party transfers this license to another party, there becomes a fork/branch in the ledger that our software detects as a transfer of license, thus disabling the original users access to that stream.
To prevent counterfeiting, of streaming content, each stream has its own PISC to identify it within the ledger and only the parties involved in the transaction can open a data stream from their device. We have designed an ai algorithm to identify which codes are already used in the system and when a new data-store is requested, a new PISC is generated by the system with the option to store a license in the ledger.
Although blockchain records are not unalterable as forks are possible, blockchains may be considered secure by design and exemplify a distributed computing system with high Byzantine fault tolerance. Transactions are trackable and can never be emulated or reverse engineered against the original data-record stored within the Hyperledger Fabric.
When Xerial assembles each of a data store’s contents on the client app, the stored data is is licensed by the end-user and becomes a “Party” in the hyper-ledger fabric recorded ledger transaction, prior to the unlocked view or licensed stream is opened. The recorded transaction becomes part of a collection of transactions stored in the ledger and are used to show that the parties transaction is validated. When a party transfers this license to another party, there becomes a fork/branch in the ledger that our software detects as a transfer of license, thus disabling the original users access to that stream.
To prevent counterfeiting, of streaming content, each stream has its own PISC to identify it within the ledger and only the parties involved in the transaction can open a data stream from their device.
Blockchains are typically managed by a peer-to-peer network for use as a publicly distributed ledger, where nodes collectively adhere to protocol to communicate and validate new blocks. Although blockchain records are not unalterable as forks are possible, blockchains may be considered secure by design and exemplify a distributed computing system with high Byzantine fault tolerance.
The code and the queried requests contained therein exist across the distributed, decentralized blockchain network. Transactions are trackable and can never be emulated or reverse engineered against the original data-record stored within the Hyperledger Fabric. This builds the advantage of better performance in the use of data shards for better traffic flow, while also securing the dynamic assembly of the product or service experience at the user interface through a client app, versus loading the server with a rendered experience and trying to push it to multiple clients at the same time.
Press play to have the following section narrated.
What is a product identifier like a PISC? In its simplest form, it is an alpha numeric string that can be used to identify a product and its associated data in a location either physically or virtually in analog or digital form.
Using the QR Code® to create a Product Identifying Serial Code™ (PISC™) is groundbreaking and changing the face of retail. Many don’t realize that a PISC can be made up of any type of 1d or 2d barcode, and more important, are at the heart of Augmented Reality information stores that map to the future of the Omni channel marketing platform.
A (PISC) is a data store identifier that uses a serial code, either numeric or alphanumeric to identify remote information stores. SerialCodes use the PISC code™ much like a UPC-A, SKU, or other identifier to locate information stores related to a specific product at either the SKU level or individual level. The Serial platform embodies the simplicity of other Merchant Management Solutions or (MMS), similar to the retailer point-of-sale system. The primary exception is that the Point of Sale under Serial, displays an image, video or other graphical representation of the product associated with its PISC and is displayed at the same time the product’s data is displayed. The difference is by delivering a richer experience to the client about the products being queried and displayed.
Through the simultaneous use of multiple independently managed data stores transmitted directly to the consumer through the consumer facing app/UI, the platform can manage heavier loads of simultaneous data streams through its use of sharding. This method opens up the ability to put the point of sale system, organically linking the product or service, directly from the product or service packaging, into areas never before possible. This was primarily due to the limitations of the hardware required to run the POS system from within the retailers brick and mortar location. It can now be run from virtually any mobile device.
On-demand data is continuously made available to the client facing app, long after the QR Code® has been published, using dynamically assembled data stores, creating post sale interaction opportunities between the brand manufacturer and the client.
The many kinds of information Xerial can simultaneously manage at the individual product level. A great example of the simultaneous management of these features is illustrated using a vehicle identifier such as the vehicle VIN (Information related to that specific vehicle) as well as simultaneous data stores that are used to identify the generalized view of the vehicle model feature list. While both sets of information are relevant to the consumer, each carry a separate set of values that drive the consumers decision making.
Think of Xerial like this; a single PISC used for managing the individual data stores related to a specific vehicle, i.e., remaining oil life or station shortcuts on the vehicles sound system. The other dataset is model specific data such as type of oil 10W40, available Radio services, i.e., on-Star® / SiriusXM® Satellite Radio or other information relevant to the overall specification.
The platform manages both sets of data across several industries represented on the primary Xerial Assembler™ page.
Xerial Codes transport information stored in the respective data record, relevant to the Vehicle while managing and disseminating that information to multiple users at the same time. It’s much like how a social media platform is built around the “Wheel and Spoke” Network architecture, while remaining platform/device agnostic.
We saw that while merchants use the traditional SKU-based register point of sale to locate products within the retail supply chain, we could design a b-Channel solution to provide access to information stores that were targeted to the consumer in a Merchant Managed Platform (MMS) where the deliverables were created to manage the consumer experience.
Using QR Codes® to create PISCs™
Product identifying Serial Codes are essentially product identifiers stored in a serial code, that is transmitted over a network to access data-stores holding content uploaded by a first user, holding the administrator role to upload and store data related to a specific product that will be accessed by anyone scanning the code (the second user) to view that uploaded content related to that product on their own device.
There are many ways to create (PISCs) product identifying serial codes. A popular method today is using QR Codes®. By no means is this the only way to identify a product, but identifiers have been used for decades by inventory managers, and the POS system to calculate things like location, order supply, price, sale and similar.
A serial Identifier can be placed on a sticker, a shelf-edge tag, the physical product, its packaging, or other methods that associate the Identification of the product and deliver that information to the requester. The difference is that Xerial identifies the information in multiple forms including photo’s, brand identity, video, infographic and any other form of data that can be stored in the data-record/database and delivered into a user experience that pulls all these data points into a deeper experience with the branded product.
For example – QR Codes®, which are considered 2D barcodes means they are read in four directions “Up, Left, Right, Down” as specified by an algorithm used in the program that identifies and captures electrical signals from a CCD (Charge Coupled Device) or CMOS image sensor on the mobile phone in a predefined sequence stored in the program’s algorithm.
To understand how a CMOS or CCD Image sensor works, Google® it.
The scanning algorithm, or Matrix Process, simply measures the element’s charge package or in laymen’s terms, each block of eight numbers “1,2, 4, 8, 16, 32, 64, 128” as either marked or unmarked and adds the marked nodes together. This added sum is converted into HEX or decimal values for an ASCII character, just like what you type in a browser address bar, which in return, when read in sequence, tell the browser the location of the information to display.
The array’s are assembled together in a snake like pattern and read by the algorithm to chain together the different blocks to read and decode each block of eight number arrays to convert to its hex value. The QR code can grow to around 4000+ potential different character possibilities for inputting very long data strings or codes.
| Character | Hex Value |
|---|---|
| f | 66 |
| g | 67 |
| h | 68 |
| i | 69 |
To get the number 68 for the first letter of a web URL that holds the data store for that product identifier, you would simply store that number as black boxes in a predefined read pattern to tell the program to convert these marks into data.
Because the code can only be rendered a single time in the sequence, the proper path to the sum would be to mark the following boxes representing the sum values. (4, 64) Which gives you the hex value of the letter h, as used in a web address like http:// to locate the product identifying serial code.
In the case of the XerialCode Identifier, the QR Code (Below Image) holds the following value as the Product Identifier: xerial=maWUkZWkIZQ=.xtem (Ending in our custom security algorithm extension) Each and every XerialCode contains a separate identifier which is generated by the enterprise extension manager at the time of an edition run. Further laws that help protect the id of the XerialCode include the Copyright registration of that PISC with the Library of Congress, increasing the sanctions from the duplication of a code by a bad actor.
“There can be as many data stores that a single barcode is capable of pointing to as there are web addresses on the internet.”
A product identifier is simply a code used to identify an individual product or group of products under a serial code that is either already etched onto the product, printed on the product packaging, or printed on the consumer-facing infographic, marketing material, or printed material related to the product. This covers both physical and virtual products.
A simple way to understand how the platform works is by comparing a smartphone to a POS Cash register where the cash register uses light to scan the barcode. When a consumer scans the product identifier using the camera on their smart device, instead of opening standard ERP-based information stores such as Price, Inventory, Employee ID, warehousing etc., the consumer can pull cloud-based information resources directly into the smart phone for viewing.
Xerial enables the brand holder the tools to create and manage the product data which becomes available to the requester while interacting with that products information directly. It is the organic link between the product and its serial code (What we call the PISC) that enables the linking to the products information stores.
Xerial platform uses this organic association between the published codes and data-stores for additional product details to deliver a richer user experience to the requester through the mobile app assembly of that product specific data.
The platform is an integrated extension of the ERP (Enterprise Resource Planning) system, opening new avenues for presale, point of sale, and post-sale channelization of product marketing and commerce positions, without having to move to new infrastructure.
Barcodes are links to identifiers that point to datastore. Such warehousing can simultaneously exist depending on whose data warehouse you are linked to.
There can be as many data stores that a single barcode is capable of pointing to as there are web addresses on the internet. Xerial is now merging WebOS and MetaOS into a hybrid framework of information management tools that point to a fully managed cloud-based enterprise data management platform for alternative information views on products and services with customizable Augmented Reality Data Tools. (ARDT)
Brand managers are beginning to realize that UPC-A codes (USA version of UPC Codes) are the barcodes that you see in on the back of virtually all packaging sold through POS systems (Think can of Campbell’s® Chicken Soup) have the specific purpose of identifying the product within the MMS, while delivering critical details about the products stock, price, warehouse location etc.
This provides an organic or natural link to the product represented by the barcode used to identify its location in the supply chain. Typical MMS systems only focus on the core aspects of the product lifecycle which include financial, supply, operations, commerce, logistics, manufacturing, and human resource activities.
The Xerial identity mechanism is essentially what has built the global commerce system where barcodes on different types of products like the EAN code for Magazines and other Copyrighted published works, as well as 27 other types of barcodes are used in everything from Banking in Switzerland to ticketing for concerts and train rides.
Barcoding has been used throughout many industries as identifiers to data related to commerce and transactions of those goods and services. All Barcodes can essentially provide the same linking to product information as the QR Code, based upon their built-in purpose to identify a given product through a registered common identifier.
Xerial at its core extends this concept but focuses more on the deliverables targeting the consumer experience. This includes the commerce capability, stock and other features, but also provides a world class backbone to deliver a rich media user experience to a consumer instead of the checkout counter employee, viewing an itemized list of product pricing on a printed transaction receipt. The Xerial product roadmap now includes Ai, mL (Artificial Intelligence and Machine Learning) to recognize and create PISCs without needing the barcode at all.
Xerial is a Patented Universal distribution information platform that manages the assembly and distribution of rich media assets, and delivering them. The platform is developed to enable a focus group to implement new ways of creating and experiencing products through a number of beneficial information gathering techniques.
Xerial was developed around four key components that make this system work with existing products and services the retailer provides. These key components are at the core of the application platform.
- Develop and Patent technology used for viewing universally acceptable, common identifiers to link products to information data stores. This is what is called the PISC or Product Identifying Serial Code.
- Create software tools that enable brand or service providers secure links to data stores capable of delivering rich media like product photos and streaming video/audio content. The user experience must be built in such a way that the experience and QoS (Quality of service) rivals that of other industry leaders. This is called the service backbone where data handlers, and content management techniques are used to deliver your information to the viewer. This makes up the bulk of Xerial’s enterprise suite.
- This service must be built from a framework that supports extensibility to stay modern and allow for customized modules that fit your client’s needs.
- A client viewing app that assembles each of these data stores in a beautiful UI that houses all the features that most modern social media apps feature, with cutting edge features that get your customer to want to interact with brand targeted marketing.
This discovery led us to file for Patent Protection (The 9892440 Patent) for the methods used in our software to compare product identifying serial codes. This was made by research development team, filed in 2014 and Patents were granted in 2018. You can review how PISC’s are used in several of our application designs by going to XerialCode Products links in the menu or visiting the modules below to see the customizable APIs we have or are in the process of developing.
The PISC code, technology design and Patent.
The PISC code technology design and Patent.
Michael Wright, the company founder developed the technology used in PISCs or “Product Identifying Serial Codes” and was granted a US Patent #9892440 for methods used in the software development, that make the functionality possible.
The technology is built around a gatekeeper concept where there are two types of user ID’s to fulfill the actions of comparing the product code. The technology encompasses both the first user (administrator) who first logs-in to the server to upload data, and a second user (customer) who uses his/her smart device to scan and view remote stores of data related to that specific products data. When the code is matched, it acts like a gate that unlocks to enable the next set of instructions to move forward.
A second user ID does have to come from a physical person where data automation requires the second login. The second user could be as simple as an automated script that sends login information over a cellular radio device to the cellular radio tower to identify the radio device on the network. Techniques like this have been used by law enforcement to track a cell phone through triangulating the last known position of that device via cell towers to identify the devices last known location on the network. Feel free to visit the FCC on this subject at the following site: https://www.fcc.gov/oet/ea/granteecode
Any time you turn on the device, it is sending its location to the cell tower, and is just another way to identify which user and which credentials are used to gain access to the product being queried. If the second user does not possess the User A credentials, the system treats the user as a client without administrator rights to that products data store in view mode.
Patents are process oriented, not time oriented.
If a user views data on a TV, they must log into the service and register payment for that service like on-demand movies, monthly subscriptions and content usage, a PC? Log-in when you create your use account to open the PC with or without a passcode, PDA or Tablet, same thing. Logging into a system can also incorporate user credentials that you input by typing on a virtual keyboard on the imaging device or in this case, the LCD/LED screen. This provides the visual feedback most people need to visualize their input.
The proof of concept and traction are that there are hundreds of brand companies already using the technology to provide access to a wealth of product information using the PISC as its product identifier. When an object is identified and a data store related to that product is used to deliver information related to that product, it is using the PISC regardless of how that data is being displayed. Through a browser, an app or as part of a third-party API.
Understanding the framework
Xerial is built on top of a series of Cloud frameworks that utilizes A RESTful API — also referred to as a RESTful web service or REST API — based on representational state transfer (REST), which is an architectural style and approach to communications often used in web services development. This means the APIs can also be built using dynamic languages such as JavaScript (ECMA Script) as well as Python and PHP.
The REST used by browsers can be thought of as the language of the internet. With cloud use on the rise, APIs are being used by cloud consumers to expose and organize access to web services. REST is a logical choice for building APIs that allow users to connect to, manage and interact with cloud services flexibly in a distributed environment. RESTful APIs are used by such sites as Amazon, Google, LinkedIn and Twitter.
A RESTful API uses commands to obtain resources. The state of a resource at any given timestamp is called a resource representation. A RESTful API uses existing HTTP methodologies defined by the RFC 2616 protocol, such as:
GET to retrieve a resource;
PUT to change the state of or update a resource, which can be an object, file or block;
POST to create that resource; and DELETE to remove it.
Data formats the REST API supports include:
application/json (Easier to understand, but limited to addressing modules using standard text and numbers)
application/xml (Supports more than letters and numbers but more difficult syntax)
application/x-wbe+xml
application/x-www-form-urlencoded
multipart/form-data
Xerial passes these methods back to the core framework (Larevel, Yii2, Django for Python related integrations, Pods for Swift, Ruby for extensions to IOS and Android and scores of other objects for use in object oriented programming) transferring information requests back to the host, which responds to the requestor for reassembly on client facing application.
Xerial uses multiple frameworks and creates translators between many of them to manage much of the utility work while enabling its customization modules to be purposed into creating the data-store for each client wanting to use the system generated PISC to link back to the framework.
At the heart of the Xerial architecture is the customization modules, written in Javascript and PHP created to easily save and retrieve data from the SQL Based data store. The primary connection point between the client/server is http which is used in methods similar to creating and managing rich media posts similar to a Tweet for text, or Facebook for Audio, Video, and imaging data streams and handlers. There is much more about how the system creates and manages each transaction between the server and requestor, but that will be posted in the future.
The platform assembles server resources around content that is comprised of modules and extensions that are compiled together into a series of ‘services’ each respectively created for a specific task targeting many areas of commerce with each respective field the content is generated for. As a service, Xerial(ERPe) manages the data load to each using sharding techniques to offset peak loads to server resources. (More to come)
Xerial - Customizable ERPe Modules and Templates (M) Module (T) Template
What is the difference between a (M) Module and a (T) Template? – Modules are single functional utilities that can be used standalone or in combination when used as a component for a template project. A Template is simply a formatted combination of modules that are tied together to develop rich or full applications that require different functions that each module provides. When combined into a template, the functionality is usually designed to provide a series of services for specific segments of a marketplace.
Audio Manager (M) – Input for managing audio content for non-commerce related transactions. Use the audio manager to embed audio file playback functions on any portion of your Pisc. This core API includes advanced playback tools, and GUI or Graphical User Interface elements and function for your app.
Video Manager (M) – Input for managing video content for non-commerce related transactions. Use the Video manager to embed video file playback functions on any portion of your Pisc. This core API includes advanced playback tools, and GUI or Graphical User Interface elements and function for your app.
Advanced Ticketing Services (T) – Simplified tools to create ticketing campaigns that go far beyond standard ticketing services. Inside are a collection of core API tools used to manage event ticketing, attract consumer interest in an event, provide ad-campaign management tools and combine additional features for artists to manage and attract audience participation in events.
Document Object (M) – Text handlers designed to manage the look and feel of fonts, sizing, kern, form etc. Easy to picture this on a forms handler that assembles data for display on documents. Advanced APIs for the placement, formatting, and display handlers of text related information. Over 1500 Fonts and style formatting tools to import or layout manual information.
Dispatch (T) – A series of APIs designed to manage the scheduling, location services and automate pickup and delivery or assets from the retailer offering the service and the customer requesting service. Think one-touch, on demand setup for delivery.
Food Item Services (T) – Labeling information services to provide a deeper look into product ingredients, allergy potential, health and nutritional information tools and linked services for FDA guidelines. Includes all tools and API for inputting data related to everything edible.
Songtracks™ (T) – The assembler environment used to build a musician’s store of selected materials including a collection of Song Tracks, Music Videos, Photographs, SKU, Commerce, and user management of data access by scanning a code printed or displayed on any surface.
Commercial Video Streaming Solutions (T) – The API for managing video on demand, commerce, display management and networking services to optimize video delivery to sources. This includes publishing, copyright, information track and tools for creating preview content for any video track you manage.
VIN – Vehicle Identification Services (T) – for in-vehicle navigation services over Cellular WiFi 5G Packet Technology (CPT)
Boutique – (SMB Solutions Group) (T) – Small business retail tools for the management and sale of small business retail Boutique specialty stores. Employee management tools, reporting, commerce for products, advertising management, sale protocol, content tie-ins, ML based and Ai based merchandising reporting.
Warehousing – Inventory SKU managemen (M) Tools and forms designed to simplify the management of shipping including scheduled internal stock and location management as well as tie-ins for logistics and shipping services from warehouse location to and from customers.
SKU Manager (M) – Our enterprise tool for building products into the ERP-POS system. Brand holders needing to place their products into a cloud-based point of sale need tools to build the description and provide relevant information related to the entered SKUs. The SKU manager enables information disclosure with software that places the product identifier into the cloud, so a smartphone can capture the product and instantly open the description.
Logistics (M) – API for setting up third-party shipping and logistic services. This data is pulled into many of the modules you will need to fill in prior to using in your mobile app.
Restaurant Management (T) – Coming Soon.
Unity Codes (T) – Integrated Charity Module designed for the capture of an items sale to go to a preselected Charity of Choice. Up to In general, you may deduct up to 60% of your adjusted gross income via charitable donations (100% if the gifts are in cash), but you may be limited to 20%, 30% or 50% depending on the type of contribution and the organization (contributions to certain private foundations, veterans organizations, fraternal societies.
Streaming Communication Services (M) – Streaming video functionality for a large variety of modules. From remote teaching to healthcare visits, this tool implements world class APIs to enable full streaming video services between parties.
Information Guide (M) – Software designed to implement interactive training, user manuals, and guide for parties wanting to skip the paper and link directly to multi-types of users with targeted information content. The API supports streaming audio, Video and decorative text. Includes accessibility tools to help individuals with their needs to better participate in the purposed content.
Graphic Manager (M) – This module provides tools to simplify the placement of screen overlays and graphic presentations for multiple templates in the XerialOS ecosystem.
Education & Remote Learning (T) – Coming Soon.
Health & Medical (T) – Coming Soon.
Photo Manager (M) – Coming Soon.
Ad Copy (M) – Advertising campaign tools to present affiliated products and services to display marketing content over an existing app experience. Includes reporting, scheduling, and linking features to measure consumer response to campaigns.
Transact – Banking and Commerce (M) – Approved financial tools for the purchase of goods and services built within the Xerial platform. The financial tools include Square, PayPal, Credit Cards and others.
SMB – Small Business Retail (T) – Coming Soon.
IMS – Inventory Management System (M) – Coming Soon.
POS – Point of Sale Register Services (M) – Tools to enable commerce transactions within the app whether inside or outside of brick-and-mortar locations. A complete set of APIs enabled the module to conduct direct to consumer purchasing from within the application, anywhere the app can be displayed.
SkubaCart (T) – SkubaCart is a combination front-end and backend commerce platform that incorporates product recognition and the POS Point of Sale directly into the product barcodes or identifier. The template was created to enable the simple link to the POS system from a mobile of desktop user environment for the instant purchase and delivery of goods, from any location in or out of the retail supply chain.
Copyright Notices
iTunes® and Safari are trademarks of Apple Computer, Inc. Registered In the USA and other countries.
Opera® is a trademark of Opera Norway AS. Registered in the USA and other countries.
IBM® is a trademark of IBM Inc. Registered in the USA and other countries.
Chrome® is a trademark of Alphabet, Inc. Registered in the USA and other countries.
Explorer® is a trademark of Microsoft Corporation. Registered in the USA and other countries.
Facebook ® is a trademark of Meta. Registered in the USA and other countries
Linked-in® is a trademark of LinkedIn, Inc. Registered in the USA and other countries.
Compuserve® is a trademark of Compuserve, Inc. Registered in the USA.
Campbell’s Soup is a Trademark of Campbell’s Soup Company, registered in the USA and other countries.
On-Star® is a trademark of OnStar LLC, Registered in the USA and other countries.
SiriusXM® is a trademark of SiriusXM Radio, Inc, Registered in the USA and other countries.
QR Code® is a trademark of Denso Wave, Inc. Registered in the USA and other countries.
Twitter® is a trademark of Twitter, Inc. Registered in the USA and other countries.
AOL® is a trademark of Oath, Inc. Registered in the USA and other countries.
Email us or Call
Silicone Valley (408) 944-5994
Silicon Prairie (913) 544-7426
Have Questions? Feel free to reach out and discuss how we can help your business grow.
© 2021, 2022 by datamazing Inc. All rights Reserved. Site Design by Michael Wright