Changed known value 'hasName' to 'name'

Author: wolfmcnally

papers/bcr-2023-002-known-value.md

@@ -167,7 +167,7 @@ This table documents the Known Value codepoints currently assigned, but is curre
 | 8  | key            | property | Declares the entity identified by the subject holds the private half of the public keys(s) in the object.
 | 9  | dereferenceVia | property | Declares the content referenced by the subject can be dereferenced using the object.
 | 10 | entity         | property | Declares the entity referenced by the subject is specified in the object.
-| 11 | hasName        | property | Declares the the subject is known by the name in the object. | http://xmlns.com/foaf/0.1/name
+| 11 | name        | property | Declares the the subject is known by the name in the object. | http://xmlns.com/foaf/0.1/name
 | 12 | language       | property | Declares the subject is written in the language of the ISO language code object. | http://www.w3.org/1999/02/22-rdf-syntax-ns#langString
 | 13 | issuer         | property | Declares the subject's issuing entity.
 | 14 | holder         | property | Declares the entity to which the subject has been issued.

papers/bcr-2023-006-envelope-attachment.md

@@ -30,12 +30,12 @@ This document uses the following [Known Values](bcr-2023-002-known-value.md):
 
 A Gordian Envelope is specified by the format of its subject and the assertions it MUST or MAY include. For security, Envelope definitions SHOULD reject as invalid any unexpected assertions that are not defined for the Envelope type.
 
-As an example, an Envelope containing a cryptographic seed has a subject that is a byte string containing the seed. It MUST include an `'isA': Seed` assertion to declare its type. A Seed Envelope MAY also include an optional `'hasName'` assertion, an optional `'note'` assertion, and an optional `'date'` assertion:
+As an example, an Envelope containing a cryptographic seed has a subject that is a byte string containing the seed. It MUST include an `'isA': Seed` assertion to declare its type. A Seed Envelope MAY also include an optional `'name'` assertion, an optional `'note'` assertion, and an optional `'date'` assertion:
 
 ```
 Bytes(16) [
     'isA': Seed
-    'hasName': "Dark Purple Aqua Love"
+    'name': "Dark Purple Aqua Love"
     'note': "This is the note."
 ]
 ```
@@ -51,7 +51,7 @@ Bytes(16) [
         'conformsTo': "https://example.com/seed-envelope-attachment/v1"
         'vendor': "com.example"
     ]
-    'hasName': "Dark Purple Aqua Love"
+    'name': "Dark Purple Aqua Love"
     'note': "This is the note."
 ]
 ```
@@ -81,7 +81,7 @@ Bytes(16) [
         'conformsTo': "https://example.com/seed-envelope-attachment/v2"
         'vendor': "com.example"
     ]
-    'hasName': "Dark Purple Aqua Love"
+    'name': "Dark Purple Aqua Love"
     'note': "This is the note."
 ]
 ```

papers/bcr-2023-007-envelope-output-desc.md

@@ -30,7 +30,7 @@ The two Known Values this protocol uses are defined in the [Known Values Registr
 
 * `OutputDescriptor` (class)
 * `outputDescriptor` (property)
-* `hasName` (property)
+* `name` (property)
 * `note` (property)
 
 Note the difference in case of the two known values: `OutputDescriptor` is a type (class), and `outputDescriptor`, is a predicate (property).
@@ -40,16 +40,16 @@ Note the difference in case of the two known values: `OutputDescriptor` is a typ
 The subject of a Bitcoin Output Descriptor Envelope is a text string containing a Bitcoin output descriptor.
 
 * It MUST include an `isA: OutputDescriptor` assertion to declare its type conforming to this document.
-* It MAY include a `hasName` assertion, where the object MUST be a non-empty string.
+* It MAY include a `name` assertion, where the object MUST be a non-empty string.
 * It MAY include a `note` assertion, where the object MUST be a non-empty string.
 
 **Example:**
 
 ```
 "wpkh([37b5eed4/84'/0'/0']xpub6BkU445MSEBXbPjD3g2c2ch6mn8yy1SXXQUM7EwjgYiq6Wt1NDwDZ45npqWcV8uQC5oi2gHuVukoCoZZyT4HKq8EpotPMqGqxdZRuapCQ23/<0;1>/*)" [
-    isA: OutputDescriptor
-    hasName: "Example"
-    note: "This is the note."
+    'isA': OutputDescriptor
+    'name': "Example"
+    'note': "This is the note."
 ]
 ```
 
@@ -61,10 +61,10 @@ A Bitcoin Output Descriptor Envelope MAY be used as the object of an assertion w
 
 ```
 "Example" [
-    outputDescriptor: "wpkh([37b5eed4/84'/0'/0']xpub6BkU445MSEBXbPjD3g2c2ch6mn8yy1SXXQUM7EwjgYiq6Wt1NDwDZ45npqWcV8uQC5oi2gHuVukoCoZZyT4HKq8EpotPMqGqxdZRuapCQ23/<0;1>/*)" [
-        isA: OutputDescriptor
-        hasName: "Example"
-        note: "This is the note."
+    'outputDescriptor': "wpkh([37b5eed4/84'/0'/0']xpub6BkU445MSEBXbPjD3g2c2ch6mn8yy1SXXQUM7EwjgYiq6Wt1NDwDZ45npqWcV8uQC5oi2gHuVukoCoZZyT4HKq8EpotPMqGqxdZRuapCQ23/<0;1>/*)" [
+        'isA': OutputDescriptor
+        'name': "Example"
+        'note': "This is the note."
     ]
 ]
 ```

papers/bcr-2023-009-envelope-seed.md

@@ -21,7 +21,7 @@ The Known Values this protocol uses are defined in the [Known Values Registry](b
 
 * `Seed` (class)
 * `isA` (property)
-* `hasName` (property)
+* `name` (property)
 * `note` (property)
 * `date` (property)
 * `outputDescriptor` (property)
@@ -32,7 +32,7 @@ The Known Values this protocol uses are defined in the [Known Values Registry](b
 An Envelope containing a cryptographic seed has a subject that is a byte string containing the seed.
 
 * It MUST include an `isA: Seed` assertion to declare its type conforming to this document.
-* It MAY include a single `hasName` assertion, where the object MUST be a non-empty string, which MAY have been elided.
+* It MAY include a single `name` assertion, where the object MUST be a non-empty string, which MAY have been elided.
 * It MAY include a single `note` assertion, where the object MUST be a non-empty string, which MAY have been elided.
 * It MAY include a single `date` assertion, where the object MUST be a date conforming to [BCR-2023-008](bcr-2023-008-dcbor-date.md).
 * It MAY include a single `outputDescriptor` assertion, where the object MUST be a Bitcoin output descriptor conforming to [BCR-2023-007](bcr-2023-007-envelope-output-desc.md).
@@ -42,20 +42,20 @@ An Envelope containing a cryptographic seed has a subject that is a byte string
 
 ```
 Bytes(16) [
-    isA: Seed
-    attachment: {
+    'isA': Seed
+    'attachment': {
         "Attachment Data"
     } [
-        conformsTo: "https://example.com/seed-envelope-attachment/v1"
-        vendor: "com.example"
+        'conformsTo': "https://example.com/seed-envelope-attachment/v1"
+        'vendor': "com.example"
     ]
-    date: 2021-02-24T09:19:01Z
-    hasName: "Dark Purple Aqua Love"
-    note: "This is the note."
-    outputDescriptor: "wpkh([37b5eed4/84'/0'/0']xpub6BkU445MSEBXbPjD3g2c2ch6mn8yy1SXXQUM7EwjgYiq6Wt1NDwDZ45npqWcV8uQC5oi2gHuVukoCoZZyT4HKq8EpotPMqGqxdZRuapCQ23/<0;1>/*)" [
-        isA: OutputDescriptor
-        hasName: "Example Descriptor"
-        note: "This is the descriptor's note."
+    'date': 2021-02-24T09:19:01Z
+    'name': "Dark Purple Aqua Love"
+    'note': "This is the note."
+    'outputDescriptor': "wpkh([37b5eed4/84'/0'/0']xpub6BkU445MSEBXbPjD3g2c2ch6mn8yy1SXXQUM7EwjgYiq6Wt1NDwDZ45npqWcV8uQC5oi2gHuVukoCoZZyT4HKq8EpotPMqGqxdZRuapCQ23/<0;1>/*)" [
+        'isA': OutputDescriptor
+        'name': "Example Descriptor"
+        'note': "This is the descriptor's note."
     ]
 ]
 ```

papers/bcr-2024-004-request.md

@@ -43,7 +43,7 @@ The Gordian Transport Protocol is crucial for enabling interoperability and thus
   * **SS Response:** Specific Share
 * **SV Request:** Shares
   * **SS Response:** All Shares
- 
+
 A Request/Response system helps to reduce the complexity of these digital tasks. A user may not be able to find a specific seed or to generate a key along an appropriate derivation path without guidance. A Request/Response system provides that guidance to minimize errors and user frustration alike.
 
 A Request/Response system becomes even more important as tasks are combined together for more complex projects. The [multisig self-sovereign scenario](https://github.com/BlockchainCommons/SmartCustody/blob/master/Docs/Scenario-Multisig.md) is one such example. It demonstrates how to safely secure digital assets using keys on two closely held devices. However, it is too complex for more users. A system built on Requests and Responses that told users what to do as part of an interactive process would be more likely to be successful, as is described in [Improving Multisigs with Request/Response](https://github.com/BlockchainCommons/SmartCustody/blob/master/Docs/Scenario-Multisig-RR.md).
@@ -68,7 +68,7 @@ A function to retrieve a seed looks as follows:
 ]
 ```
 
-The numbers refer to specific functions and specific parameters. They are essentially "known values" for Envelope Expressions. These values are defined in [Format.swift](https://github.com/BlockchainCommons/BCSwiftEnvelope/blob/master/Sources/Envelope/Base/Format.swift) in the [Envelope base code](https://github.com/BlockchainCommons/BCSwiftEnvelope/tree/master/Sources/Envelope/Base). 
+The numbers refer to specific functions and specific parameters. They are essentially "known values" for Envelope Expressions. These values are defined in [Format.swift](https://github.com/BlockchainCommons/BCSwiftEnvelope/blob/master/Sources/Envelope/Base/Format.swift) in the [Envelope base code](https://github.com/BlockchainCommons/BCSwiftEnvelope/tree/master/Sources/Envelope/Base).
 
 The function call is tagged with CBOR tag #40006, which defines it as a `ur:function` and the parameter is defined with CBOR tag #40007, which defines it as a `ur:parameter`. This is represented in `envelope-cli` (and in the examples here) with "«»" for `ur:function` and "❰❱" for `ur:parameter`.
 
@@ -122,18 +122,18 @@ The subject is the seed, while the three assertions describe the seed. The subje
 ```
 Bytes(16) [
         'isA': 'Seed'
-        'hasName': "Dark Purple Peck Vial"
+        'name': "Dark Purple Peck Vial"
         'outputDescriptor': output-descriptor(Map)
 ]
 ```
 
-The `isA` assertion is the required one. The others are optional. 
+The `isA` assertion is the required one. The others are optional.
 
 The output descriptor contains a map structure as described in [BCR-2023-010](https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2023-010-output-descriptor.md).
 
 ## 3. Gordian Transport Protocol: Wrapping a Request
 
-To turn a inquiry for information into a Request requires wrapping the Expression with a `ur:request` subject. 
+To turn a inquiry for information into a Request requires wrapping the Expression with a `ur:request` subject.
 
 Creating the subject for a Request requires the following steps:
 
@@ -184,15 +184,15 @@ request(ARID(7b33b86e)) [
 Digging down instead, here's what the lower-level CBOR of that Request looks like:
 ```
 [
- 
+
  24(40004(40012(
      h'7b33b86e604e3cb5ef9d1675d59c70b6ea7d1f625d062e4d14c4310f2e616cd9'
-   ))), 
-  
- {4: 24("Seed requested by GeneraWallet with note 'Joe wants a copy of the seed'.")}, 
-        
+   ))),
+
+ {4: 24("Seed requested by GeneraWallet with note 'Joe wants a copy of the seed'.")},
+
  {100: [
-        24(40006(100)), 
+        24(40006(100)),
         {24(40007(200)): 24(40001(
           h'ffa11a8b90954fc89ae625779ca11b8f0227573a2f8b4ed85d96ddf901a72cea'
         ))}
@@ -206,46 +206,46 @@ Here's a more detailed look at the CBOR for this `request`:
 /* Array of 3 */
 
 [
- 
+
  /* #1: request(ARID(7b33b86e)) */
 
      /* CBOR tag #24 = byte string */
      /* CBOR tag #40004 = request */
      /* CBOR tag #40012 = ur:arid */
- 
+
  24(40004(40012(
      h'7b33b86e604e3cb5ef9d1675d59c70b6ea7d1f625d062e4d14c4310f2e616cd9'
-   ))), 
+   ))),
+
 
- 
   /* #2: note */
-  
+
      /* map */
      /* Known Value #4 = note */
      /* CBOR tag #24 = byte string */
-  
- {4: 24("Seed requested by GeneraWallet with note 'Joe wants a copy of the seed'.")}, 
- 
+
+ {4: 24("Seed requested by GeneraWallet with note 'Joe wants a copy of the seed'.")},
+
  /* #3: 'body': «getSeed» */
- 
+
      /* map */
      /* Known Value #100 = body */
-     
+
      /* array of 2 */
-       
+
        /* CBOR tag #24 = bytestring */
        /* CBOR tag #40006 = ur:function */
        /* Function #100 = getSeed */
-       
+
        /* CBOR tag #24 = bytestring */
        /* CBOR tag #40007 = ur:parameter */
        /* Parameter #200 = seedDigest */
-       
+
        /* CBOR tag #24 = bytestring */
        /* CBOR tag #40001 = ur:digest */
-       
+
  {100: [
-        24(40006(100)), 
+        24(40006(100)),
         {24(40007(200)): 24(40001(
           h'ffa11a8b90954fc89ae625779ca11b8f0227573a2f8b4ed85d96ddf901a72cea'
         ))}
@@ -267,7 +267,7 @@ To respond to a GTP Request:
 5. Add an object to the 'result' subject containing the Requested data.
 6. Create an assertion under the 'result' assertion that contains 'isA:' and the appropriate data type.
 7. Add additional assertions with any other metadata desired.
-   
+
 The response to the above request thus look as follows:
 
 ```
@@ -285,7 +285,7 @@ Or:
 response(ARID(7b33b86e)) [
     'result': Bytes(16) [
         'isA': 'Seed'
-        'hasName': "Dark Purple Peck Vial"
+        'name': "Dark Purple Peck Vial"
         'outputDescriptor': output-descriptor(Map)
     ]
 ]
@@ -308,7 +308,7 @@ request(ARID(7b33b86e)) [
 response(ARID(7b33b86e)) [
     'result': Bytes(16) [
         'isA': 'Seed'
-        'hasName': "Dark Purple Peck Vial"
+        'name': "Dark Purple Peck Vial"
         'outputDescriptor': output-descriptor(Map)
     ]
 ]