DRIVERS-2789 Clean up source file structure

source/client-side-encryption/subtype6.md → source/bson-binary-encrypted/binary-encrypted.md

@@ -1,4 +1,4 @@
-# BSON Binary Subtype 6
+# BSON Binary Encrypted
 
 - Status: Accepted
 - Minimum Server Version: 4.2

source/uuid.md → source/bson-binary-uuid/uuid.md

@@ -1,4 +1,4 @@
-# Handling of Native UUID Types
+# BSON Binary UUID
 
 - Status: Accepted
 - Minimum Server Version: N/A

source/bson-corpus/bson-corpus.md

@@ -37,7 +37,7 @@ pseudo-specification provides such tests.
 ## Specification
 
 The specification for BSON lives at <http://bsonspec.org>. The `extjson` format specification is
-[here](../extended-json.md).
+[here](../extended-json/extended-json.md).
 
 ## Test Plan
 

source/dbref.md → source/bson-dbref/dbref.md

@@ -1,4 +1,4 @@
-# Handling of DBRefs
+# BSON DBRef
 
 - Status: Accepted
 - Minimum Server Version: N/A

source/bson-decimal128/decimal128.md

@@ -1,4 +1,4 @@
-# BSON Decimal128 Type Handling in Drivers
+# BSON Decimal128
 
 - Status: Accepted
 - Minimum Server Version: 3.4

source/objectid.md → source/bson-objectid/objectid.md

@@ -1,4 +1,4 @@
-# ObjectID format
+# BSON ObjectID
 
 - Status: Accepted
 - Minimum Server Version: N/A

source/client-side-encryption/client-side-encryption.md

@@ -99,7 +99,7 @@ A local process the driver communicates with to determine how to encrypt values
 
 This term, spelled in all-lowercase with an underscore, refers to the client-side field-level-encryption dynamic library
 provided as part of a MongoDB Enterprise distribution. It replaces [mongocryptd](#mongocryptd) as the method of
-[marking-up a database command for encryption](./subtype6.md#intent-to-encrypt).
+[marking-up a database command for encryption](../bson-binary-encrypted/binary-encrypted.md#intent-to-encrypt).
 
 See also:
 
@@ -108,8 +108,8 @@ See also:
 
 **ciphertext**
 
-One of the data formats of [BSON binary subtype 6](./subtype6.md), representing an encoded BSON document containing
-encrypted ciphertext and metadata.
+One of the data formats of [BSON binary encrypted](../bson-binary-encrypted/binary-encrypted.md), representing an
+encoded BSON document containing encrypted ciphertext and metadata.
 
 **FLE**
 
@@ -258,7 +258,7 @@ connect to [mongocryptd](#mongocryptd) and instead rely on [crypt_shared](#crypt
 
 [crypt_shared](#crypt_shared) is a dynamically-loaded C++ library providing query analysis for auto-encryption. It
 replaces [mongocryptd](#mongocryptd) for performing query analysis to -
-[mark-up sensitive fields within a command](./subtype6.md#intent-to-encrypt).
+[mark-up sensitive fields within a command](../bson-binary-encrypted/binary-encrypted.md#intent-to-encrypt).
 
 Drivers are not required to load and interact with [crypt_shared](#crypt_shared) directly. Instead, they inform
 [libmongocrypt](#libmongocrypt) where to find [crypt_shared](#crypt_shared) and [libmongocrypt](#libmongocrypt) will
@@ -305,7 +305,7 @@ Drivers MAY deviate the spelling of option names to conform to their language's
 in an idiomatic way (e.g. keyword arguments, builder classes, etc.).
 
 Drivers MAY use a native UUID type in place of a parameter or return type specified as a BSON binary with subtype 0x04
-as described in [Handling of Native UUID Types](../uuid.md).
+as described in [Handling of Native UUID Types](../bson-binary-uuid/uuid.md).
 
 ### MongoClient Changes
 
@@ -1791,7 +1791,7 @@ struct {
 }
 ```
 
-See [Driver Spec: BSON Binary Subtype 6](./subtype6.md) for more information.
+See [Driver Spec: BSON Binary Encrypted](../bson-binary-encrypted/binary-encrypted.md) for more information.
 
 ### JSONSchema "encrypt"
 

source/client-side-encryption/subtype6.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `subtype6.md <subtype6.md>`_.  
+  `subtype6.md <../bson-binary-encrypted/binary-encrypted.md>`_.  

source/client-side-operations-timeout/client-side-operations-timeout.md

@@ -91,8 +91,8 @@ The `timeoutMS` option applies to all operations defined in the following specif
 - [CRUD](../crud/crud.md)
 - [Change Streams](../change-streams/change-streams.md)
 - [Client Side Encryption](../client-side-encryption/client-side-encryption.md)
-- [Enumerating Collections](../enumerate-collections.md)
-- [Enumerating Databases](../enumerate-databases.md)
+- [Enumerating Collections](../enumerate-collections/enumerate-collections.md)
+- [Enumerating Databases](../enumerate-databases/enumerate-databases.md)
 - [GridFS](../gridfs/gridfs-spec.md)
 - [Index Management](../index-management/index-management.md)
 - [Transactions](../transactions/transactions.md)

source/crud/bulk-write.md

@@ -505,8 +505,8 @@ operation should be performed as its value. The documents have the following for
 }
 ```
 
-If the document to be inserted does not contain an `_id` field, drivers MUST generate a new [`ObjectId`](../objectid.md)
-and add it as the `_id` field at the beginning of the document.
+If the document to be inserted does not contain an `_id` field, drivers MUST generate a new
+[`ObjectId`](../bson-objectid/objectid.md) and add it as the `_id` field at the beginning of the document.
 
 #### Update
 

source/dbref.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `dbref.md <dbref.md>`_.  
+  `dbref.md <bson-dbref/dbref.md>`_.  

source/enumerate-collections.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `enumerate-collections.md <enumerate-collections.md>`_.  
+  `enumerate-collections.md <enumerate-collections/enumerate-collections.md>`_.  

source/enumerate-collections.md → source/enumerate-collections/enumerate-collections.md

@@ -133,10 +133,10 @@ All methods:
 - MAY allow the `cursor.batchSize` option to be passed.
 - SHOULD allow the `comment` option to be passed.
 - MUST apply timeouts per the
-  [Client Side Operations Timeout](./client-side-operations-timeout/client-side-operations-timeout.md) specification.
+  [Client Side Operations Timeout](../client-side-operations-timeout/client-side-operations-timeout.md) specification.
 
 All methods that return cursors MUST support the timeout options documented in
-[Client Side Operations Timeout: Cursors](./client-side-operations-timeout/client-side-operations-timeout.md#cursors).
+[Client Side Operations Timeout: Cursors](../client-side-operations-timeout/client-side-operations-timeout.md#cursors).
 
 #### Getting Collection Names
 

source/enumerate-databases.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `enumerate-databases.md <enumerate-databases.md>`_.  
+  `enumerate-databases.md <enumerate-databases/enumerate-databases.md>`_.  

source/enumerate-databases.md → source/enumerate-databases/enumerate-databases.md

@@ -99,7 +99,7 @@ backwards compatibility when adding new methods.
 All methods SHOULD be implemented on the MongoClient object.
 
 All methods MUST apply timeouts per the
-[Client Side Operations Timeout](./client-side-operations-timeout/client-side-operations-timeout.md) specification.
+[Client Side Operations Timeout](../client-side-operations-timeout/client-side-operations-timeout.md) specification.
 
 #### Enumerating Full Database Information
 
@@ -210,8 +210,9 @@ to be expanded to support this option.
 
 ## Design Rationale
 
-The design of this specification is inspired by the [Collection Enumeration](./enumerate-collections.md) and
-[Index Management](./index-management/index-management.md) specifications. Since most drivers already implement a
+The design of this specification is inspired by the
+[Collection Enumeration](../enumerate-collections/enumerate-collections.md) and
+[Index Management](../index-management/index-management.md) specifications. Since most drivers already implement a
 `listDatabases` command helper in some fashion, this spec is flexible when it comes to existing APIs.
 
 ## Backwards Compatibility

source/extended-json.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `extended-json.md <extended-json.md>`_.  
+  `extended-json.md <extended-json/extended-json.md>`_.  

source/extended-json.md → source/extended-json/extended-json.md

@@ -109,7 +109,7 @@ ______________________________________________________________________
 
 #### Representation of Non-finite Numeric Values
 
-Following the [Extended JSON format for the Decimal128 type](./bson-decimal128/decimal128.md#to-string-representation),
+Following the [Extended JSON format for the Decimal128 type](../bson-decimal128/decimal128.md#to-string-representation),
 non-finite numeric values are encoded as follows:
 
 | **Value**          | **String**  |
@@ -217,9 +217,9 @@ parsing JSON numbers:
 
 #### Special rules for parsing `$uuid` fields
 
-As per the [UUID specification](uuid.md), Binary subtype 3 or 4 are used to represent UUIDs in BSON. Consequently, UUIDs
-are handled as per the convention described for the `Binary` type in the [Conversion table](#conversion-table), e.g. the
-following document written with the MongoDB Python Driver:
+As per the [UUID specification](../bson-binary-uuid/uuid.md), Binary subtype 3 or 4 are used to represent UUIDs in BSON.
+Consequently, UUIDs are handled as per the convention described for the `Binary` type in the
+[Conversion table](#conversion-table), e.g. the following document written with the MongoDB Python Driver:
 
 ```javascript
 {"Binary": uuid.UUID("c8edabc3-f738-4ca3-b68d-ab92a91478a3")}
@@ -238,7 +238,7 @@ is transformed into the following (newlines and spaces added for readability):
 
 > [!NOTE]
 > The above described type conversion assumes that UUID representation is set to `STANDARD`. See the
-> [UUID specification](uuid.md) for more information about UUID representations.
+> [UUID specification](../bson-binary-uuid/uuid.md) for more information about UUID representations.
 
 While this transformation preserves BSON subtype information (since UUIDs can be represented as BSON subtype 3 *or* 4),
 base64-encoding is not the standard way of representing UUIDs and using it makes comparing these values against textual
@@ -320,7 +320,7 @@ exception of the DBRef convention, which is accounted for in this spec).
 ## Test Plan
 
 Drivers, tools, and libraries can test their compliance to this specification by running the tests in version 2.0 and
-above of the [BSON Corpus Test Suite](./bson-corpus/bson-corpus.md).
+above of the [BSON Corpus Test Suite](../bson-corpus/bson-corpus.md).
 
 ## Examples
 
@@ -718,7 +718,7 @@ parsed as a normal document and not reported as an error.
   - Clarified parser and generator rules.
 - 2017-02-01: Initial specification version 1.0.
 
-[^1]: This MUST conform to the [Decimal128 specification](./bson-decimal128/decimal128.md#writing-to-extended-json)
+[^1]: This MUST conform to the [Decimal128 specification](../bson-decimal128/decimal128.md#writing-to-extended-json)
 
 [^2]: BSON Regular Expression options MUST be in alphabetical order.
 

source/find_getmore_killcursors_commands.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `find_getmore_killcursors_commands.md <find_getmore_killcursors_commands.md>`_.  
+  `find_getmore_killcursors_commands.md <find_getmore_killcursors_commands/find_getmore_killcursors_commands.md>`_.  

source/find_getmore_killcursors_commands.md → source/find_getmore_killcursors_commands/find_getmore_killcursors_commands.md

@@ -1,4 +1,4 @@
-# Find, getMore and killCursors commands.
+# Find, getMore and killCursors commands
 
 - Status: Accepted
 - Minimum Server Version: 3.2
@@ -120,7 +120,7 @@ The **secondaryOk** flag SHOULD not be set for all follow-up **getMore** and **k
 server keeps the original **secondaryOk** value first set on the **find** command.
 
 More detailed information about the interaction of the **secondaryOk** with **OP_QUERY** can be found in the Server
-Selection Spec [Passing a Read Preference](./server-selection/server-selection.md#passing-read-preference-to-mongos).
+Selection Spec [Passing a Read Preference](../server-selection/server-selection.md#passing-read-preference-to-mongos).
 
 #### Behavior of Limit, skip and batchSize
 
@@ -131,7 +131,7 @@ existing **OP_QUERY** behavior where there is no server-side concept of limit an
 of the limit on the client side and **MUST** send a **OP_KILL_CURSORS** wire protocol message when the limit is reached.
 
 When setting the **batchSize** on the **find** and **getMore** commands the value of **batchSize** **MUST** be based on
-the cursor limit calculations specified in the [CRUD](./crud/crud.md#find) specification.
+the cursor limit calculations specified in the [CRUD](../crud/crud.md#find) specification.
 
 Note that with 5.0, the server-side handling of cursors with a limit has changed. Before 5.0, some cursors were
 automatically closed when the limit was reached (e.g. when running **find** with **limit**), and the reply document did
@@ -452,7 +452,7 @@ The **find** command does not include a readPreference field. To pass a readPref
 This format is general for all commands when executing against a Mongos proxy.
 
 More in depth information about passing read preferences to Mongos can be found in the Server Selection Specification
-[Server Selection Specification](./server-selection/server-selection.md#passing-read-preference-to-mongos).
+[Server Selection Specification](../server-selection/server-selection.md#passing-read-preference-to-mongos).
 
 ## Changelog
 

source/gridfs/tests/README.md

@@ -12,8 +12,8 @@ GridFS. These tests utilize the [Unified Test Format](../../unified-test-format/
 The unified test format allows binary stream data to be expressed and matched with `$$hexBytes` (for uploads) and
 `$$matchesHexBytes` (for downloads), respectively; however, those operators are not supported in all contexts, such as
 `insertData` and `outcome`. When binary data must be expressed as a base64-encoded string
-([Extended JSON](../../extended-json.md) for a BSON binary type), the test SHOULD include a comment noting the
-equivalent value in hexadecimal for human-readability. For example:
+([Extended JSON](../../extended-json/extended-json.md) for a BSON binary type), the test SHOULD include a comment noting
+the equivalent value in hexadecimal for human-readability. For example:
 
 ```yaml
 data: { $binary: { base64: "ESIzRA==", subType: "00" } } # hex 11223344

source/index.md

@@ -2,9 +2,12 @@
 
 - [Atlas Serverless Tests](serverless-testing/README.md)
 - [Authentication](auth/auth.md)
-- [BSON Binary Subtype 6](client-side-encryption/subtype6.md)
+- [BSON Binary Encrypted](bson-binary-encrypted/binary-encrypted.md)
+- [BSON Binary UUID](bson-binary-uuid/uuid.md)
 - [BSON Corpus](bson-corpus/bson-corpus.md)
-- [BSON Decimal128 Type Handling in Drivers](bson-decimal128/decimal128.md)
+- [BSON DBRef](bson-dbref/dbref.md)
+- [BSON Decimal128](bson-decimal128/decimal128.md)
+- [BSON ObjectID](bson-objectid/objectid.md)
 - [Bulk Write](crud/bulk-write.md)
 - [CRUD API](crud/crud.md)
 - [Causal Consistency Specification](causal-consistency/causal-consistency.md)
@@ -17,14 +20,12 @@
 - [Connection String Spec](connection-string/connection-string-spec.md)
 - [Convenient API for Transactions](transactions-convenient-api/transactions-convenient-api.md)
 - [Driver Mantras](./driver-mantras.md)
-- [Enumerating Collections](./enumerate-collections.md)
-- [Enumerating Databases](./enumerate-databases.md)
-- [Extended JSON](./extended-json.md)
+- [Enumerating Collections](enumerate-collections/enumerate-collections.md)
+- [Enumerating Databases](enumerate-databases/enumerate-databases.md)
+- [Extended JSON](extended-json/extended-json.md)
 - [FaaS Automated Testing](faas-automated-testing/faas-automated-testing.md)
-- [Find, getMore and killCursors commands.](./find_getmore_killcursors_commands.md)
+- [Find, getMore and killCursors commands](find_getmore_killcursors_commands/find_getmore_killcursors_commands.md)
 - [GridFS Spec](gridfs/gridfs-spec.md)
-- [Handling of DBRefs](./dbref.md)
-- [Handling of Native UUID Types](./uuid.md)
 - [Index Management](index-management/index-management.md)
 - [Initial DNS Seedlist Discovery](initial-dns-seedlist-discovery/initial-dns-seedlist-discovery.md)
 - [Load Balancer Support](load-balancers/load-balancers.md)
@@ -34,7 +35,6 @@
 - [MongoDB Handshake](mongodb-handshake/handshake.md)
 - [OCSP Support](ocsp-support/ocsp-support.md)
 - [OP_MSG](message/OP_MSG.md)
-- [ObjectID format](./objectid.md)
 - [Performance Benchmarking](benchmarking/benchmarking.md)
 - [Polling SRV Records for mongos Discovery](polling-srv-records-for-mongos-discovery/polling-srv-records-for-mongos-discovery.md)
 - [Read and Write Concern](read-write-concern/read-write-concern.md)
@@ -49,12 +49,12 @@
 - [Server Monitoring](server-discovery-and-monitoring/server-monitoring.md)
 - [Server Selection](server-selection/server-selection.md)
 - [Server Selection Test Plan](server-selection/server-selection-tests.md)
-- [Server Wire version and Feature List](./wireversion-featurelist.md)
+- [Server Wire version and Feature List](wireversion-featurelist/wireversion-featurelist.md)
 - [Sessions Specification](sessions/driver-sessions.md)
 - [Snapshot Reads Specification](sessions/snapshot-sessions.md)
 - [Stable API For Drivers](versioned-api/versioned-api.md)
 - [Transactions Specification](transactions/transactions.md)
 - [URI Options Specification](uri-options/uri-options.md)
 - [Unified Test Format](unified-test-format/unified-test-format.md)
 - [Wire Compression in Drivers](compression/OP_COMPRESSED.md)
-- [Write Commands Specification](./server_write_commands.md)
+- [Write Commands Specification](server_write_commands/server_write_commands.md)

source/objectid.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `objectid.md <objectid.md>`_.  
+  `objectid.md <bson-objectid/objectid.md>`_.  

source/retryable-reads/retryable-reads.md

@@ -84,7 +84,7 @@ the defined name but MAY deviate to comply with their existing conventions.
 
 Drivers MUST verify server eligibility by ensuring that `maxWireVersion` is at least 6 because retryable reads require a
 MongoDB 3.6 standalone, replica set or shard cluster, MongoDB 3.6 server wire version is 6 as defined in the
-[Server Wire version and Feature List specification](../wireversion-featurelist.md).
+[Server Wire version and Feature List specification](../wireversion-featurelist/wireversion-featurelist.md).
 
 The minimum server version is 3.6 because
 
@@ -142,9 +142,9 @@ Most of the above methods are defined in the following specifications:
 
 - [Change Streams](../change-streams/change-streams.md)
 - [CRUD](../crud/crud.md)
-- [Enumerating Collections](../enumerate-collections.md)
+- [Enumerating Collections](../enumerate-collections/enumerate-collections.md)
 - [Enumerating Indexes](../index-management/index-management.md#enumerate-indexes)
-- [Enumerating Databases](../enumerate-databases.md)
+- [Enumerating Databases](../enumerate-databases/enumerate-databases.md)
 - [GridFS Spec](../gridfs/gridfs-spec.md)
 
 #### Unsupported Read Operations

source/run-command/run-command.md

@@ -293,12 +293,13 @@ permit users to change `getMore` field settings at any time during the cursor's
 commands MUST be constructed with the changes to those fields. If that API is offered drivers MUST write tests asserting
 `getMore` commands are constructed with any updated fields.
 
-- See Find, getMore and killCursors commands' section on [GetMore](../find_getmore_killcursors_commands.md#getmore)
+- See Find, getMore and killCursors commands' section on
+  [GetMore](../find_getmore_killcursors_commands/find_getmore_killcursors_commands.md#getmore)
 
 ##### Tailable and TailableAwait
 
 - **See first:** Find, getMore and killCursors commands's section on
-  [Tailable cursors](../find_getmore_killcursors_commands.md#tailable-cursors)
+  [Tailable cursors](../find_getmore_killcursors_commands/find_getmore_killcursors_commands.md#tailable-cursors)
 
 It is the responsibility of the caller to construct their initial command with `awaitData` and `tailable` flags **as
 well as** inform RunCursorCommand of the `cursorType` that should be constructed. Requesting a `cursorType` that does
@@ -313,7 +314,7 @@ ClientSession associated with the cursor MUST be ended and the ServerSession ret
 - See Driver Sessions' section on
   [When sending a killCursors command](../sessions/driver-sessions.md#when-sending-a-killcursors-command)
 - See Find, getMore and killCursors commands' section on
-  [killCursors](../find_getmore_killcursors_commands.md#killcursors)
+  [killCursors](../find_getmore_killcursors_commands/find_getmore_killcursors_commands.md#killcursors)
 
 ##### Client Side Operations Timeout
 

source/server_write_commands.rst

@@ -1,4 +1,4 @@
 
 .. note::
   This specification has been converted to Markdown and renamed to
-  `server_write_commands.md <server_write_commands.md>`_.  
+  `server_write_commands.md <server_write_commands/server_write_commands.md>`_.