/**
         * Sets the attributes of the XML node.
         * <p>
         * The provided map will be copied to ensure immutability.
         *
         * @param attributes the map of attribute names to values
         * @return this builder instance
         */
        public Builder attributes(Map<String, String> attributes) {
            this.attributes = attributes;
            return this;
        }

                final SearchResult searchResult = results.next();
                final Attribute attribute = searchResult.getAttributes().get("sAMAccountName");
                if (logger.isDebugEnabled()) {
                    logger.debug("sAMAccountName: {}", attribute);
                }
                if (attribute != null && attribute.get() instanceof String sAMAccountName) {
                    return OptionalEntity.of(sAMAccountName);

                }
            }
        }
        return null;
    }

    /**
     * Gets an attribute value as an integer.
     *
     * @param attributes the named node map of attributes
     * @param name the attribute name
     * @return the attribute value as Integer, null if not found or not parseable
     */

                    if (manifest != null && manifest.getEntries() != null) {
                        final Attributes attributes = manifest.getMainAttributes();
                        if (attributes != null
                                && (attributes.get("Fess-WebAppJar") != null || attributes.getValue("Fess-WebAppJar") != null)) {

{* ../../docs_src/body_nested_models/tutorial005_py310.py hl[2,8] *}

The string will be checked to be a valid URL, and documented in JSON Schema / OpenAPI as such.

## Attributes with lists of submodels { #attributes-with-lists-of-submodels }

You can also use Pydantic models as subtypes of `list`, `set`, etc.:

{* ../../docs_src/body_nested_models/tutorial006_py310.py hl[18] *}

 * from specific HTML tags and attributes.
 * </p>
 *
 * <p>
 * <b>Configuration:</b>
 * </p>
 * <ul>
 *   <li><b>featureMap:</b> A map of features to be set on the DOM parser.</li>
 *   <li><b>propertyMap:</b> A map of properties to be set on the DOM parser.</li>
 *   <li><b>childUrlRuleMap:</b> A map of HTML tag names to attribute names, used
 *       to extract child URLs.</li>

Then you declare your data model as a class that inherits from `BaseModel`.

Use standard Python types for all the attributes:

{* ../../docs_src/body/tutorial001_py310.py hl[5:9] *}


The same as when declaring query parameters, when a model attribute has a default value, it is not required. Otherwise, it is required. Use `None` to make it just optional.

///

/// note

Notice that the input model is still validated.

So, if you want to receive partial updates that can omit all the attributes, you need to have a model with all the attributes marked as optional (with default values or `None`).

{* ../../docs_src/body_nested_models/tutorial005_py310.py hl[2,8] *}

Es wird getestet, ob der String eine gültige URL ist, und als solche wird er in JSON Schema / OpenAPI dokumentiert.

## Attribute mit Listen von Kindmodellen { #attributes-with-lists-of-submodels }

Sie können Pydantic-Modelle auch als Typen innerhalb von `list`, `set`, usw. verwenden:

{* ../../docs_src/body_nested_models/tutorial006_py310.py hl[18] *}

And these models are all sharing a lot of the data and duplicating attribute names and types.

We could do better.

We can declare a `UserBase` model that serves as a base for our other models. And then we can make subclasses of that model that inherit its attributes (type declarations, validation, etc).

All the data conversion, validation, documentation, etc. will still work as normally.