This is the BrainML-X protocols subschema describing interactions with catalog servers. Included are a resource description format, a means to submit resource descriptions to a catalog server, and a means to query a catalog server for resources matching certain criteria. - Resource descriptions describe basic information about a resource, such as URL and technical contact, as well as what the resource contains and how it is accessed. - Catalog submissions send one or more resource descriptions to a catalog server for indexing. Previous authentication is required. - Catalog queries requests URLs for repositories that serve a certain type of data. Full name of person. Email address. Full phone number including country code for non-U.S. locations. Person responsible for the resource, determining its contents and policies, etc.. Person responsible for day to day upkeep and technical management of the resource. Description of a resource suitable as a catalog entry. Short or acronymic name of the resource. Full or expanded / descriptive name of the resource. Information on the cataloging of this resource. Date / time resource first entered into catalog. Date / time resource entry most recently modified. Name or identifier for individual most recently modifying the entry. URL including http:// or other protocol. If this resource is part of a network or array of related resources, perhaps hosted by the same organization, this should be specified here. Description of the overall nature of a resource. The type or format of the resource (online data store, reagent supply house, etc.). Controlled Vocabulary. Description of the available format(s) for the primary contents provided by the resource (if applicable). Short description and/or key words describing resource's neuroscience contents, focus, and significance. This is supplemental or in place of controlled vocabulary selections below. Description of the neuroscience contents of a resource. Keywords describing normal function or disease state relevant to resource's contents and/or mission. Keywords describing brain or body location(s) relevant to resource's contents or mission. Keywords describing brain or body structural component relevant to resource's contents and/or mission. Keywords describing organism(s) relevant to resource's contents and/or mission. Keywords describing technique(s) relevant to resource's contents and/or mission. Keywords describing functional system relevant to resource's contents and/or mission. Keywords describing developmental stage, if any, relevant to resource's contents and/or mission. Keywords describing disease condition, if any, relevant to resource's contents and/or mission. Description of availability of / access to the resource. Is this an open resource, is registration required, or is access restricted to a particular community, or is this a private resource? Controlled vocabulary. License agreement, if any, restricting (re)use or redistribution of the data or software tool or other content provided by the resource. The main interface for obtaining primary data from the resource. Designated method for software to access data from the resource. Does this resource use terminology that is shared, open, closed, or otherwise situated? Description of the terminology used. Evaluation of the resource's utility. Estimate of how central this resource is among others providing the same type of content. Two-sentence free-text critical evaluation of the utility of this resource. Additional comments on the resource. (DEVELOPMENT) Comments on the description structure, controlled vocabulary, etc. used by the catalog itself. Catalog query. Catalog response. Return component for catalog_response. URL to repository site root. Catalog submission wrapper. The contents are given as one or more entries under this element. Catalog update wrapper. The contents are given as one or more entries under this element. Catalog submission acknowledgement, which includes a repetition of the user name and identifier given with the submission, together with a status indicator. Child submitted_entity elements contain information on the individual components of the submission.. ID assigned by the server, which may be used to uniquely identify the submission (on this server). If the value "FAILED" is received, the submission failed, and 'error' elements under this one specify the reasons.