add docs for xml comment inclusion for schemagen

Author: gregsdennis

_docs/path/basics.md

@@ -7,9 +7,9 @@ permalink: /path/:title/
 icon: fas fa-tag
 order: "02.1"
 ---
-JSON Path is a query language for JSON documents inspired by what XPath provides for XML documents.  It was [originally proposed](https://goessner.net/articles/JsonPath/) by Matt Goëssner, and now a [specification](https://github.com/ietf-wg-jsonpath/draft-ietf-jsonpath-base) is in progress.
+JSON Path is a query language for JSON documents inspired by what XPath provides for XML documents.  It was [originally proposed](https://goessner.net/articles/JsonPath/) by Matt Goëssner and is now an IETF specification: [RFC 9535](https://www.rfc-editor.org/rfc/rfc9535.html).
 
-Version 0.5.x is aligned with the specification as of the end of April 2023, plus additional support for the following features, which were not included in the specification:
+The library was promoted to version with the release of the specification, and also includes additional support for the following features, which the specification team passed on:
 
 - arithmetic operations in expressions
 - `in` operator in expressions

_docs/schema/schemagen/schema-generation.md

@@ -142,6 +142,22 @@ For POCOs, read-only properties and fields will be marked with a `readOnly` keyw
 
 Lastly, property names will either be listed as declared in code (default) or sorted by name.  This is controlled via the `SchemaGenerationConfiguration.PropertyOrder` property.
 
+### XML comment support
+
+In addition to the explicit attributes above, the XML comment `<Summary>` element can be configured to render to a `description` keyword.  Because .Net saves this information into an external XML file instead of into the reflection data, you'll need to have a configuration object and register the XML filename.
+
+```c#
+var config = new SchemaGenerationConfiguration();
+// MyModel is any type from the assembly.  A single registration will
+// cover the entire assembly.
+config.RegisterXmlCommentsFile<MyModel>("MyAssembly.xml");
+
+var schema = new JsonSchemaBuilder.FromType<MyModel>(config).Build();
+```
+
+> Explicitly using the `[Description]` attribute will override XML comments, and XML comments on members will override XML comments on types.
+{: .prompt-info }
+
 ### Nullability {#schema-schemagen-nullability}
 
 There is a discrepancy between how .Net does validation and how JSON Schema does validation that centers primarily around nullable types and the `[Required]` attribute.