w3c / web-ledger Goto Github PK

It would be really useful to be able to import and use the web-ledger context as an npm package. (Similar to how veres-one-context does it, for example.)

Given that this is a multi-language standard, not just for node, we can organize it by programming language. So, this issue is to:

• add a js/ folder, and put an index.js in there
• add a top level package.json and have main: point to /js/index.js

If there's demand for other programming languages, we can organize them similarly, by language.
So, we'd add a rb/ folder for Ruby (and a top level Gemfile), and so on.

For BTCR audit trail, seeking (but not finding):

• chain (what chain is this on? bitcoin, testnet, or alt satoshi chains like lightcoin, zcash)
• blockHash (alternative to blockHeight)
• transactionIndex (aka index to transaction in block)

etc.

See an example of needs at WebOfTrustInfo/btcr-hackathon-2019#9

The id field in CreateWebLedgerRecord.record needs a special rule that indicates the id property will not change from the core web ledger context and that it must be present. This rule makes it such that new contexts can be used without having to specify the web ledger context -- with only that caveat, i.e. it should improve ergonomics.

From the documents:

EXAMPLE 1: Example genesis block
{
  "@context": "https://w3id.org/web-ledger/v1",
  "id": BLOCK_ID,
  "type": "LedgerConfigurationBlock",
  "ledgerConfig": {
    "id": LEDGER_ID,
    "type": "LedgerConfiguration",
    "name": "example",
    "description": "This is an example ledger.",
    "storageMechanism": STORAGE_DATA_STRUCTURE,
    "consensusAlgorithm": CONSENSUS_ALGORITHM,
  "previousBlock": {
    "hash": "urn:sha256:0000000000000000000000000000000000000000000000000000000000000000"
  },
  "signature": SIGNATURE_VALUE
}

if a genesis block is the first block why does it have a previousBlock?

As a contributor, It would be easier if I could access information about the repo and contributing guides in the repo itself. So, adding repository details, purpose, or usage in a Readme markdown File, and contributing guides in a Contributing markdown file would be helpful.