Pivot Structure Modeling and Deploy

https://github.com/xuemen/psmd
Admin
PSMD trains personnel in pivot structure modeling and deployment to adapt to Distributed Autonomous...
Tokens:1,383
Snippets:6
Trust Score:3.2
Update:1 year ago
Show doc for...
Tokens:
Raw
### Handling Deployments with PSMD CLI (Node.js)

Source: https://github.com/xuemen/psmd/blob/master/src/README.md

These commands interact with the `deploy.js` module. `node deploy id` processes deployment metadata to generate Markdown and HTML documentation, and upon successful completion, produces COD metadata. The `node deploy` command likely triggers a general deployment process without a specific ID.

```Shell
node deploy id
```

```Shell
node deploy
```

--------------------------------

### Processing Models with PSMD CLI (Node.js)

Source: https://github.com/xuemen/psmd/blob/master/src/README.md

This command utilizes the `model.js` module to process COM metadata, generating corresponding Markdown and HTML documentation. It requires COM metadata as input.

```Shell
node model id
```

--------------------------------

### Managing Terms with PSMD CLI (Node.js)

Source: https://github.com/xuemen/psmd/blob/master/src/README.md

These commands interact with the `term.js` module of the PSMD tool. `node term 1` reads `term.1.yaml`, hashes its text to generate an ID, and saves it as `term.id.yaml`. `node term all` combines term and termset metadata into `allterm` metadata. `node term term id` converts individual term metadata into Markdown and HTML. `node term termset id` converts termset metadata into Markdown and HTML.

```Shell
node term 1
```

```Shell
node term all
```

```Shell
node term term id
```

```Shell
node term termset id
```

--------------------------------

### Initial COM Data Structure Definition in PSMD (YAML)

Source: https://github.com/xuemen/psmd/blob/master/data/README.md

This YAML snippet outlines the initial data structure for a 'Community Model' (COM) in the PSMD system. It includes fields for name, ID, modeler information (name, ID, COM, IRI), and interface mappings. The 'item' section is structured with 'level0' for constant and loop terms, and 'level1' and 'level2' for upgradeable options, indicating a hierarchical and revisable model.

```YAML
name:
id:
modeler:
  name:
  id:
  COM:
  IRI: //代替其它字段
interface:
  <term.termid.entity.1>: value
  <term.termid.entity.2>: value
  <term.termid.asset.1>: value
  <term.termid.term.1>: value
  <term.termid.event.1>: value
  <term.termid.localid.1>: value
item:
  level0:
    const: //不可修订条款
      - termid:
        map:
        readme: |
      - termid:
    loop: //自修订条款
      - termid:
        map:
        readme: |
      - termid:
  level1:
    - upgradeby:
      option:
        - termid:
          map:
          readme: |
        - termid:
    - upgradeby: //对于开源信息可以解决的，可以用readme说明而不列出具体term。
      readme:
  level2:
    - upgradeby:
      option:
        - termid:
          map:
          readme: |
        - termid:
```

--------------------------------

### Proposed COM Data Structure Definition in PSMD (YAML)

Source: https://github.com/xuemen/psmd/blob/master/data/README.md

This YAML snippet presents a revised proposal for the 'Community Model' (COM) data structure in PSMD. It retains core fields like name, ID, modeler, and interface. The 'termmaker' section consolidates 'const' and 'loop' terms, and introduces 'level1' and 'level2' for upgradeable options, streamlining the previous 'item' structure. A top-level 'termid' field is also noted.

```YAML
name:
id:
modeler:
  name:
  id:
  COM:
  IRI: //代替其它字段
interface:
  <term.termid.entity.1>: value
  <term.termid.entity.2>: value
  <term.termid.asset.1>: value
  <term.termid.term.1>: value
  <term.termid.event.1>: value
  <term.termid.localid.1>: value
termmaker:
  const: //不可修订条款
    - termid:
      map:
      readme: |
    - termid:
  loop: //自修订条款
    - termid:
      map:
      readme: |
    - termid:
  level1:
    - upgradeby:
      option:
        - termid:
          map:
          readme: |
        - termid:
    - upgradeby: //对于开源信息可以解决的，可以用readme说明而不列出具体term。
      readme:
  level2:
    - upgradeby:
      option:
        - termid:
          map:
          readme: |
        - termid:
termid: // not term maker
```

--------------------------------

### Defining Term Data Structure in PSMD (YAML)

Source: https://github.com/xuemen/psmd/blob/master/data/README.md

This YAML snippet defines the structure for a 'term' in the PSMD system. It includes fields for name, ID, interface mappings for various entities (entity, asset, term, event, localid), and an 'item' array for nested terms with their own local IDs, text, upgradeby rules, and specific mappings. It also defines 'depend', 'together', and 'effect' sections to link terms to errors and specify their impact.

```YAML
name:
id:
interface:
  <term.termid.entity.1>: value
  <term.termid.entity.2>: value
  <term.termid.asset.1>: value
  <term.termid.term.1>: value
  <term.termid.event.1>: value
  <term.termid.localid.1>: value
item:
  - localid:
    text: |
    termid: 
    upgradeby: // localid.localid.....localid
    map:
      <term.termid.entity.1>: <term.termid.entity.1>
      <term.termid.entity.2>: <term.termid.entity.2>
      <term.termid.asset.1>: <term.termid.asset.1>
      <term.termid.term.1>: <term.termid.term.1>
      <term.termid.event.1>: <term.termid.event.1>
      <term.termid.localid.1>: <term.termid.localid.1>
readme: |
depend:
  - errorid:
    percent:
    map:
        <term.termid.entity.1>: <term.termid.entity.1>
    text: | 
together:
  - errorid:
    percent:
    map:
        <error.errorid.entity.1>: <term.termid.entity.1>
    text: |
effect:
  - errorid:
    percent:
    map:
        <error.errorid.entity.1>: <term.termid.entity.1>
    text: |
```
Tokens:
Raw