CLI Command Design: Create a Trust Claim (subcommand: claim)

[harlantwood]

Usage

Create Claims

trust claim --help

Usage: trust-claim [options]

  Options:

    -h, --help                   output usage information
    --creator <creator>          DID or URL of claim creator
    --target <target>            DID or URL of claim target
    --tags <tag1, tag2>          Rating tags (at least 1 tag is required)
    --description <description>  Rating description
    --extra key=value           Extra data (can be used multiple times)
    --value <value>              Rating weight in the range 0..1
    --algorithm <algorithm>      Signing algorithm
    --private-key <key>          Private key
    --target-format <format>     opentrustclaim | reputon | trustatom | trustclaim 
    --write <store>              stdout | file | ipfs 

Note: add OpenTrustClaim fields as top level --options.

* reputons: https://www.rfc-editor.org/rfc/rfc7071

[ocarissa]

@harlantwood The original CLI command design - Issue #6 is now broken into:

• CLI Command Design: Create a Trust Claim (subcommand: claim) #6
• CLI Command Design: Retrieve a Trust Claim (subcommand: graph)  #7
• CLI Command Design: JSON - Get Claim ID #8

[dauphin3]

should all these args/flags be required? for now I have description and value as optional

[harlantwood]

Target is the only one that is required. The others are optional, some are not needed, like extra, and others have smart defaults.
@dauphin3

[dauphin3]

this command is meant to return a JSON-LD as a type serde_json::Value
is that correct?

[harlantwood]

If
--target-format trustatom
And
--write stdout
Then just a JSON string, canonicalized (keys sorted) and minified.