|-->
  <servers>
    <!-- server
     | Specifies the authentication information to use when connecting to a particular server, identified by
     | a unique name within the system (referred to by the 'id' attribute below).
     |
     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
     |       used together.
     |
    <server>
      <id>deploymentRepo</id>

    protected static final String USER_TYPE = "A";

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    /** Login assistance helper for managing user authentication and session. */
    @Resource

////

That extra info will be added as-is to the output **JSON Schema** for that model, and it will be used in the API docs.

//// tab | Pydantic v2

In Pydantic version 2, you would use the attribute `model_config`, that takes a `dict` as described in <a href="https://docs.pydantic.dev/latest/api/config/" class="external-link" target="_blank">Pydantic's docs: Configuration</a>.

        assertEquals(maxAttributes, decoded.getAttributes());
    }

    @Test
    @DisplayName("Test with various file attributes")
    void testVariousFileAttributes() {
        // Test common file attribute combinations
        int[] attributes = { 0x00000001, // FILE_ATTRIBUTE_READONLY
                0x00000002, // FILE_ATTRIBUTE_HIDDEN
                0x00000004, // FILE_ATTRIBUTE_SYSTEM

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    // keeping parsed request parameters, normal texts or uploaded files

    // ===================================================================================
    //                                                                           Attribute
    //                                                                           =========
    @Resource
    private BadWordService badWordService;
    @Resource
    private BadWordPager badWordPager;

    /**

     */
    public RoleQueryHelper() {
        super();
    }

    private static final Logger logger = LogManager.getLogger(RoleQueryHelper.class);

    /**
     * The key for user roles in the request attribute.
     */
    protected static final String USER_ROLES = "userRoles";

    /**
     * The cached cipher for encryption and decryption.
     */
    protected CachedCipher cipher;

    /**

        @DisplayName("DosFileFilter wildcard and attributes are preserved through unwrap")
        void dosFileFilter_preservesFieldsThroughUnwrap() throws Exception {
            // Test with various wildcard patterns and attribute masks
            String[] wildcards = { "*.txt", "test*", null };
            int[] attributes = { 0x10, 0x20, 0x07 };

            for (int i = 0; i < wildcards.length; i++) {

    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="metadata" java.clone="deep">
      <name>Metadata</name>
      <version>1.0.0+</version>
      <fields>
        <field xml.attribute="true" xml.tagName="modelVersion">
          <name>modelVersion</name>
          <version>1.1.0+</version>
          <type>String</type>
          <description>The version of the underlying metadata model.</description>

#### Daten-„Schema“

Der Begriff „Schema“ kann sich auch auf die Form von Daten beziehen, wie z. B. einen JSON-Inhalt.

In diesem Fall sind die JSON-Attribute und deren Datentypen, usw. gemeint.

#### OpenAPI und JSON Schema