Common Criteria Protection Profile Schema Documentation
Index

Grammar Documentation

Namespace: https://niap-ccevs.org/cc/app-vetting/1.0
Root Element: report

Element:

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Defines all html-elements with an optional number of html attributes and descendants.
Content Model ( )* , ( ( TEXT | %html-element ) )*
Attributes:
Attribute Type Use Documentation
TEXT Optional

<element   ns='http://www.w3.org/1999/xhtml' >
<anyName>
<except>
<nsName   ns='https://commoncriteria.github.io/pp/app-vetting/1.0' />
</except>
</anyName>
<a:documentation>
Defines all html-elements with an optional number of html attributes and descendants.
</a:documentation>
<zeroOrMore>
<attribute>
<anyName/>
</attribute>
</zeroOrMore>
<zeroOrMore>
<choice>
<text/>
<ref   name='html-element' />
</choice>
</zeroOrMore>
</element>

Element: Formfactor

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Description of the equipment this intends to run on (eg: Phone, laptop, watch).
Content Model TEXT

<element   name='Formfactor' >
<a:documentation>
Description of the equipment this intends to run on (eg: Phone, laptop, watch).
</a:documentation>
<text/>
</element>

Element: activity

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Activities completed to check this compliance
Content Model summary, transcript ? , tools ?

<element   name='activity' >
<a:documentation>
Activities completed to check this compliance
</a:documentation>
<element   name='summary' >
<a:documentation>
Description of the actions performed with HTML if stylized content is desired
</a:documentation>
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<a:documentation>
Data the represents what happened on a terminal if that was the method of testing
</a:documentation>
<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>
<oneOrMore>
<choice>
<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>
<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<element   name='tools' >
<a:documentation>
Tools used for the evaluation
</a:documentation>
<oneOrMore>
<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>

Element: activity

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model summary, transcript ? , tools ?

<element   name='activity' >
<element   name='summary' >
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<oneOrMore>
<choice>
<element   name='input' >
<text/>
</element>
<element   name='output' >
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<a:documentation>
</a:documentation>
<element   name='tools' >
<oneOrMore>
<element   name='tool' >
<attribute   name='name' />
<optional>
<attribute   name='url' />
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>

Element: address

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Address that does not fit in the standard USA address.
Content Model TEXT

<element   name='address' >
<a:documentation>
Address that does not fit in the standard USA address.
</a:documentation>
<text/>
</element>

Element: app-info

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Meta-data about the app (identification, etc).
Content Model name, %description? , vendor ? , package-identification ? , %version, ( platform )+ , hash ? , signature ? , category ? , apptype ? , Formfactor ? , filename ? %info

<element   name='app-info' >
<a:documentation>
Meta-data about the app (identification, etc).
</a:documentation>
<element   name='name' >
<a:documentation>
Name of the app as given by its vendor.
</a:documentation>
<text/>
</element>
<optional>
<ref   name='description' />
</optional>
<optional>
<element   name='vendor' >
<a:documentation>
Name of the vendor (hopefully as registered in the playstore)
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<a:documentation>
URL of the vendor's main website.
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<choice>
<element   name='us-address' >
<a:documentation>
USA mailing address the vendor is registered to.
</a:documentation>
<element   name='street1' >
<text/>
</element>
<optional>
<element   name='street2' >
<text/>
</element>
</optional>
<element   name='city' >
<data   type='NCName' />
</element>
<element   name='state' >
<data   type='string' >
<param   name='pattern' >
[A-Z]{2}
</param>
</data>
</element>
<element   name='zip-code' >
<data   type='string' >
<param   name='pattern' >
[0-9]{5}(\-[0-9]{4})?
</param>
</data>
</element>
</element>
<element   name='address' >
<a:documentation>
Address that does not fit in the standard USA address.
</a:documentation>
<text/>
</element>
</choice>
</zeroOrMore>
</element>
</optional>
<optional>
<element   name='package-identification' >
<a:documentation>
Package identifier (e.g., Java package name)
</a:documentation>
<text/>
</element>
</optional>
<ref   name='version' />
<oneOrMore>
<element   name='platform' >
<a:documentation>
Information describing the kind of platform the app runs on
</a:documentation>
<element   name='type' >
<a:documentation>
Name of the platform (eg: iOS, Android, Windows, Tizen,...)
</a:documentation>
<text/>
</element>
<optional>
<element   name='min-version' >
<a:documentation>
Minimum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='max-version' >
<a:documentation>
Maximum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
</oneOrMore>
<optional>
<element   name='hash' >
<a:documentation>
Checksum of the app package
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the hash (eg. SHA-256)
</a:documentation>
</attribute>
<text/>
</element>
</optional>
<optional>
<element   name='signature' >
<a:documentation>
Cryptographic signature for the app package.
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the signature.
</a:documentation>
</attribute>
<text/>
</element>
</optional>
<optional>
<element   name='category' >
<a:documentation>
Category the app belongs in (eg: mapping, browser)
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='apptype' >
<text/>
</element>
</optional>
<optional>
<element   name='Formfactor' >
<a:documentation>
Description of the equipment this intends to run on (eg: Phone, laptop, watch).
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='filename' >
<a:documentation>
Name of the apps file.
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>

Element: applied-text

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model %applied-text-content

<element   name='applied-text' >
<a:annontation>
The content for this element should be the exact text that this requirement was evaluated against with selections selected and assignments assigned.
</a:annontation>
<ref   name='applied-text-content' />
</element>

Element: apptype

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='apptype' >
<text/>
</element>

Element: assignment

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='assignment' >
<text/>
</element>

Element: category

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Category the app belongs in (eg: mapping, browser)
Content Model TEXT

<element   name='category' >
<a:documentation>
Category the app belongs in (eg: mapping, browser)
</a:documentation>
<text/>
</element>

Element: city

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model xsd:NCName

<element   name='city' >
<data   type='NCName' />
</element>

Element: command

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Command executed
Content Model TEXT

<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>

Element: comment

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( tag )* %comment-content
Attributes:
Attribute Type Use Documentation
when TEXT Optional Timestamp for this comment
who TEXT Optional Identifier of the originator of the comment
what TEXT Optional A unique-id for this comment.

<element   name='comment' >
<zeroOrMore>
<element   name='tag' >
<a:documentation>
Requirement id or any keyword.
</a:documentation>
<text/>
</element>
</zeroOrMore>
<ref   name='comment-content' />
</element>

Element: date-completed

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Date when the evaluation finished
Content Model TEXT

<element   name='date-completed' >
<a:documentation>
Date when the evaluation finished
</a:documentation>
<text/>
</element>

Element: date-started

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Date when the evaluation started
Content Model TEXT

<element   name='date-started' >
<a:documentation>
Date when the evaluation started
</a:documentation>
<text/>
</element>

Element: description

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='description' >
<text/>
</element>

Element: email

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Email address associated with the tester
Content Model TEXT

<element   name='email' >
<a:documentation>
Email address associated with the tester
</a:documentation>
<text/>
</element>

Element: environment

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Information about the testing environment.
Content Model ( tester )+ , date-started, date-completed, test-devices %info

<element   name='environment' >
<a:documentation>
Information about the testing environment.
</a:documentation>
<oneOrMore>
<element   name='tester' >
<a:documentation>
Information about a person doing the evaluation
</a:documentation>
<element   name='name' >
<a:documentation>
Name of a person
</a:documentation>
<text/>
</element>
<optional>
<element   name='org' >
<a:documentation>
Name of the organization the tester represents
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='email' >
<a:documentation>
Email address associated with the tester
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
</oneOrMore>
<element   name='date-started' >
<a:documentation>
Date when the evaluation started
</a:documentation>
<text/>
</element>
<element   name='date-completed' >
<a:documentation>
Date when the evaluation finished
</a:documentation>
<text/>
</element>
<element   name='test-devices' >
<a:documentation>
Devices the app was tested on.
</a:documentation>
<oneOrMore>
<element   name='test-device' >
<a:documentation>
Device it was tested on (e.g. Samsung Galaxy, iPhone)
</a:documentation>
<ref   name='version-attr' >
<a:documentation>
Version of the test device
</a:documentation>
</ref>
<text/>
</element>
</oneOrMore>
</element>
<ref   name='info' />
</element>

Element: evaluation

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Information about an evaluation
Content Model environment, ( niap-requirements )* , ( other-requirements )* %info

<element   name='evaluation' >
<a:documentation>
Information about an evaluation
</a:documentation>
<element   name='environment' >
<a:documentation>
Information about the testing environment.
</a:documentation>
<oneOrMore>
<element   name='tester' >
<a:documentation>
Information about a person doing the evaluation
</a:documentation>
<element   name='name' >
<a:documentation>
Name of a person
</a:documentation>
<text/>
</element>
<optional>
<element   name='org' >
<a:documentation>
Name of the organization the tester represents
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='email' >
<a:documentation>
Email address associated with the tester
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
</oneOrMore>
<element   name='date-started' >
<a:documentation>
Date when the evaluation started
</a:documentation>
<text/>
</element>
<element   name='date-completed' >
<a:documentation>
Date when the evaluation finished
</a:documentation>
<text/>
</element>
<element   name='test-devices' >
<a:documentation>
Devices the app was tested on.
</a:documentation>
<oneOrMore>
<element   name='test-device' >
<a:documentation>
Device it was tested on (e.g. Samsung Galaxy, iPhone)
</a:documentation>
<ref   name='version-attr' >
<a:documentation>
Version of the test device
</a:documentation>
</ref>
<text/>
</element>
</oneOrMore>
</element>
<ref   name='info' />
</element>
<zeroOrMore>
<element   name='niap-requirements' >
<a:documentation>
Element for NIAP requirements. Each NIAP requirements section should correspond to a specific EP or PP. Requirements are grouped under this section. They can either be organized into sections/subsections/requirements or less organized into just subsections or requirements. It should not matter.
</a:documentation>
<attribute   name='source-document' >
<a:documentation>
NIAP PP or EP the requirements were gleaned from
</a:documentation>
</attribute>
<attribute   name='version' >
<a:documentation>
The version of the PP or EP
</a:documentation>
<data   type='string' >
<param   name='pattern' >
[0-9]+\.[0-9]
</param>
</data>
</attribute>
<attribute   name='url' >
<a:documentation>
Web location of the PP or EP
</a:documentation>
<data   type='anyURI' />
</attribute>
<oneOrMore>
<choice>
<ref   name='section' />
<ref   name='subsection' />
<ref   name='requirement' />
</choice>
</oneOrMore>
<ref   name='info' />
</element>
</zeroOrMore>
<zeroOrMore>
<element   name='other-requirements' >
<a:documentation>
Non-NIAP PP or EP requirements
</a:documentation>
<attribute   name='scheme' >
<a:documentation>
Name of the organization where the requirements were taken from.
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
Web address where one could go to learn more about the requirements
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<ref   name='recursive-sections' />
</zeroOrMore>
</element>
</zeroOrMore>
<ref   name='info' />
</element>

Element: failed

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model EMPTY

<element   name='failed' >
<empty/>
</element>

Element: filename

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of the apps file.
Content Model TEXT

<element   name='filename' >
<a:documentation>
Name of the apps file.
</a:documentation>
<text/>
</element>

Element: hash

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Checksum of the app package
Content Model TEXT
Attributes:
Attribute Type Use Documentation
type TEXT Optional Algorithm used to compute the hash (eg. SHA-256)

<element   name='hash' >
<a:documentation>
Checksum of the app package
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the hash (eg. SHA-256)
</a:documentation>
</attribute>
<text/>
</element>

Element: incomplete-results

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model

<element   name='incomplete-results' >
<optional>
<text/>
</optional>
</element>

Element: info

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( ( TEXT | %info ) )*
Attributes:
Attribute Type Use Documentation
type TEXT Optional

<element   name='info' >
<optional>
<a:documentation>
Meta-data section that defines the type of data.
</a:documentation>
<attribute   name='type' />
</optional>
<zeroOrMore>
<choice>
<text/>
<ref   name='info' />
</choice>
</zeroOrMore>
</element>

Element: input

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Text that is sent to the application
Content Model TEXT

<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>

Element: input

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='input' >
<text/>
</element>

Element: max-version

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Maximum version of platform the app runs on.
Content Model TEXT

<element   name='max-version' >
<a:documentation>
Maximum version of platform the app runs on.
</a:documentation>
<text/>
</element>

Element: min-version

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Minimum version of platform the app runs on.
Content Model TEXT

<element   name='min-version' >
<a:documentation>
Minimum version of platform the app runs on.
</a:documentation>
<text/>
</element>

Element: name

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of the app as given by its vendor.
Content Model TEXT

<element   name='name' >
<a:documentation>
Name of the app as given by its vendor.
</a:documentation>
<text/>
</element>

Element: name

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of a person
Content Model TEXT

<element   name='name' >
<a:documentation>
Name of a person
</a:documentation>
<text/>
</element>

Element: niap-requirements

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Element for NIAP requirements. Each NIAP requirements section should correspond to a specific EP or PP. Requirements are grouped under this section. They can either be organized into sections/subsections/requirements or less organized into just subsections or requirements. It should not matter.
Content Model ( ( %section | %subsection | %requirement ) )+ %info
Attributes:
Attribute Type Use Documentation
source-document TEXT Optional NIAP PP or EP the requirements were gleaned from
version xsd:string Optional The version of the PP or EP
url xsd:anyURI Optional Web location of the PP or EP

<element   name='niap-requirements' >
<a:documentation>
Element for NIAP requirements. Each NIAP requirements section should correspond to a specific EP or PP. Requirements are grouped under this section. They can either be organized into sections/subsections/requirements or less organized into just subsections or requirements. It should not matter.
</a:documentation>
<attribute   name='source-document' >
<a:documentation>
NIAP PP or EP the requirements were gleaned from
</a:documentation>
</attribute>
<attribute   name='version' >
<a:documentation>
The version of the PP or EP
</a:documentation>
<data   type='string' >
<param   name='pattern' >
[0-9]+\.[0-9]
</param>
</data>
</attribute>
<attribute   name='url' >
<a:documentation>
Web location of the PP or EP
</a:documentation>
<data   type='anyURI' />
</attribute>
<oneOrMore>
<choice>
<ref   name='section' />
<ref   name='subsection' />
<ref   name='requirement' />
</choice>
</oneOrMore>
<ref   name='info' />
</element>

Element: not-applicable

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model

<element   name='not-applicable' >
<optional>
<text/>
</optional>
</element>

Element: not-applicable

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model

<element   name='not-applicable' >
<optional>
<text/>
</optional>
</element>

Element: not-tested

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model

<element   name='not-tested' >
<optional>
<text/>
</optional>
</element>

Element: not-tested

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model

<element   name='not-tested' >
<optional>
<text/>
</optional>
</element>

Element: org

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of the organization the tester represents
Content Model TEXT

<element   name='org' >
<a:documentation>
Name of the organization the tester represents
</a:documentation>
<text/>
</element>

Element: other-requirements

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Non-NIAP PP or EP requirements
Content Model ( %recursive-sections )*
Attributes:
Attribute Type Use Documentation
scheme TEXT Optional Name of the organization where the requirements were taken from.
url xsd:anyURI Optional Web address where one could go to learn more about the requirements

<element   name='other-requirements' >
<a:documentation>
Non-NIAP PP or EP requirements
</a:documentation>
<attribute   name='scheme' >
<a:documentation>
Name of the organization where the requirements were taken from.
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
Web address where one could go to learn more about the requirements
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<ref   name='recursive-sections' />
</zeroOrMore>
</element>

Element: output

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Text printed by the application
Content Model TEXT

<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>

Element: output

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='output' >
<text/>
</element>

Element: package-identification

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Package identifier (e.g., Java package name)
Content Model TEXT

<element   name='package-identification' >
<a:documentation>
Package identifier (e.g., Java package name)
</a:documentation>
<text/>
</element>

Element: passed

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model EMPTY

<element   name='passed' >
<empty/>
</element>

Element: platform

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Information describing the kind of platform the app runs on
Content Model type, min-version ? , max-version ? %info

<element   name='platform' >
<a:documentation>
Information describing the kind of platform the app runs on
</a:documentation>
<element   name='type' >
<a:documentation>
Name of the platform (eg: iOS, Android, Windows, Tizen,...)
</a:documentation>
<text/>
</element>
<optional>
<element   name='min-version' >
<a:documentation>
Minimum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='max-version' >
<a:documentation>
Maximum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>

Element: reply

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model %comment-content
Attributes:
Attribute Type Use Documentation
when TEXT Optional Timestamp for this comment
who TEXT Optional Identifier of the originator of the comment
what TEXT Optional A unique-id for this comment.

<element   name='reply' >
<ref   name='comment-content' />
</element>

Element: report

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Root element for App Vetting Reports
Content Model app-info, ( evaluation )+ , ( comment )*

<element   name='report' >
<a:documentation>
Root element for App Vetting Reports
</a:documentation>
<element   name='app-info' >
<a:documentation>
Meta-data about the app (identification, etc).
</a:documentation>
<element   name='name' >
<a:documentation>
Name of the app as given by its vendor.
</a:documentation>
<text/>
</element>
<optional>
<ref   name='description' />
</optional>
<optional>
<element   name='vendor' >
<a:documentation>
Name of the vendor (hopefully as registered in the playstore)
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<a:documentation>
URL of the vendor's main website.
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<choice>
<element   name='us-address' >
<a:documentation>
USA mailing address the vendor is registered to.
</a:documentation>
<element   name='street1' >
<text/>
</element>
<optional>
<element   name='street2' >
<text/>
</element>
</optional>
<element   name='city' >
<data   type='NCName' />
</element>
<element   name='state' >
<data   type='string' >
<param   name='pattern' >
[A-Z]{2}
</param>
</data>
</element>
<element   name='zip-code' >
<data   type='string' >
<param   name='pattern' >
[0-9]{5}(\-[0-9]{4})?
</param>
</data>
</element>
</element>
<element   name='address' >
<a:documentation>
Address that does not fit in the standard USA address.
</a:documentation>
<text/>
</element>
</choice>
</zeroOrMore>
</element>
</optional>
<optional>
<element   name='package-identification' >
<a:documentation>
Package identifier (e.g., Java package name)
</a:documentation>
<text/>
</element>
</optional>
<ref   name='version' />
<oneOrMore>
<element   name='platform' >
<a:documentation>
Information describing the kind of platform the app runs on
</a:documentation>
<element   name='type' >
<a:documentation>
Name of the platform (eg: iOS, Android, Windows, Tizen,...)
</a:documentation>
<text/>
</element>
<optional>
<element   name='min-version' >
<a:documentation>
Minimum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='max-version' >
<a:documentation>
Maximum version of platform the app runs on.
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
</oneOrMore>
<optional>
<element   name='hash' >
<a:documentation>
Checksum of the app package
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the hash (eg. SHA-256)
</a:documentation>
</attribute>
<text/>
</element>
</optional>
<optional>
<element   name='signature' >
<a:documentation>
Cryptographic signature for the app package.
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the signature.
</a:documentation>
</attribute>
<text/>
</element>
</optional>
<optional>
<element   name='category' >
<a:documentation>
Category the app belongs in (eg: mapping, browser)
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='apptype' >
<text/>
</element>
</optional>
<optional>
<element   name='Formfactor' >
<a:documentation>
Description of the equipment this intends to run on (eg: Phone, laptop, watch).
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='filename' >
<a:documentation>
Name of the apps file.
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
<oneOrMore>
<element   name='evaluation' >
<a:documentation>
Information about an evaluation
</a:documentation>
<element   name='environment' >
<a:documentation>
Information about the testing environment.
</a:documentation>
<oneOrMore>
<element   name='tester' >
<a:documentation>
Information about a person doing the evaluation
</a:documentation>
<element   name='name' >
<a:documentation>
Name of a person
</a:documentation>
<text/>
</element>
<optional>
<element   name='org' >
<a:documentation>
Name of the organization the tester represents
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='email' >
<a:documentation>
Email address associated with the tester
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>
</oneOrMore>
<element   name='date-started' >
<a:documentation>
Date when the evaluation started
</a:documentation>
<text/>
</element>
<element   name='date-completed' >
<a:documentation>
Date when the evaluation finished
</a:documentation>
<text/>
</element>
<element   name='test-devices' >
<a:documentation>
Devices the app was tested on.
</a:documentation>
<oneOrMore>
<element   name='test-device' >
<a:documentation>
Device it was tested on (e.g. Samsung Galaxy, iPhone)
</a:documentation>
<ref   name='version-attr' >
<a:documentation>
Version of the test device
</a:documentation>
</ref>
<text/>
</element>
</oneOrMore>
</element>
<ref   name='info' />
</element>
<zeroOrMore>
<element   name='niap-requirements' >
<a:documentation>
Element for NIAP requirements. Each NIAP requirements section should correspond to a specific EP or PP. Requirements are grouped under this section. They can either be organized into sections/subsections/requirements or less organized into just subsections or requirements. It should not matter.
</a:documentation>
<attribute   name='source-document' >
<a:documentation>
NIAP PP or EP the requirements were gleaned from
</a:documentation>
</attribute>
<attribute   name='version' >
<a:documentation>
The version of the PP or EP
</a:documentation>
<data   type='string' >
<param   name='pattern' >
[0-9]+\.[0-9]
</param>
</data>
</attribute>
<attribute   name='url' >
<a:documentation>
Web location of the PP or EP
</a:documentation>
<data   type='anyURI' />
</attribute>
<oneOrMore>
<choice>
<ref   name='section' />
<ref   name='subsection' />
<ref   name='requirement' />
</choice>
</oneOrMore>
<ref   name='info' />
</element>
</zeroOrMore>
<zeroOrMore>
<element   name='other-requirements' >
<a:documentation>
Non-NIAP PP or EP requirements
</a:documentation>
<attribute   name='scheme' >
<a:documentation>
Name of the organization where the requirements were taken from.
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
Web address where one could go to learn more about the requirements
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<ref   name='recursive-sections' />
</zeroOrMore>
</element>
</zeroOrMore>
<ref   name='info' />
</element>
</oneOrMore>
<zeroOrMore>
<element   name='comment' >
<zeroOrMore>
<element   name='tag' >
<a:documentation>
Requirement id or any keyword.
</a:documentation>
<text/>
</element>
</zeroOrMore>
<ref   name='comment-content' />
</element>
</zeroOrMore>
</element>

Element: requirement

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Describes a generic requirement
Content Model %results-section, ( activity %info )+
Attributes:
Attribute Type Use Documentation
id TEXT Optional Unique name or identifier associated with this requirement
url xsd:anyURI Optional URL associated with this requirement

<element   name='requirement' >
<a:documentation>
Describes a generic requirement
</a:documentation>
<attribute   name='id' >
<a:documentation>
Unique name or identifier associated with this requirement
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
URL associated with this requirement
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<ref   name='results-section' />
<oneOrMore>
<element   name='activity' >
<a:documentation>
Activities completed to check this compliance
</a:documentation>
<element   name='summary' >
<a:documentation>
Description of the actions performed with HTML if stylized content is desired
</a:documentation>
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<a:documentation>
Data the represents what happened on a terminal if that was the method of testing
</a:documentation>
<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>
<oneOrMore>
<choice>
<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>
<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<element   name='tools' >
<a:documentation>
Tools used for the evaluation
</a:documentation>
<oneOrMore>
<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>
<ref   name='info' />
</oneOrMore>
</element>

Element: requirement

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model applied-text ? , %results-section, ( activity %info )+ ?
Attributes:
Attribute Type Use Documentation
id xsd:string Optional

<element   name='requirement' >
<attribute   name='id' >
<data   type='string' >
<param   name='pattern' >
[AaFf][A-Za-z]+_.+(_ext)?\.[0-9]+\.[0-9]+[a-z]*
</param>
</data>
</attribute>
<optional>
<element   name='applied-text' >
<a:annontation>
The content for this element should be the exact text that this requirement was evaluated against with selections selected and assignments assigned.
</a:annontation>
<ref   name='applied-text-content' />
</element>
</optional>
<optional>
<ref   name='results-section' />
<oneOrMore>
<element   name='activity' >
<element   name='summary' >
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<oneOrMore>
<choice>
<element   name='input' >
<text/>
</element>
<element   name='output' >
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<a:documentation>
</a:documentation>
<element   name='tools' >
<oneOrMore>
<element   name='tool' >
<attribute   name='name' />
<optional>
<attribute   name='url' />
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>
<ref   name='info' />
</oneOrMore>
</optional>
</element>

Element: section

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Level of nesting
Content Model ( ( %recursive-sections | requirement | %info ) )*
Attributes:
Attribute Type Use Documentation
id TEXT Optional Name or identifier associated with this level

<element   name='section' >
<a:documentation>
Level of nesting
</a:documentation>
<optional>
<attribute   name='id' >
<a:documentation>
Name or identifier associated with this level
</a:documentation>
</attribute>
</optional>
<zeroOrMore>
<choice>
<ref   name='recursive-sections' />
<element   name='requirement' >
<a:documentation>
Describes a generic requirement
</a:documentation>
<attribute   name='id' >
<a:documentation>
Unique name or identifier associated with this requirement
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
URL associated with this requirement
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<ref   name='results-section' />
<oneOrMore>
<element   name='activity' >
<a:documentation>
Activities completed to check this compliance
</a:documentation>
<element   name='summary' >
<a:documentation>
Description of the actions performed with HTML if stylized content is desired
</a:documentation>
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<a:documentation>
Data the represents what happened on a terminal if that was the method of testing
</a:documentation>
<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>
<oneOrMore>
<choice>
<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>
<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<element   name='tools' >
<a:documentation>
Tools used for the evaluation
</a:documentation>
<oneOrMore>
<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>
<ref   name='info' />
</oneOrMore>
</element>
<ref   name='info' />
</choice>
</zeroOrMore>
</element>

Element: section

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Represents a NIAP PP or EP section. Requirements under it can be organized into subsections or requirements.
Content Model ( ( %subsection)+ | ( %requirement)+ ) %info
Attributes:
Attribute Type Use Documentation
id xsd:NCName Optional ID of the section should correspond to a Functional Class Name from CCPART2V3.1R2.pdf.

<element   name='section' >
<a:documentation>
Represents a NIAP PP or EP section. Requirements under it can be organized into subsections or requirements.
</a:documentation>
<attribute   name='id' >
<a:documentation>
ID of the section should correspond to a
<htm:i>
Functional Class Name
</htm:i>
from CCPART2V3.1R2.pdf.
</a:documentation>
<data   type='NCName' />
</attribute>
<choice>
<oneOrMore>
<ref   name='subsection' />
</oneOrMore>
<oneOrMore>
<ref   name='requirement' />
</oneOrMore>
</choice>
<ref   name='info' />
</element>

Element: selection

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model %applied-text-content

<element   name='selection' >
<ref   name='applied-text-content' />
</element>

Element: signature

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Cryptographic signature for the app package.
Content Model TEXT
Attributes:
Attribute Type Use Documentation
type TEXT Optional Algorithm used to compute the signature.

<element   name='signature' >
<a:documentation>
Cryptographic signature for the app package.
</a:documentation>
<attribute   name='type' >
<a:documentation>
Algorithm used to compute the signature.
</a:documentation>
</attribute>
<text/>
</element>

Element: state

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model xsd:string

<element   name='state' >
<data   type='string' >
<param   name='pattern' >
[A-Z]{2}
</param>
</data>
</element>

Element: street1

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='street1' >
<text/>
</element>

Element: street2

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='street2' >
<text/>
</element>

Element: subsection

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation ID of the section should correspond to the Function Family Name in CCPART2V3.1R2.pdf.
Content Model ( not-tested | not-applicable | ( %requirement )+ )
Attributes:
Attribute Type Use Documentation
id TEXT Optional

<element   name='subsection' >
<a:documentation>
ID of the section should correspond to the
<htm:i>
Function Family Name
</htm:i>
in CCPART2V3.1R2.pdf.
</a:documentation>
<attribute   name='id' />
<choice>
<element   name='not-tested' >
<optional>
<text/>
</optional>
</element>
<element   name='not-applicable' >
<optional>
<text/>
</optional>
</element>
<oneOrMore>
<ref   name='requirement' />
</oneOrMore>
</choice>
</element>

Element: summary

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Description of the actions performed with HTML if stylized content is desired
Content Model %html-content

<element   name='summary' >
<a:documentation>
Description of the actions performed with HTML if stylized content is desired
</a:documentation>
<ref   name='html-content' />
</element>

Element: summary

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model %html-content

<element   name='summary' >
<ref   name='html-content' />
</element>

Element: tag

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Requirement id or any keyword.
Content Model TEXT

<element   name='tag' >
<a:documentation>
Requirement id or any keyword.
</a:documentation>
<text/>
</element>

Element: test-device

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Device it was tested on (e.g. Samsung Galaxy, iPhone)
Content Model %version-attr TEXT
Attributes:
Attribute Type Use Documentation
version TEXT Optional

<element   name='test-device' >
<a:documentation>
Device it was tested on (e.g. Samsung Galaxy, iPhone)
</a:documentation>
<ref   name='version-attr' >
<a:documentation>
Version of the test device
</a:documentation>
</ref>
<text/>
</element>

Element: test-devices

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Devices the app was tested on.
Content Model ( test-device )+

<element   name='test-devices' >
<a:documentation>
Devices the app was tested on.
</a:documentation>
<oneOrMore>
<element   name='test-device' >
<a:documentation>
Device it was tested on (e.g. Samsung Galaxy, iPhone)
</a:documentation>
<ref   name='version-attr' >
<a:documentation>
Version of the test device
</a:documentation>
</ref>
<text/>
</element>
</oneOrMore>
</element>

Element: tester

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Information about a person doing the evaluation
Content Model name, org ? , email ? %info

<element   name='tester' >
<a:documentation>
Information about a person doing the evaluation
</a:documentation>
<element   name='name' >
<a:documentation>
Name of a person
</a:documentation>
<text/>
</element>
<optional>
<element   name='org' >
<a:documentation>
Name of the organization the tester represents
</a:documentation>
<text/>
</element>
</optional>
<optional>
<element   name='email' >
<a:documentation>
Email address associated with the tester
</a:documentation>
<text/>
</element>
</optional>
<ref   name='info' />
</element>

Element: text

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model %html-content

<element   name='text' >
<ref   name='html-content' />
</element>

Element: tool

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Tool used for the evaluation
Content Model
Attributes:
Attribute Type Use Documentation
name TEXT Optional
url xsd:anyURI Optional
description TEXT Optional

<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>

Element: tool

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model
Attributes:
Attribute Type Use Documentation
name TEXT Optional
url TEXT Optional
description TEXT Optional

<element   name='tool' >
<attribute   name='name' />
<optional>
<attribute   name='url' />
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>

Element: tools

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Tools used for the evaluation
Content Model ( tool )+

<element   name='tools' >
<a:documentation>
Tools used for the evaluation
</a:documentation>
<oneOrMore>
<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>

Element: tools

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( tool )+

<element   name='tools' >
<oneOrMore>
<element   name='tool' >
<attribute   name='name' />
<optional>
<attribute   name='url' />
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>

Element: transcript

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Data the represents what happened on a terminal if that was the method of testing
Content Model command, ( ( input | output | %info | TEXT ) )+ TEXT

<element   name='transcript' >
<a:documentation>
Data the represents what happened on a terminal if that was the method of testing
</a:documentation>
<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>
<oneOrMore>
<choice>
<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>
<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>

Element: transcript

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( ( input | output | %info | TEXT ) )+ TEXT

<element   name='transcript' >
<oneOrMore>
<choice>
<element   name='input' >
<text/>
</element>
<element   name='output' >
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>

Element: type

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of the platform (eg: iOS, Android, Windows, Tizen,...)
Content Model TEXT

<element   name='type' >
<a:documentation>
Name of the platform (eg: iOS, Android, Windows, Tizen,...)
</a:documentation>
<text/>
</element>

Element: us-address

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation USA mailing address the vendor is registered to.
Content Model street1, street2 ? , city, state, zip-code

<element   name='us-address' >
<a:documentation>
USA mailing address the vendor is registered to.
</a:documentation>
<element   name='street1' >
<text/>
</element>
<optional>
<element   name='street2' >
<text/>
</element>
</optional>
<element   name='city' >
<data   type='NCName' />
</element>
<element   name='state' >
<data   type='string' >
<param   name='pattern' >
[A-Z]{2}
</param>
</data>
</element>
<element   name='zip-code' >
<data   type='string' >
<param   name='pattern' >
[0-9]{5}(\-[0-9]{4})?
</param>
</data>
</element>
</element>

Element: vendor

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Name of the vendor (hopefully as registered in the playstore)
Content Model ( ( us-address | address ) )*
Attributes:
Attribute Type Use Documentation
name TEXT Optional
url xsd:anyURI Optional URL of the vendor's main website.

<element   name='vendor' >
<a:documentation>
Name of the vendor (hopefully as registered in the playstore)
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<a:documentation>
URL of the vendor's main website.
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<zeroOrMore>
<choice>
<element   name='us-address' >
<a:documentation>
USA mailing address the vendor is registered to.
</a:documentation>
<element   name='street1' >
<text/>
</element>
<optional>
<element   name='street2' >
<text/>
</element>
</optional>
<element   name='city' >
<data   type='NCName' />
</element>
<element   name='state' >
<data   type='string' >
<param   name='pattern' >
[A-Z]{2}
</param>
</data>
</element>
<element   name='zip-code' >
<data   type='string' >
<param   name='pattern' >
[0-9]{5}(\-[0-9]{4})?
</param>
</data>
</element>
</element>
<element   name='address' >
<a:documentation>
Address that does not fit in the standard USA address.
</a:documentation>
<text/>
</element>
</choice>
</zeroOrMore>
</element>

Element: version

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model TEXT

<element   name='version' >
<text/>
</element>

Element: zip-code

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model xsd:string

<element   name='zip-code' >
<data   type='string' >
<param   name='pattern' >
[0-9]{5}(\-[0-9]{4})?
</param>
</data>
</element>

Pattern: applied-text-content

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( ( TEXT | selection | assignment ) )+

<define   name='applied-text-content' >
<oneOrMore>
<choice>
<text/>
<element   name='selection' >
<ref   name='applied-text-content' />
</element>
<element   name='assignment' >
<text/>
</element>
</choice>
</oneOrMore>
</define>

Pattern: comment-content


Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Content for a comment or a reply.
Content Model text, ( reply )*
Attributes:
Attribute Type Use Documentation
when TEXT Required Timestamp for this comment
who TEXT Required Identifier of the originator of the comment
what TEXT Required A unique-id for this comment.

<define   name='comment-content' >
<attribute   name='when' >
<a:documentation>
Timestamp for this comment
</a:documentation>
</attribute>
<attribute   name='who' >
<a:documentation>
Identifier of the originator of the comment
</a:documentation>
</attribute>
<attribute   name='what' >
<a:documentation>
A unique-id for this comment.
</a:documentation>
</attribute>
<a:documentation>
Content for a comment or a reply.
</a:documentation>
<element   name='text' >
<ref   name='html-content' />
</element>
<zeroOrMore>
<element   name='reply' >
<ref   name='comment-content' />
</element>
</zeroOrMore>
</define>

Pattern: description

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model description

<define   name='description' >
<element   name='description' >
<text/>
</element>
</define>

Pattern: html-content

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Pattern that defines text that can be marked up with HTML content.
Content Model ( ( TEXT | %html-element ) )+

<define   name='html-content' >
<a:documentation>
Pattern that defines text that can be marked up with HTML content.
</a:documentation>
<oneOrMore>
<choice>
<text/>
<ref   name='html-element' />
</choice>
</oneOrMore>
</define>

Pattern: html-element

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Pattern defines the html-element, which is any element in the xhtml namespace.
Content Model

<define   name='html-element' >
<a:documentation>
Pattern defines the html-element, which is any element in the xhtml namespace.
</a:documentation>
<element   ns='http://www.w3.org/1999/xhtml' >
<anyName>
<except>
<nsName   ns='https://commoncriteria.github.io/pp/app-vetting/1.0' />
</except>
</anyName>
<a:documentation>
Defines all html-elements with an optional number of html attributes and descendants.
</a:documentation>
<zeroOrMore>
<attribute>
<anyName/>
</attribute>
</zeroOrMore>
<zeroOrMore>
<choice>
<text/>
<ref   name='html-element' />
</choice>
</zeroOrMore>
</element>
</define>

Pattern: info

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation This is a generic tree-like structure that hopefully lets users expand the report structure as necessary.
Content Model ( info )*

<define   name='info' >
<a:documentation>
This is a generic tree-like structure that hopefully lets users expand the report structure as necessary.
</a:documentation>
<zeroOrMore>
<element   name='info' >
<optional>
<a:documentation>
Meta-data section that defines the type of data.
</a:documentation>
<attribute   name='type' />
</optional>
<zeroOrMore>
<choice>
<text/>
<ref   name='info' />
</choice>
</zeroOrMore>
</element>
</zeroOrMore>
</define>

Pattern: recursive-sections

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Documentation Pattern to handle arbitrarily deep nesting of different sections and categories
Content Model section

<define   name='recursive-sections' >
<a:documentation>
Pattern to handle arbitrarily deep nesting of different sections and categories
</a:documentation>
<element   name='section' >
<a:documentation>
Level of nesting
</a:documentation>
<optional>
<attribute   name='id' >
<a:documentation>
Name or identifier associated with this level
</a:documentation>
</attribute>
</optional>
<zeroOrMore>
<choice>
<ref   name='recursive-sections' />
<element   name='requirement' >
<a:documentation>
Describes a generic requirement
</a:documentation>
<attribute   name='id' >
<a:documentation>
Unique name or identifier associated with this requirement
</a:documentation>
</attribute>
<optional>
<attribute   name='url' >
<a:documentation>
URL associated with this requirement
</a:documentation>
<data   type='anyURI' />
</attribute>
</optional>
<ref   name='results-section' />
<oneOrMore>
<element   name='activity' >
<a:documentation>
Activities completed to check this compliance
</a:documentation>
<element   name='summary' >
<a:documentation>
Description of the actions performed with HTML if stylized content is desired
</a:documentation>
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<a:documentation>
Data the represents what happened on a terminal if that was the method of testing
</a:documentation>
<element   name='command' >
<a:documentation>
Command executed
</a:documentation>
<text/>
</element>
<oneOrMore>
<choice>
<element   name='input' >
<a:documentation>
Text that is sent to the application
</a:documentation>
<text/>
</element>
<element   name='output' >
<a:documentation>
Text printed by the application
</a:documentation>
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<element   name='tools' >
<a:documentation>
Tools used for the evaluation
</a:documentation>
<oneOrMore>
<element   name='tool' >
<a:documentation>
Tool used for the evaluation
</a:documentation>
<attribute   name='name' />
<optional>
<attribute   name='url' >
<data   type='anyURI' />
</attribute>
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>
<ref   name='info' />
</oneOrMore>
</element>
<ref   name='info' />
</choice>
</zeroOrMore>
</element>
</define>

Pattern: requirement

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model requirement

<define   name='requirement' >
<element   name='requirement' >
<attribute   name='id' >
<data   type='string' >
<param   name='pattern' >
[AaFf][A-Za-z]+_.+(_ext)?\.[0-9]+\.[0-9]+[a-z]*
</param>
</data>
</attribute>
<optional>
<element   name='applied-text' >
<a:annontation>
The content for this element should be the exact text that this requirement was evaluated against with selections selected and assignments assigned.
</a:annontation>
<ref   name='applied-text-content' />
</element>
</optional>
<optional>
<ref   name='results-section' />
<oneOrMore>
<element   name='activity' >
<element   name='summary' >
<ref   name='html-content' />
</element>
<optional>
<element   name='transcript' >
<oneOrMore>
<choice>
<element   name='input' >
<text/>
</element>
<element   name='output' >
<text/>
</element>
<ref   name='info' />
<text/>
</choice>
</oneOrMore>
<text/>
</element>
</optional>
<optional>
<a:documentation>
</a:documentation>
<element   name='tools' >
<oneOrMore>
<element   name='tool' >
<attribute   name='name' />
<optional>
<attribute   name='url' />
</optional>
<optional>
<attribute   name='description' />
</optional>
</element>
</oneOrMore>
</element>
</optional>
</element>
<ref   name='info' />
</oneOrMore>
</optional>
</element>
</define>

Pattern: results-section

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model ( passed | failed | incomplete-results | not-tested | not-applicable )

<define   name='results-section' >
<choice>
<element   name='passed' >
<empty/>
</element>
<element   name='failed' >
<empty/>
</element>
<element   name='incomplete-results' >
<optional>
<text/>
</optional>
</element>
<element   name='not-tested' >
<optional>
<text/>
</optional>
</element>
<element   name='not-applicable' >
<optional>
<text/>
</optional>
</element>
</choice>
</define>

Pattern: section

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model section

<define   name='section' >
<element   name='section' >
<a:documentation>
Represents a NIAP PP or EP section. Requirements under it can be organized into subsections or requirements.
</a:documentation>
<attribute   name='id' >
<a:documentation>
ID of the section should correspond to a
<htm:i>
Functional Class Name
</htm:i>
from CCPART2V3.1R2.pdf.
</a:documentation>
<data   type='NCName' />
</attribute>
<choice>
<oneOrMore>
<ref   name='subsection' />
</oneOrMore>
<oneOrMore>
<ref   name='requirement' />
</oneOrMore>
</choice>
<ref   name='info' />
</element>
</define>

Pattern: subsection

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model subsection

<define   name='subsection' >
<element   name='subsection' >
<a:documentation>
ID of the section should correspond to the
<htm:i>
Function Family Name
</htm:i>
in CCPART2V3.1R2.pdf.
</a:documentation>
<attribute   name='id' />
<choice>
<element   name='not-tested' >
<optional>
<text/>
</optional>
</element>
<element   name='not-applicable' >
<optional>
<text/>
</optional>
</element>
<oneOrMore>
<ref   name='requirement' />
</oneOrMore>
</choice>
</element>
</define>

Pattern: version

Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model version

<define   name='version' >
<element   name='version' >
<text/>
</element>
</define>

Pattern: version-attr


Namespace https://niap-ccevs.org/cc/app-vetting/1.0
Content Model
Attributes:
Attribute Type Use Documentation
version TEXT Required

<define   name='version-attr' >
<attribute   name='version' >
<text/>
</attribute>
</define>