Meta design to enable searching and matching in the free market

williamwang · October 10, 2019, 2:28am

To enable the token searchable and matchable by other parties..is is essential to differentiate header and body just like html did, include metadata in header, attribute and action in body ?

weiwu.zhang · October 11, 2019, 1:44am

This bit of code in the example section of TokenScript demonstrates it:

github.com

AlphaWallet/TokenScript/blob/master/examples/fifa/fifa.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE token  [
        <!ENTITY fifa.en SYSTEM "fifa.en.shtml">
        <!ENTITY style SYSTEM "shared.css">
        ]>
<ts:token xmlns:ts="http://tokenscript.org/2019/05/tokenscript"
          xmlns="http://www.w3.org/1999/xhtml"
          xmlns:xml="http://www.w3.org/XML/1998/namespace"
          xsi:schemaLocation="http://tokenscript.org/2019/05/tokenscript"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          custodian="false"
>
    <ts:name>
        <ts:plurals xml:lang="en">
            <ts:string quantity="one">Ticket</ts:string>
            <ts:string quantity="other">Tickets</ts:string>
        </ts:plurals>
        <ts:plurals xml:lang="es">
            <ts:string quantity="one">Boleto de admisión</ts:string>
            <ts:string quantity="other">Boleto de admisiónes</ts:string>

This file has been truncated. show original

The part to look starts at line 110, which explains how token data is extracted. For example, for the token that is a FIFA ticket, the "locality" value of that token, which translates to City (at line 112), is originated from the token-id, which has value 1 representing Mosco and value 2 representing San Petersburgo.

The example demonstrated how to get attributes from token-id, but there are other ways to get attributes. Look at this example:

github.com

AlphaWallet/TokenScript/blob/master/examples/EntryToken/EntryToken.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE token  [
    <!ENTITY token.en SYSTEM "token.en.shtml">
    <!ENTITY enter.en SYSTEM "enter.en.shtml">
    <!ENTITY icon.en SYSTEM "icon.en.shtml">
    <!ENTITY style SYSTEM "shared.css">
]>
<ts:token xmlns:ts="http://tokenscript.org/2019/05/tokenscript"
          xmlns="http://www.w3.org/1999/xhtml"
          xmlns:xml="http://www.w3.org/XML/1998/namespace"
          xsi:schemaLocation="http://tokenscript.org/2019/05/tokenscript"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          custodian="false"
>
  <ts:name>
    <ts:plurals xml:lang="en">
      <ts:string quantity="one">Ticket</ts:string>
      <ts:string quantity="other">Tickets</ts:string>
    </ts:plurals>
    <ts:plurals xml:lang="es">

This file has been truncated. show original

Observe line 81:

<ts:attribute-type id="locality" syntax="1.3.6.1.4.1.1466.115.121.1.15">`

Its also a locality attribute, but this time its origin is a pure smart contract function call, at line 83. Meaning the function provides the value, not the token-id.

A list of possible token data origins:

Token-ID
Pure Smart Contract call
Attestations
Oracles (including web-oracles)
User input

An engine that searches and matches token might want to look at all data origins except the last, which is the only data origin used solely for user interface generation.

More on that in the document written by Boon:

github.com

AlphaWallet/TokenScript/blob/master/doc/data.md

# Token Attributes

A. I describe how to think of attributes and their origins and mappings as a pipeline below. A useful case to think through is a function origin which returns a GeneralisedTime (so we set as=”utf8”), but the attribute syntax is GeneralisedTime (and hence the JavaScript object is expected to be our standard JavaScript GeneralisedTime class).

B. Based on this, it would be good if we add as=”address”. The matching syntax type should be IA5 String (but Directory String will work too). We can return the JavaScript object as a string or if there’s a suitable syntax that defines it as an address, we can create a simple class to wrap it (in the future?)

C. To preserve precision, Numeric Strings are stored internally as a Big Integer, but returned as a JavaScript string (unless we want to support provide or endorse a big number library. Possibly later?)

D. Note that according to https://tools.ietf.org/html/rfc4517#section-3.3.23, Numeric String is:

NumericString = 1*(DIGIT / SPACE)
DIGIT   = %x30 / LDIGIT       ; "0"-"9"
LDIGIT  = %x31-39             ; "1"-"9"

Attribute as a pipeline:

One way to look at an attribute type and their origin, and (optional) mapping is as a pipeline of 2 or 3 processing stages.

With a mapping:

This file has been truncated. show original

What project are you doing? I'm eager to learn about it and provide relevant information.

Topic		Replies	Views
Attribute Typing Tokenscript Design	1	529	May 24, 2020
TokenScript meeting #40 Tokenscript Design	0	428	July 5, 2020
Weekly design meeting #26 Tokenscript Design	3	489	May 24, 2020
Weekly design meeting #30 Tokenscript Design	8	824	May 18, 2020
Weekly design meeting #17 + #18 Tokenscript Design	0	496	January 7, 2020

Meta design to enable searching and matching in the free market

Related Topics