Should the JSON LD Schema require anon ID's for all non-element properties?

[goneall]

For classes like Hash, we require an @id property. If the Hash is inlined within the referenced class and is not referenced externally, the @id is not technically required. Adding the @id requirement adds some unnecessary text in many situations.

Example:

...
      "verifiedUsing": [
        {
          "@id": "_someid",
          "type": "Hash",
          "hashValue": "d301fcd0b7c84c879456eb041af246fbc7edbfea54f6470a859d8bd4073a47b8",
          "algorithm": "SHA256"
        }
      ],
...

...
      "verifiedUsing": [
        {
          "type": "Hash",
          "hashValue": "d301fcd0b7c84c879456eb041af246fbc7edbfea54f6470a859d8bd4073a47b8",
          "algorithm": "SHA256"
        }
      ],
...

[goneall]

In taking another look at the schema, this is not listed as required - closing