RIXML 2.2 element Resource

Abstract	false (This can be used in an instance)
Nillable	false (Instance values cannot use xsi:nil)
Declared Namespaces	xmlns:rixmldt=http://www.rixml.org/2005/3/RIXML-datatypes xmlns:xs=http://www.w3.org/2001/XMLSchema

<xs:element name="Resource">
    <xs:annotation>
        <xs:documentation>Describes the resource that contains the media representation of the research product. For example, can describe a file, URL, or encoded data that represents the product. There can be any number of Resource elements associated with a product. For example, a product may consist of both a PDF document (one resource) and an Excel spreadsheet (another resource), or there could be multiple language versions of the same document (each one a resource).</xs:documentation>
    </xs:annotation>
    <xs:complexType>
        <xs:sequence>
            <xs:element name="Protocol" type="xs:string" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>Indicates the protocol (rules determining format and transmission). This eliminates the need for parsing this information from the URL.</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element ref="Length" minOccurs="0"/>
            <xs:element ref="StatusInfo" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="MIMEType" type="xs:string">
                <xs:annotation>
                    <xs:documentation>Indicates the type of media used to store the content. MIMEType is used to determine the software product(s) that can read the content. MIMETypes are described in RFC 2046.</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Name" type="xs:string" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>The Name element is intended to provide a research consumer with a suggestion on how to store the particular resource, whether is comes via an actual file, embedded data or remote URL. If this RIXML file arrives with a companion file (PDF, Word, text, etc.) representing this resource, then the Name value is used to match the resource with right companion file. If a payload file is embedded data, the Name value is used by the publisher to suggest a file name to the consumer, who may choose to store the embedded data locally. If a payload file is referenced via URL, the Name value is similarly used by the publisher to suggest a file name to the consumer for local storage.</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Comments" type="xs:string" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>Any additional comments that are deemed necessary. For example, which software version is required to open the document? Or, how does this resource relate to the others for this product?</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="URL" type="xs:anyURI" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>Indicates the URL at which the resource can be found.</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="Data" type="xs:base64Binary" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>Used when the content (data) of the research product needs to be included within the RIXML document. The data must be base64-encoded.</xs:documentation>
                </xs:annotation>
            </xs:element>
            <xs:element name="XMLData" minOccurs="0">
                <xs:complexType>
                    <xs:sequence>
                        <xs:any namespace="http://www.xbrl.org/2003/instance" processContents="lax"
                            maxOccurs="unbounded"/>
                    </xs:sequence>
                </xs:complexType>
            </xs:element>
        </xs:sequence>
        <xs:attribute name="resourceID" type="xs:string" use="required">
            <xs:annotation>
                <xs:documentation>The unique identifier of the resource within the product. The implementation of the resourceID is left for the publishers of content to implement as they deem fit. At a minimum, the resourceID is required to be unique within the product(s) it appears under.</xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="language" type="rixmldt:ISO639-2LanguageType" use="optional">
            <xs:annotation>
                <xs:documentation>Indicates the language of the resource, described using the ISO 639-2/T Code. Highly recommended, especially when multiple resources are included that are different translations of the same product. Whereas the language attribute of the Research element represents the language of the metadata describing the Research, the language attribute of the Resource element represents the language of the media representation (often a file) of the product. These two language attributes may be different.</xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="sizeInBytes" type="xs:string" use="optional">
            <xs:annotation>
                <xs:documentation>Indicates the size of the resource in bytes. Could be used by the end user to estimate the download time and storage needs.</xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="primaryIndicator" type="rixmldt:YesNoEnum" use="required">
            <xs:annotation>
                <xs:documentation>Indicates the primary Resource. At least one Resource must be set to Primary.</xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="sequence" type="xs:integer" use="optional">
            <xs:annotation>
                <xs:documentation>If there are multiple Resources, and they should appear in a certain order when the content is published, indicate the desired order by associating the appropriate sequence number to each Resource.</xs:documentation>
            </xs:annotation>
        </xs:attribute>
        <xs:attribute name="type" type="rixmldt:ResourceTypeEnum" use="optional"/>
    </xs:complexType>
</xs:element>

element {}Resource

Source

Documentation