| Rule ID |
Description / Results |
Conformance Method |
Unit Tests |
| GD-01 |
All XML schemas MUST be based on W3C technical specifications that have achieved Recommendation
status. |
Manual |
None |
| GD-02 |
Schemas MUST conform to XML Schema Part 1: Structures (http://www.w3.org/TR/xmlschema-1/)
and XML Schema, Part 2: Datatypes (http://www.w3.org/TR/xmlschema-2/).
| GD-02/1.xsd |
Successfully validated: Identified error for schema: 1.xsd. The root element is not
an xsd:schema element. |
|
Partial |
Pass |
| GD-03 |
Schemas MUST use the ISO/IEC 10646 – UCS – Unicode character set. UTF-8 MUST be used
for encoding Unicode characters.
| GD-03/1.xsd |
Successfully validated: Identified error for schema: 1.xsd. The XML declaration (first
line) of the document does not indicate an encoding of UTF-8. |
|
Auto |
Pass |
| GD-04 |
Type, element and attribute names MUST be composed of words in the English language,
using the primary English spellings provided in the Oxford English Dictionary. The
only permitted exceptions are the acronyms, abbreviations and other word truncations
listed in Appendix C. |
Manual |
None |
| GD-05 |
Type, element and attribute names SHOULD consist only of nouns, adjectives, and verbs
in the present tense with the exception of acronyms, abbreviations and other word
truncations listed in Appendix C. |
Manual |
None |
| GD-06 |
The characters used in type, element and attribute names MUST be contained in the
following set: ‘a-z, A-Z and 0-9’.
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD_element".
The name of
element BAD_element
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD.element".
The name of
element BAD.element
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD-element".
The name of
element BAD-element
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BADΔelement".
The name of
element BADΔelement
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD_attribute".
The name of
attribute BAD_attribute
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD.attribute".
The name of
attribute BAD.attribute
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD-attribute".
The name of
attribute BAD-attribute
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BADΔattribute".
The name of
attribute BADΔattribute
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD_simpleType".
The name of
simpleType BAD_simpleType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD.simpleType".
The name of
simpleType BAD.simpleType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD-simpleType".
The name of
simpleType BAD-simpleType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BADΔsimpleType".
The name of
simpleType BADΔsimpleType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD_complexType".
The name of
complexType BAD_complexType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD.complexType".
The name of
complexType BAD.complexType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BAD-complexType".
The name of
complexType BAD-complexType
contains invalid characters.
|
| GD-06/1.xsd |
Successfully validated: Identified error for component: "BADΔcomplexType".
The name of
complexType BADΔcomplexType
contains invalid characters.
|
| GD-06/2.xsd |
Successfully validated: No error for component: "GOODelementABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789". |
| GD-06/3.xsd |
Successfully validated: No error for component: "GOODattributeABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789". |
| GD-06/4.xsd |
Successfully validated: No error for component: "GOODsimpleTypeABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890". |
| GD-06/4.xsd |
Successfully validated: No error for component: "GOODcomplexTypeABCDEFGHIJKLMNOPQRSTUVWXYZ2345678901abcdefghijklmnopqrstuvwxyz". |
|
Auto |
Pass |
| GD-07 |
The maximum length of a component name SHOULD be no more than 35 characters. Use of
abbreviations and acronyms, is encouraged to reduce component name length. Any new
abbreviations or acronyms MUST be added to Appendix C.
| GD-07/1.xsd |
Successfully validated: No error for component: "ThisElementNameHas34CharactersAAAA". |
| GD-07/2.xsd |
Successfully validated: Identified error for component: "ThisElementNameHas36CharactersAAAAAA".
The length of the
element
named
ThisElementNameHas36CharactersAAAAAA
is
36.
|
| GD-07/2.xsd |
Successfully validated: Identified error for component: "ThisAttributeNameHas36CharactersAAAA".
The length of the
attribute
named
ThisAttributeNameHas36CharactersAAAA
is
36.
|
| GD-07/2.xsd |
Successfully validated: Identified error for component: "ThisSimpleTypeNameHas41CharactersAAAAAAAA".
The length of the
simpleType
named
ThisSimpleTypeNameHas41CharactersAAAAAAAA
is
41.
|
| GD-07/2.xsd |
Successfully validated: Identified error for component: "ThisComplexTypeNameHas40Characters123456".
The length of the
complexType
named
ThisComplexTypeNameHas40Characters123456
is
40.
|
| GD-07/2.xsd |
Successfully validated: No error for component: "ThisComplexTypeNameHas39CharactersAAAAA". |
| GD-07/3.xsd |
Successfully validated: No error for component: "ThisAttributeNameHas34CharactersAA". |
| GD-07/4.xsd |
Successfully validated: No error for component: "ThisSimpleTypeNameHas34CharactersA". |
| GD-07/5.xsd |
Successfully validated: No error for component: "ThisComplexTypeNameHas34Characters". |
| GD-07/6.xsd |
Successfully validated: No error for component: "ThisElementNameHas35CharactersAAAAA". |
| GD-07/7.xsd |
Successfully validated: No error for component: "ThisAttributeNameHas35CharactersAAA". |
| GD-07/8.xsd |
Successfully validated: No error for component: "ThisSimpleTypeNameHas35CharactersAA". |
| GD-07/9.xsd |
Successfully validated: No error for component: "ThisComplexTypeNameHas35CharactersA". |
|
Auto |
Pass |
| GD-08 |
Type, element and attribute names SHOULD be concise and self-explanatory. |
Manual |
None |
| GD-09 |
Element names MUST use the upper camel case (UCC) convention. For example, CountryCode.
| GD-09/1.xsd |
Successfully validated: No error for component: "Good". |
| GD-09/2.xsd |
Successfully validated: No error for component: "GoodElementName". |
| GD-09/3.xsd |
Successfully validated: Identified error for component: "badElementName".
The element name badElementName does not start with an upper-case letter.
|
| GD-09/3.xsd |
Successfully validated: Identified error for component: "badelementname".
The element name badelementname does not start with an upper-case letter.
|
| GD-09/3.xsd |
Successfully validated: Identified error for component: "BADELEMENTNAME".
The element name BADELEMENTNAME contains all
upper-case letters instead of using camel case.
|
| GD-09/4.xsd |
Successfully validated: No error for component: "DOI". |
| GD-09/5.xsd |
Successfully validated: No error for component: "AB". |
| GD-09/6.xsd |
Successfully validated: No error for component: "A". |
|
Auto |
Pass |
| GD-10 |
Type names MUST use the UCC convention and have the suffix Type. For example, ApplicantType.
| GD-10/1.xsd |
Successfully validated: Identified error for component: "badComplexType".
The complexType name badComplexType does not start with an upper-case letter.
|
| GD-10/1.xsd |
Successfully validated: Identified error for component: "BadComplex".
The complexType name BadComplex does not end with Type.
|
| GD-10/1.xsd |
Successfully validated: Identified error for component: "BADCOMPLEXTYPE".
The complexType name BADCOMPLEXTYPE contains all upper-case letters instead of
using camel case.
|
The complexType name BADCOMPLEXTYPE does not end with Type.
|
| GD-10/1.xsd |
Successfully validated: Identified error for component: "badSimpleType".
The simpleType name badSimpleType does not start with an upper-case letter.
|
| GD-10/1.xsd |
Successfully validated: Identified error for component: "BadSimple".
The simpleType name BadSimple does not end with Type.
|
| GD-10/1.xsd |
Successfully validated: Identified error for component: "BADSIMPLETYPE".
The simpleType name BADSIMPLETYPE contains all upper-case letters instead of
using camel case.
|
The simpleType name BADSIMPLETYPE does not end with Type.
|
| GD-10/2.xsd |
Successfully validated: No error for component: "GoodComplexType". |
| GD-10/3.xsd |
Successfully validated: No error for component: "GoodSimpleType". |
|
Auto |
Pass |
| GD-11 |
Attribute names MUST use the lower camel case (LCC) convention. For example, currencyCode="EUR".
| GD-11/1.xsd |
Successfully validated: No error for component: "good". |
| GD-11/2.xsd |
Successfully validated: No error for component: "goodAttributeName". |
| GD-11/3.xsd |
Successfully validated: Identified error for component: "BadAttributeName".
Attribute name BadAttributeName does not start with
a lower-case letter.
|
|
Auto |
Pass |
| GD-12 |
The acronyms and abbreviations listed in Appendix C MUST always be used instead of
the complete extended name.
| GD-12/1.xsd |
Successfully validated: Identified error for component: "SomethingBiologicalDepositSomething".
BiologicalDeposit in SomethingBiologicalDepositSomething should be abbreviated as
BioDeposit.
|
| GD-12/1.xsd |
Successfully validated: Identified error for component: "Bold". Bold in Bold should
be abbreviated as B.
|
| GD-12/1.xsd |
Successfully validated: Identified error for component: "ThisDefinitionDescription".
DefinitionDescription in ThisDefinitionDescription should be abbreviated as DD.
|
| GD-12/2.xsd |
Successfully validated: No error for component: "NoAbbreviationsHere". |
| GD-12/3.xsd |
Successfully validated: No error for component: "SomethingIdentifier". |
|
Auto |
Pass |
| GD-13 |
Acronyms and abbreviations at the beginning of an attribute declaration MUST appear
in all lower case. For example, biodepositDescriptionText. All other acronym and
abbreviation usage in an attribute declaration MUST appear in upper case as listed
in Appendix C.
| GD-13/1.xsd |
Successfully validated: No error for component: "noAbbreviationsAnyway". |
| GD-13/2.xsd |
Successfully validated: No error for component: "altThis". |
| GD-13/3.xsd |
Successfully validated: No error for component: "hasIButIsGoodAnyway". |
| GD-13/4.xsd |
Successfully validated: No error for component: "isothis". |
| GD-13/5.xsd |
Successfully validated: No error for component: "someBioDepositThing". |
| GD-13/6.xsd |
Successfully validated: Identified error for component: "ISOThis".
Attribute ISOThis contains these improperly capitalized abbreviations: ISO. |
| GD-13/6.xsd |
Successfully validated: Identified error for component: "hasCapitalizedIso".
Attribute hasCapitalizedIso contains these improperly capitalized abbreviations: Iso. |
| GD-13/6.xsd |
Successfully validated: Identified error for component: "CPCAbcDeCPCFGhicpcJ".
Attribute CPCAbcDeCPCFGhicpcJ contains these improperly capitalized abbreviations:
CPC, CPCF. |
|
Auto |
Pass |
| GD-14 |
Acronyms and abbreviations MUST appear as listed in Appendix C for element and type
names.
| GD-14/1.xsd |
Successfully validated: No error for component: "NoAbbreviationsAnyway". |
| GD-14/2.xsd |
Successfully validated: No error for component: "AltThis". |
| GD-14/3.xsd |
Successfully validated: No error for component: "HasIButIsGoodAnyway". |
| GD-14/4.xsd |
Successfully validated: Identified error for component: "ISOthis".
Component ISOthis contains these improperly capitalized abbreviations: IS.
|
| GD-14/5.xsd |
Successfully validated: No error for component: "SomeBioDepositThing". |
| GD-14/6.xsd |
Successfully validated: Identified error for component: "isoThis".
Component isoThis contains these improperly capitalized abbreviations: iso.
|
| GD-14/6.xsd |
Successfully validated: Identified error for component: "HasCapitalizedIso".
Component HasCapitalizedIso contains these improperly capitalized abbreviations: Iso.
|
|
Auto |
Pass |
| GD-15 |
Complex type names SHOULD include a meaningful Object Class Term.
| GD-15/1.xsd |
Successfully validated: No error for component: "badComplexType". |
| GD-15/1.xsd |
Successfully validated: No error for component: "BadComplex". |
| GD-15/1.xsd |
Successfully validated: No error for component: "BADCOMPLEXTYPE". |
| GD-15/2.xsd |
Successfully validated: No error for component: "GoodComplexType". |
| GD-15/2.xsd |
Successfully validated: Identified error for component: "Type".
No Object Class Term was found in the complexType name Type. Object Class refers to
an activity or object within a business context and represents the logical data grouping
or aggregation (in a logical data model) to which a Property belongs.
|
| GD-15/2.xsd |
Successfully validated: Identified error for component: "MeasureType".
No Object Class Term was found in the complexType name MeasureType. Object Class refers
to an activity or object within a business context and represents the logical data
grouping or aggregation (in a logical data model) to which a Property belongs.
|
|
Partial |
Pass |
| GD-16 |
When we need two Object Class terms in a given component name due to the nature of
business entity, association complex type can be used. Names of an association complex
type SHOULD use a structure of Object Class term of the associating complex type,
a Property term that describes the nature of the association, and the Object Class
of the associated complex type. Qualifiers may precede the Object Class and Property
Term. For example, in ApplicantResidenceAddress, Applicant is Object Class of associating
complex type, Residence is the Property, and Address is the Object Class of associated
complex type. |
Manual |
None |
| GD-17 |
Names of basic elements (those based on a simple or complex type that do not permit
children) SHOULD consist of an Object Class Term, Property Term, and where applicable
a Representation Term. Qualifier Terms may precede the Object Class term and Property
Term.
| GD-17/1.xsd |
Successfully validated: No error for component: "AdditionalRemark". |
| GD-17/1.xsd |
Successfully validated: No error for component: "ConferenceDate". |
| GD-17/1.xsd |
Successfully validated: No error for component: "ApplicationLanguageCode". |
| GD-17/2.xsd |
Successfully validated: Identified error for component: "Subgroup".
Name consists only of Subgroup. Missing Object Class Term and/or Property Term. Object
Class refers to an activity or object within a business context and represents the
logical data grouping or aggregation (in a logical data model) to which a Property
belongs. Property Term identifies characteristics of the Object Class.
|
|
Partial |
Pass |
| GD-18 |
An Object Class Term MUST always have the same semantic meaning throughout a namespace
and MAY consist of more than one word. For example, ContactInformation. |
Manual |
None |
| GD-19 |
A Property Term in a name MUST be unique within the context of an Object Class but
MAY be reused across different Object Classes. |
Manual |
None |
| GD-20 |
A Qualifier Term MAY be attached to an Object Class Term or a Property Term if necessary
to make a name unique. |
Manual |
None |
| GD-21 |
When a name contains an Object Class Term, a Property Term, and a Representation Term,
the Object Class Term MUST precede the Property Term and the Property Term MUST precede
the Representation Term. A Qualifier Term SHOULD precede the associated Object Class
Term or Property Term. |
Manual |
None |
| GD-22 |
If the Property Term ends with the same word as the Representation Term (or an equivalent
word) then the Representation Term MUST be removed.
| GD-22/1.xsd |
Successfully validated: No error for component: "NoRepeatedRepresentationRate". |
| GD-22/2.xsd |
Successfully validated: Identified error for component: "ThisQuantityQuantity". ThisQuantityQuantity
contains a repeated representation term (Quantity).
|
| GD-22/3.xsd |
Successfully validated: Identified error for component: "ThatRateRate". ThatRateRate
contains a repeated representation term (Rate).
|
| GD-22/4.xsd |
Successfully validated: Identified error for component: "SimpleAmountAmountType".
SimpleAmountAmountType contains a repeated representation term (Amount).
|
| GD-22/5.xsd |
Successfully validated: Identified error for component: "ComplexCategoryCategoryType".
ComplexCategoryCategoryType contains a repeated representation term (Category).
|
|
Auto |
Pass |
| GD-23 |
Where a representation term is required, the Representation Terms in Appendix B MUST
be used for representation terms in Basic component names.
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E0Text". E0Text
must have
Amount as a representation term, not Text. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E1Rate". E1Rate
must have
Category, Code, Identifier, Number, Text or Name as a representation term, not Rate. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E2Percent". E2Percent
must have
Category, Code, Identifier, Number, Text or Name as a representation term, not Percent. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E3Time". E3Time
must have
Date as a representation term, not Time. E3Time uses com:DateType |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E4Time". E4Time
must have
Date as a representation term, not Time. E4Time uses xsd:date |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E6Identifier". E6Identifier
must have
Indicator as a representation term, not Identifier. E6Identifier uses xsd:boolean |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E7Rate". E7Rate
must have
Measure as a representation term, not Rate. E7Rate uses com:MeasureType |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E8Quantity". E8Quantity
must have
Text, Name, Number, Identifier or Category as a representation term, not Quantity. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E9URI". E9URI
must have
Number as a representation term, not URI. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E10Percent". E10Percent
must have
Text, Name, Number, Identifier or Category as a representation term, not Percent. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E12Category". E12Category
must have
Percent, Rate or Quantity as a representation term, not Category. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E13". E13
must have
Quantity as a representation term, but it has none. E13 uses com:QuantityType |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E14". E14
must have
Quantity as a representation term, but it has none. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E15". E15
must have
Percent, Rate or Quantity as a representation term, but it has none. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E16". E16
must have
Text, Name, Number, Identifier or Category as a representation term, but it has none. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E17". E17
must have
Text, Name or Number as a representation term, but it has none. |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E18". E18
must have
Time as a representation term, but it has none. E18 uses xsd:time |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E19". E19
must have
DateTime as a representation term, but it has none. E19 uses xsd:dateTime |
| GD-23/1.xsd |
Successfully validated: Identified error for component: "E20". E20
must have
URI as a representation term, but it has none. E20 uses xsd:anyURI |
| GD-23/10.xsd |
Successfully validated: No error for component: "E1Number". |
| GD-23/11.xsd |
Successfully validated: No error for component: "E2Number". |
| GD-23/12.xsd |
Successfully validated: No error for component: "E3Number". |
| GD-23/13.xsd |
Successfully validated: No error for component: "EPercent". |
| GD-23/14.xsd |
Successfully validated: No error for component: "E1Quantity". |
| GD-23/15.xsd |
Successfully validated: No error for component: "E2Quantity". |
| GD-23/16.xsd |
Successfully validated: No error for component: "ERate". |
| GD-23/17.xsd |
Successfully validated: No error for component: "E1Text". |
| GD-23/18.xsd |
Successfully validated: No error for component: "E2Text". |
| GD-23/19.xsd |
Successfully validated: No error for component: "ETime". |
| GD-23/2.xsd |
Successfully validated: No error for component: "E1Date". |
| GD-23/20.xsd |
Successfully validated: No error for component: "EDateTime". |
| GD-23/21.xsd |
Successfully validated: No error for component: "E_URI". |
| GD-23/22.xsd |
Successfully validated: No error for component: "NonBasicElementWithoutRepresentationTerm". |
| GD-23/23.xsd |
Successfully validated: No error for component: "NonBasicElementWithoutRepresentationTermText". |
| GD-23/24.xsd |
Successfully validated: No error for component: "E5Text". |
| GD-23/25.xsd |
Successfully validated: Identified error for component: "BadDuration". BadDuration
is a basic component which must have a representation term, but it has none. Representation
terms from Appendix B are: Amount, Category, Code, Date, Identifier, Indicator, Measure,
Name, Number, Percent, Quantity, Rate, Text, Time, DateTime, URI.
|
| GD-23/3.xsd |
Successfully validated: No error for component: "EAmount". |
| GD-23/4.xsd |
Successfully validated: No error for component: "E1Category". |
| GD-23/5.xsd |
Successfully validated: No error for component: "E2Date". |
| GD-23/6.xsd |
Successfully validated: No error for component: "EIdentifier". |
| GD-23/7.xsd |
Successfully validated: No error for component: "EIndicator". |
| GD-23/8.xsd |
Successfully validated: No error for component: "EMeasure". |
| GD-23/9.xsd |
Successfully validated: No error for component: "EName". |
| GD-23/Common/IPRightDurationPeriod.xsd |
Successfully validated: Identified error for component: "IPRightDurationPeriod".
IPRightDurationPeriod
must have
Date as a representation term, but it has none. IPRightDurationPeriod uses com:DateType |
| GD-23/endnoteNumber.xsd |
Successfully validated: No error for component: "endnoteNumber". |
| GD-23/GeographicalIndication/GIApplicantGroupID.xsd |
Successfully validated: Identified error for component: "GIApplicantGroupID". GIApplicantGroupID
must have
Category, Code, Identifier, Number, Text or Name as a representation term, but it
has none. |
| GD-23/GeographicalIndication/ProductionMaximumAmountQuantity.xsd |
Successfully validated: Identified error for component: "ProductionMaximumAmountQuantity".
ProductionMaximumAmountQuantity
must have
Category, Code, Identifier, Number, Text or Name as a representation term, not Quantity. |
| GD-23/Patent/SequenceCancelledIdentifier.xsd |
Successfully validated: Identified error for component: "SequenceCancelledIdentifier".
SequenceCancelledIdentifier
must have
Text as a representation term, not Identifier. |
|
Auto |
Pass |
| GD-24 |
Within a namespace, all type, element and attribute names MUST be unique.
| GD-24/1.xsd |
Successfully validated: Identified error for component: "a". element Name a is not
unique.
| attribute Name a is not unique.
|
| GD-24/1.xsd |
Successfully validated: Identified error for component: "b". element Name b is not
unique.
| simpleType Name b is not unique.
|
| GD-24/1.xsd |
Successfully validated: Identified error for component: "c". attribute Name c is
not unique.
| complexType Name c is not unique.
|
| GD-24/2.xsd |
Successfully validated: No error for component: "d". |
| GD-24/DesignLegalStatusData.xsd |
Successfully validated: Identified error for component: "DesignLegalStatusData".
Name DesignLegalStatusData is not unique. Found element in DesignLegalStatusData.xsd,
Document/DesignLegalStatusData_V8_0.xsd| Locally run:
Name DesignLegalStatusData is not unique. Found element in GD-24/DesignLegalStatusData.xsd*,
Document/DesignLegalStatusData_V8_0.xsd* |
| GD-24/DesignLegalStatusDataType.xsd |
Successfully validated: Identified error for component: "DesignLegalStatusDataType".
Name DesignLegalStatusDataType is not unique. Found complexType in DesignLegalStatusDataType.xsd,
Document/DesignLegalStatusDataType_V8_0.xsd| Locally run:
Name DesignLegalStatusDataType is not unique. Found complexType in GD-24/DesignLegalStatusDataType.xsd*,
Document/DesignLegalStatusDataType_V8_0.xsd* |
|
Auto |
Pass |
| GD-25 |
Word(s) in a name SHOULD be in singular form unless the concept itself is plural.
For example, TotalMarkSeries.
| GD-25/Claims.xsd |
Successfully validated: No error for component: "Claims". |
| GD-25/OppositionGroundsText.xsd |
Successfully validated: Identified error for component: "OppositionGroundsText".
Possible plural form in name of component OppositionGroundsText: Grounds |
|
Partial |
Pass |
| GD-26 |
The name of an element or a type which contains a collection of contextually related
components SHOULD have the “Bag” suffix. For example, EmailAddressBag represents
a collection of EmailAddress elements.
| GD-26/1.xsd |
Failed: No error for component: "HType". |
| GD-26/5.xsd |
Failed: Identified error for component: "IBagType".
The 'IBagType' complexType is not a collection, but its name has a 'BagType' suffix.
It does not have at least one element which repeats.
|
| GD-26/6.xsd |
Failed: Identified error for component: "LBag".
The 'LBag' element is not a collection, but its name has a 'Bag' suffix. It does not
have at least one element which repeats.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "BList".
The 'BList' element is a collection, but its name lacks a 'Bag' suffix.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "CBag".
The 'CBag' element is not a collection, but its name has a 'Bag' suffix. It does not
have at least one element which repeats.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "DBagType".
The 'DBagType' simpleType is not a collection of elements, but its name has a 'BagType'
suffix.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "FType".
The 'FType' complexType is a collection, but its name lacks a 'BagType' suffix.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "GBagType".
The 'GBagType' complexType is not a collection, but its name has a 'BagType' suffix.
It does not have at least one element which repeats.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "NBag".
The 'NBag' element is not a collection, but its name has a 'Bag' suffix. It does not
have at least one element which repeats.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "OBagType".
The 'OBagType' complexType is not a collection, but its name has a 'BagType' suffix.
It does not have at least one element which repeats.
|
| GD-26/1.xsd |
Successfully validated: Identified error for component: "BoundaryData2BagType".
The 'BoundaryData2BagType' complexType is not a collection, but its name has a 'BagType'
suffix. It does not have at least one element which repeats.
|
| GD-26/2.xsd |
Successfully validated: No error for component: "ABag". |
| GD-26/3.xsd |
Successfully validated: No error for component: "EBagType". |
| GD-26/4.xsd |
Successfully validated: No error for component: "HIBagType". |
| GD-26/7.xsd |
Successfully validated: No error for component: "MBag". |
| GD-26/8.xsd |
Successfully validated: No error for component: "BoundaryDataBagType". |
|
Partial |
Fail |
| GD-27 |
Connecting words like “and”, “of” and “the” SHOULD NOT be used in type, element, and
attribute names unless they are part of the business terminology.
| GD-27/1.xsd |
Successfully validated: No error for component: "Good". |
| GD-27/2.xsd |
Successfully validated: No error for component: "BadandWorse". |
| GD-27/3.xsd |
Successfully validated: Identified error for component: "BadAndWorse".
Name of element BadAndWorse
contains the connecting word(s) And.
|
| GD-27/3.xsd |
Successfully validated: Identified error for component: "FigureOfSpeech".
Name of element FigureOfSpeech
contains the connecting word(s) Of.
|
| GD-27/3.xsd |
Successfully validated: Identified error for component: "BreakTheRule".
Name of element BreakTheRule
contains the connecting word(s) The.
|
| GD-27/3.xsd |
Successfully validated: Identified error for component: "TheViolationIsFirst".
Name of element TheViolationIsFirst
contains the connecting word(s) The.
|
|
Partial |
Pass |
| GD-28 |
Type, element and attribute names MUST NOT be translated, changed or replaced for
any purpose. |
Manual |
None |
| GD-29 |
Type and element names MUST NOT refer to article and rule numbers. For example, PCTRule702C
for the PCT.
| GD-29/1.xsd |
Successfully validated: No error for component: "ArtNumber12". |
| GD-29/2.xsd |
Successfully validated: No error for component: "Article". |
| GD-29/3.xsd |
Successfully validated: Identified error for component: "Article12".
The name Article12 contains an article or rule number (Article followed by a digit).
|
| GD-29/3.xsd |
Successfully validated: Identified error for component: "BeginningArticle12".
The name BeginningArticle12 contains an article or rule number (Article followed by
a digit).
|
| GD-29/3.xsd |
Successfully validated: Identified error for component: "Rule12".
The name Rule12 contains an article or rule number (Rule followed by a digit).
|
| GD-29/3.xsd |
Successfully validated: Identified error for component: "ItsRule12WithSomethingAfter".
The name ItsRule12WithSomethingAfter contains an article or rule number (Rule followed
by a digit).
|
|
Partial |
Pass |
| GD-30 |
The characters used in Schema filenames MUST belong to the following set: ‘a-z, A-Z,
0-9’, underscore “_”, and period “.”.
| GD-30/bad 1.xsd |
Successfully validated: Identified error for schema: bad%201.xsd.
The file name bad%201.xsd contains invalid
characters.
|
| GD-30/bad+1.xsd |
Successfully validated: Identified error for schema: bad+1.xsd.
The file name bad+1.xsd contains invalid
characters.
|
| GD-30/bad-1.xsd |
Successfully validated: Identified error for schema: bad-1.xsd.
The file name bad-1.xsd contains invalid
characters.
|
| GD-30/good_1.xsd |
Successfully validated: No error for schema: good_1.xsd. |
|
Auto |
Pass |
| GD-31 |
A Schema filename MUST consist of component name, optional version information, and
file extension, i.e., <component name>{“_”“V”<major version number>“_”<minor version
number>“_”<patch version number>}“.”<file extension>; and the version information
applies only to document level schemas, for example, EmailAddressType.xsd, languageCode.xsd,
ApplicationBody_V1_0.xsd, TrademarkApplication_V4_0_1.xsd.
| GD-31/BadDraft.xsd |
Successfully validated: Identified error for schema: BadDraft.xsd.
The file name BadDraft.xsd does not follow the required format <Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| GD-31/Bad_1_0.xsd |
Successfully validated: Identified error for schema: Bad_1_0.xsd.
The file name Bad_1_0.xsd does not follow the required format <Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| GD-31/DesignClaimBagTextType.xsd |
Successfully validated: Identified error for schema: DesignClaimBagTextType.xsd.
The file name DesignClaimBagTextType.xsd does not follow the required format <DesignClaimTextBagType>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| GD-31/Document/BibliographicData_V1_0.xsd |
Successfully validated: Identified error for schema: BibliographicData_V1_0.xsd.
The file name BibliographicData_V1_0.xsd does not match the @version attribute value
V4_2 |
| GD-31/Good.xsd |
Successfully validated: No error for schema: Good.xsd. |
| GD-31/GoodPatch_V4_2_1.xsd |
Successfully validated: No error for schema: GoodPatch_V4_2_1.xsd. |
| GD-31/Good_V1_0.xsd |
Successfully validated: No error for schema: Good_V1_0.xsd. |
| GD-31/Good_V1_0_D1.xsd |
Successfully validated: No error for schema: Good_V1_0_D1.xsd. |
|
Auto |
Pass |
| GD-32 |
A draft Schema filename MUST consist of component name, optional version information,
and file extension, i.e., <component name>{“_”“V”<major version number>“_”<minor version
number>“_”“D”<revision number>}“.”<file extension>; and the version information applies
only to document level schemas, for example, TrademarkApplication_V1_1_D1.xsd. If
a draft schema is based on an existing schema and has version information in its filename,
the major and minor version numbers in the draft schema filename SHOULD be the same
as specified in the schema file that the draft schema is based on. If a draft schema
is new, the major version number in the draft schema filename SHOULD be the same number
as specified in the corresponding namespace and a minor version number in the draft
schema file SHOULD be zero “0”.
| GD-32/Bad_1_0_D3.xsd |
Successfully validated: Identified error for schema: Bad_1_0_D3.xsd.
The file name Bad_1_0_D3.xsd does not follow the required format for drafts: <Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_D<RevisionNumber>}.<FileExtension>
|
| GD-32/Bad_V1_0_D2.xsd |
Successfully validated: Identified error for schema: Bad_V1_0_D2.xsd.
The version in XSD name Bad_V1_0_D2.xsd (V1_0) is inconsistent with the version given
by schema/@version (V2_0).
|
| GD-32/Bad_V1_0_d3.xsd |
Successfully validated: Identified error for schema: Bad_V1_0_d3.xsd.
The file name Bad_V1_0_d3.xsd does not follow the required format for drafts: <Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_D<RevisionNumber>}.<FileExtension>
|
| GD-32/Bad_V1_0_draft.xsd |
Successfully validated: Identified error for schema: Bad_V1_0_draft.xsd.
The file name Bad_V1_0_draft.xsd does not follow the required format for drafts:
<DummyText>{_V<MajorVersionNumber>_<MinorVersionNumber>_D<RevisionNumber>}.<FileExtension>
|
| GD-32/Good_D1.xsd |
Successfully validated: No error for schema: Good_D1.xsd. |
| GD-32/Good_V1_0_D2.xsd |
Successfully validated: No error for schema: Good_V1_0_D2.xsd. |
|
Auto |
Pass |
| GD-33 |
A test Schema filename MUST consist of component name, optional version information,
and file extension, i.e., <component name>{“_”“V”<major version number>“_”<minor version
number>“_”“T”<revision number>}“.”<file extension>; and the version information applies
only to document level schemas, for example, TrademarkApplication_V4_0_T1.xsd.
| GD-33/Bad_1_0_T3.xsd |
Successfully validated: Identified error for schema: Bad_1_0_T3.xsd.
The file name Bad_1_0_T3.xsd does not follow the required format for test schemas:
<Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_T<RevisionNumber>}.<FileExtension>
|
| GD-33/Bad_T1.xsd |
Successfully validated: Identified error for schema: Bad_T1.xsd.
The file name Bad_T1.xsd does not follow the required format for test schemas: <Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_T<RevisionNumber>}.<FileExtension>
|
| GD-33/Bad_V1_0_t3.xsd |
Successfully validated: Identified error for schema: Bad_V1_0_t3.xsd.
The file name Bad_V1_0_t3.xsd does not follow the required format for test schemas:
<Bad>{_V<MajorVersionNumber>_<MinorVersionNumber>_T<RevisionNumber>}.<FileExtension>
|
| GD-33/Good_V1_0_T2.xsd |
Successfully validated: No error for schema: Good_V1_0_T2.xsd. |
|
Auto |
Pass |
| SD-01 |
Patent Component schema modules, Trademark Component schema modules, Design Component
schema modules, Geographical Indication Component schema modules, and Copyright Component
schema modules MUST use the xsd:import construct to reference Common Component schema
modules.
| SD-01/1b.xsd |
Failed: No error for schema: 1b.xsd. |
| SD-01/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-01/1c.xsd |
Successfully validated: No error for schema: 1c.xsd. |
| SD-01/2.xsd |
Successfully validated: No error for schema: 2.xsd. |
| SD-01/2b.xsd |
Successfully validated: Identified error for schema: 2b.xsd.
The xsd:import construct must reference a schema module using the attribute @schemaLocation
|
| SD-01/2c.xsd |
Successfully validated: No error for schema: 2c.xsd. |
| SD-01/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-01/3c.xsd |
Successfully validated: No error for schema: 3c.xsd. |
| SD-01/4.xsd |
Successfully validated: No error for schema: 4.xsd. |
| SD-01/4b.xsd |
Successfully validated: Identified error for schema: 4b.xsd.
The xsd:import construct must reference a schema module using the attribute @schemaLocation
|
| SD-01/4c.xsd |
Successfully validated: No error for schema: 4c.xsd. |
| SD-01/5.xsd |
Successfully validated: No error for schema: 5.xsd. |
| SD-01/5b.xsd |
Successfully validated: Identified error for schema: 5b.xsd.
The xsd:import construct must reference a schema module using the attribute @schemaLocation
|
| SD-01/5c.xsd |
Successfully validated: No error for schema: 5c.xsd. |
| SD-01/6.xsd |
Successfully validated: No error for schema: 6.xsd. |
| SD-01/6b.xsd |
Successfully validated: Identified error for schema: 6b.xsd.
The xsd:import construct must reference a schema module using the attribute @schemaLocation
|
| SD-01/6c.xsd |
Successfully validated: No error for schema: 6c.xsd. |
|
Auto |
Fail |
| SD-02 |
Common Component schema modules MUST NOT refer to Patent Component schema modules,
Trademark Component schema modules, Design Component schema modules, Geographical
Indication Component schema modules or Copyright Component schema modules.
| SD-02/10a.xsd |
Successfully validated: Identified error for schema: 10a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:dissemination.
|
| SD-02/10b.xsd |
Successfully validated: Identified error for schema: 10b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:dissemination.
|
| SD-02/11a.xsd |
Successfully validated: Identified error for schema: 11a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:legal.
|
| SD-02/11b.xsd |
Successfully validated: Identified error for schema: 11b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:legal.
|
| SD-02/1a.xsd |
Successfully validated: No error for schema: 1a.xsd. |
| SD-02/1b.xsd |
Successfully validated: No error for schema: 1b.xsd. |
| SD-02/2a.xsd |
Successfully validated: Identified error for schema: 2a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Patent.
|
| SD-02/2b.xsd |
Successfully validated: Identified error for schema: 2b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Patent.
|
| SD-02/3a.xsd |
Successfully validated: Identified error for schema: 3a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-02/3b.xsd |
Successfully validated: Identified error for schema: 3b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-02/4a.xsd |
Successfully validated: Identified error for schema: 4a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Design.
|
| SD-02/4b.xsd |
Successfully validated: Identified error for schema: 4b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
http://www.wipo.int/standards/XMLSchema/ST96/Design.
|
| SD-02/5a.xsd |
Successfully validated: Identified error for schema: 5a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:patent.
|
| SD-02/5b.xsd |
Successfully validated: Identified error for schema: 5b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:patent.
|
| SD-02/6a.xsd |
Successfully validated: Identified error for schema: 6a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:trademark.
|
| SD-02/6b.xsd |
Successfully validated: Identified error for schema: 6b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:trademark.
|
| SD-02/7a.xsd |
Successfully validated: Identified error for schema: 7a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:design.
|
| SD-02/7b.xsd |
Successfully validated: Identified error for schema: 7b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:design.
|
| SD-02/8a.xsd |
Successfully validated: No error for schema: 8a.xsd. |
| SD-02/8b.xsd |
Successfully validated: No error for schema: 8b.xsd. |
| SD-02/9a.xsd |
Successfully validated: Identified error for schema: 9a.xsd.
XSDs in the urn:us:gov:doc:uspto:common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:corporate.
|
| SD-02/9b.xsd |
Successfully validated: Identified error for schema: 9b.xsd.
XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace
may not refer to XSDs in the following namespace(s):
urn:us:gov:doc:uspto:corporate.
|
|
Auto |
Pass |
| SD-03 |
A Patent Component, Trademark Component, Design Component, Geographical Indication
Component, or Copyright Component MAY make reference to Common Component schema modules,
schemas in the same Component module, and approved industry-standard schemas, but
SHOULD NOT refer to other Component schema modules, with two exceptions: Geographical
Indication Component schemas MAY refer to Trademark Components schemas and vice versa
and Patent Component schemas MAY refer to Design Component schemas and vice versa,
as they have overlapping business areas
| SD-03/1b.xsd |
Successfully validated: Identified error for schema: 1b.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Patent
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-03/1c.xsd |
Successfully validated: Identified error for schema: 1c.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Patent
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:trademark,
urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination, urn:us:gov:doc:uspto:legal.
|
| SD-03/2b.xsd |
Successfully validated: Identified error for schema: 2b.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Trademark
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Patent,
http://www.wipo.int/standards/XMLSchema/ST96/Design. |
| SD-03/2c.xsd |
Successfully validated: Identified error for schema: 2c.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Trademark
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:patent,
urn:us:gov:doc:uspto:design, urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination,
urn:us:gov:doc:uspto:legal. |
| SD-03/3b.xsd |
Successfully validated: Identified error for schema: 3b.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Design
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-03/3c.xsd |
Successfully validated: Identified error for schema: 3c.xsd. XSDs in the http://www.wipo.int/standards/XMLSchema/ST96/Design
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:trademark,
urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination, urn:us:gov:doc:uspto:legal.
|
| SD-03/4b.xsd |
Successfully validated: Identified error for schema: 4b.xsd. XSDs in the urn:us:gov:doc:uspto:patent
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-03/4c.xsd |
Successfully validated: Identified error for schema: 4c.xsd. XSDs in the urn:us:gov:doc:uspto:patent
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:trademark,
urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination, urn:us:gov:doc:uspto:legal.
|
| SD-03/5b.xsd |
Successfully validated: Identified error for schema: 5b.xsd. XSDs in the urn:us:gov:doc:uspto:trademark
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Patent,
http://www.wipo.int/standards/XMLSchema/ST96/Design. |
| SD-03/5c.xsd |
Successfully validated: Identified error for schema: 5c.xsd. XSDs in the urn:us:gov:doc:uspto:trademark
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:patent,
urn:us:gov:doc:uspto:design, urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination,
urn:us:gov:doc:uspto:legal. |
| SD-03/6b.xsd |
Successfully validated: Identified error for schema: 6b.xsd. XSDs in the urn:us:gov:doc:uspto:design
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Trademark.
|
| SD-03/6c.xsd |
Successfully validated: Identified error for schema: 6c.xsd. XSDs in the urn:us:gov:doc:uspto:design
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:trademark,
urn:us:gov:doc:uspto:corporate, urn:us:gov:doc:uspto:dissemination, urn:us:gov:doc:uspto:legal.
|
| SD-03/7b.xsd |
Successfully validated: Identified error for schema: 7b.xsd. XSDs in the urn:us:gov:doc:uspto:corporate
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Patent,
http://www.wipo.int/standards/XMLSchema/ST96/Trademark, http://www.wipo.int/standards/XMLSchema/ST96/Design.
|
| SD-03/7c.xsd |
Successfully validated: Identified error for schema: 7c.xsd. XSDs in the urn:us:gov:doc:uspto:corporate
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:patent,
urn:us:gov:doc:uspto:trademark, urn:us:gov:doc:uspto:design, urn:us:gov:doc:uspto:dissemination,
urn:us:gov:doc:uspto:legal. |
| SD-03/8b.xsd |
Successfully validated: Identified error for schema: 8b.xsd. XSDs in the urn:us:gov:doc:uspto:dissemination
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Patent,
http://www.wipo.int/standards/XMLSchema/ST96/Trademark, http://www.wipo.int/standards/XMLSchema/ST96/Design.
|
| SD-03/8c.xsd |
Successfully validated: Identified error for schema: 8c.xsd. XSDs in the urn:us:gov:doc:uspto:dissemination
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:patent,
urn:us:gov:doc:uspto:trademark, urn:us:gov:doc:uspto:design, urn:us:gov:doc:uspto:corporate,
urn:us:gov:doc:uspto:legal. |
| SD-03/9b.xsd |
Successfully validated: Identified error for schema: 9b.xsd. XSDs in the urn:us:gov:doc:uspto:legal
namespace may not refer to XSDs in the following namespace(s): http://www.wipo.int/standards/XMLSchema/ST96/Patent,
http://www.wipo.int/standards/XMLSchema/ST96/Trademark, http://www.wipo.int/standards/XMLSchema/ST96/Design.
|
| SD-03/9c.xsd |
Successfully validated: Identified error for schema: 9c.xsd. XSDs in the urn:us:gov:doc:uspto:legal
namespace may not refer to XSDs in the following namespace(s): urn:us:gov:doc:uspto:patent,
urn:us:gov:doc:uspto:trademark, urn:us:gov:doc:uspto:design, urn:us:gov:doc:uspto:corporate,
urn:us:gov:doc:uspto:dissemination. |
| SD-03/DesignPatentBibliographicDataType_V8_1.xsd |
Successfully validated: No error for schema: DesignPatentBibliographicDataType_V8_1.xsd. |
| SD-03/GIComponentType.xsd |
Successfully validated: No error for schema: GIComponentType.xsd. |
| SD-03/TrademarkComponentType.xsd |
Successfully validated: No error for schema: TrademarkComponentType.xsd. |
|
Auto |
Pass |
| SD-04 |
Existing schemas MUST be used wherever applicable prior to creating new schemas.
| SD-04/duplicates.xsd |
Successfully validated: Identified error for component: "ClaimNumberRangeType".
The complexType ClaimNumberRangeType has an identical model with pat:AlloyCompositionRangeType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The complexType ClaimNumberRangeType has an identical model with pat:AlloyCompositionRangeType*.
Consider reusing existing complexTypes based on business needs.
|
| SD-04/duplicates.xsd |
Successfully validated: Identified error for component: "AlloyCompositionRangeType".
The complexType AlloyCompositionRangeType has an identical model with pat:ClaimNumberRangeType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The complexType AlloyCompositionRangeType has an identical model with
pat:ClaimNumberRangeType*. Consider reusing existing complexTypes based on business
needs.
|
| SD-04/Patent/ECLAClassificationValueCodeType.xsd |
Successfully validated: Identified error for component: "ECLAClassificationValueCodeType".
The simpleType ECLAClassificationValueCodeType has an identical model with pat:IPCClassificationValueCodeType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The simpleType ECLAClassificationValueCodeType has an identical model
with pat:IPCClassificationValueCodeType*. Consider reusing existing complexTypes based
on business needs.
|
| SD-04/Patent/ExaminationRequesterCategoryType.xsd |
Successfully validated: Identified error for component: "ExaminationRequesterCategoryType".
The simpleType ExaminationRequesterCategoryType has an identical model with pat:SearchRequesterCategoryType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The simpleType ExaminationRequesterCategoryType has an identical model
with pat:SearchRequesterCategoryType*. Consider reusing existing complexTypes based
on business needs.
|
| SD-04/Patent/IPCClassificationValueCodeType.xsd |
Successfully validated: Identified error for component: "IPCClassificationValueCodeType".
The simpleType IPCClassificationValueCodeType has an identical model with pat:ECLAClassificationValueCodeType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The simpleType IPCClassificationValueCodeType has an identical model
with pat:ECLAClassificationValueCodeType*. Consider reusing existing complexTypes
based on business needs.
|
| SD-04/Patent/SearchRequesterCategoryType.xsd |
Successfully validated: Identified error for component: "SearchRequesterCategoryType".
The simpleType SearchRequesterCategoryType has an identical model with pat:ExaminationRequesterCategoryType.
Consider reusing existing complexTypes based on business needs.
| Locally run: The simpleType SearchRequesterCategoryType has an identical model
with pat:ExaminationRequesterCategoryType*. Consider reusing existing complexTypes
based on business needs.
|
|
Partial |
Pass |
| SD-05 |
Schemas SHOULD use elements and types defined in existing schemas to the maximum extent
possible.
| SD-05/Common/FigurativeElementClassificationBag.xsd |
Successfully validated: No error for component: "FigurativeElementClassificationBag". |
| SD-05/Common/FigurativeElementClassificationBagType.xsd |
Successfully validated: No error for component: "FigurativeElementClassificationBagType". |
| SD-05/Trademark/FigurativeElementClassificationBag.xsd |
Successfully validated: Identified error for component: "FigurativeElementClassificationBag".
The xsd:element tmk:FigurativeElementClassificationBag has a duplicate name with com:FigurativeElementClassificationBag.
Consider whether the Common component should be used instead.
| Locally run:
The xsd:element tmk:FigurativeElementClassificationBag has a duplicate name with com:FigurativeElementClassificationBag*.
Consider whether the Common component should be used instead.
|
| SD-05/Trademark/FigurativeElementClassificationBagType.xsd |
Successfully validated: Identified error for component: "FigurativeElementClassificationBagType".
The xsd:complexType tmk:FigurativeElementClassificationBagType has a duplicate name
with com:FigurativeElementClassificationBagType. Consider whether the Common component
should be used instead.
| Locally run:
The xsd:complexType tmk:FigurativeElementClassificationBagType has a duplicate name
with com:FigurativeElementClassificationBagType*. Consider whether the Common component
should be used instead.
|
|
Partial |
Pass |
| SD-06 |
All types, elements and attributes MUST be globally declared.
| SD-06/1.xsd |
Successfully validated: Identified error for component: "LocallyDeclaredComplexType".
LocallyDeclaredComplexType (xs:complexType) is declared locally. |
| SD-06/1.xsd |
Successfully validated: Identified error for component: "LocallyDeclaredElement".
LocallyDeclaredElement (xs:element) is declared locally. |
| SD-06/1.xsd |
Successfully validated: Identified error for component: "LocallyDeclaredSimpleType".
LocallyDeclaredSimpleType (xs:simpleType) is declared locally. |
| SD-06/1.xsd |
Successfully validated: Identified error for component: "LocallyDeclaredAttribute".
LocallyDeclaredAttribute (xs:attribute) is declared locally. |
| SD-06/2.xsd |
Successfully validated: No error for component: "GloballyDeclaredComplexType". |
| SD-06/3.xsd |
Successfully validated: No error for component: "GloballyDeclaredSimpleType". |
| SD-06/4.xsd |
Successfully validated: No error for component: "GloballyDeclaredAttribute". |
|
Auto |
Pass |
| SD-07 |
Schemas MUST NOT use xsd:redefine construct.
| SD-07/redefine.xsd |
Successfully validated: Identified error for schema: redefine.xsd.
xsd:redefine must not be used.
|
|
Auto |
Pass |
| SD-08 |
Schemas MUST use namespaces.
| SD-08/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-08/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
xsd:schema has no targetNamespace attribute.
|
|
Auto |
Pass |
| SD-09 |
Published namespace declarations SHOULD NOT be changed.
| SD-09/1.xsd |
Successfully validated: Identified error for schema: 1.xsd.
Imported namespace urn:us:gov:doc:uspto:foo is not one of the baseline namespaces.
|
Imported namespace foo is not one of the baseline namespaces.
|
| SD-09/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
Target namespace foo is not one of the baseline namespaces.
|
|
Partial |
Pass |
| SD-10 |
Schemas MUST declare the W3C Schema namespace.
| SD-10/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-10/2.xsd |
Successfully validated: No error for schema: 2.xsd. |
|
Auto |
Pass |
| SD-11 |
Schemas MUST use namespace qualifications for all W3C Schema constructs.
| SD-11/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-11/2.xsd |
Successfully validated: Identified error for schema: 2.xsd. A namespace prefix must
be used for the http://www.w3.org/2001/XMLSchema namespace. |
|
Auto |
Pass |
| SD-12 |
Schemas MUST use the URI-formatted namespace.
| SD-12/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-12/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-12/2.xsd |
Successfully validated: No error for schema: 2.xsd. |
| SD-12/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
@targetNamespace= is not a valid URI.
|
| SD-12/5.xsd |
Successfully validated: Identified error for schema: 5.xsd.
@targetNamespace=NOT-A-URI is not a valid URI.
|
| SD-12/6.xsd |
Successfully validated: Identified error for schema: 6.xsd.
@targetNamespace=https://www.wipo.int/standards/en/st96/v8-0/annex-i/this is a bad
uri.pdf is not a valid URI.
|
|
Auto |
Pass |
| SD-13 |
All schemas MUST have attributes elementFormDefault and attributeFormDefault with
value “qualified” in the root xsd:schema element.
| SD-13/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-13/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
@elementFormDefault must be qualified.
|
@attributeFormDefault must be qualified.
|
| SD-13/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
@elementFormDefault must be qualified.
|
@attributeFormDefault must be qualified.
|
|
Auto |
Pass |
| SD-14 |
The names for namespaces MUST have the following structure: http://www.wipo.int/standards/XMLSchema/ST96/<category>;
where <category> is a token identifying the domain of Schema being used: Common,
Patent, Trademark, Design, GeographicalIndication or Copyright.
| SD-14/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-14/Common/2.xsd |
Successfully validated: No error for schema: 2.xsd. |
| SD-14/Common/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
Namespace http://www.wipo.int/standards/XMLSchema/ST96/BAD does not follow the proper
form.
|
| SD-14/Common/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
Namespace http://www.wipo.int/standards/XMLSchema/ST96/BAD/Common does not follow
the proper form.
|
| SD-14/Design/5.xsd |
Successfully validated: No error for schema: 5.xsd. |
| SD-14/Patent/6.xsd |
Successfully validated: No error for schema: 6.xsd. |
| SD-14/Patent/7.xsd |
Successfully validated: Identified error for schema: 7.xsd.
Namespace http://www.wipo.int/standards/XMLSchema/ST96/BAD does not follow the proper
form.
|
| SD-14/Patent/Document/18.xsd |
Successfully validated: No error for schema: 18.xsd. |
| SD-14/Patent/Document/19.xsd |
Successfully validated: Identified error for schema: 19.xsd.
Namespace http://www.wipo.int/standards/XMLSchema/ST96/BAD does not follow the proper
form.
|
| SD-14/Trademark/8.xsd |
Successfully validated: No error for schema: 8.xsd. |
| SD-14/USCommon/9.xsd |
Successfully validated: No error for schema: 9.xsd. |
|
Auto |
Pass |
| SD-15 |
Schemas SHOULD use “xsd” as a namespace prefix for all W3C Schema constructs, “com”
for all Common Component Schemas, “pat” for all Patent Component Schemas, “tmk” for
all Trademark Component Schemas, “dgn” for all Design Component Schemas, “gin” for
Geographical Indication Component Schemas, “cpy” for Copyright Component schemas,
“tbl” for OASIS Table Component Schemas and “mathml” for MathML Component Schemas
| SD-15/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-15/2.xsd |
Successfully validated: Identified error for schema: 2.xsd. com: prefix (not co:)
must be used for the http://www.wipo.int/standards/XMLSchema/ST96/Common namespace.,
pat: prefix (not pa:) must be used for the http://www.wipo.int/standards/XMLSchema/ST96/Patent
namespace., dgn: prefix (not dg:) must be used for the http://www.wipo.int/standards/XMLSchema/ST96/Design
namespace., tmk: prefix (not tm:) must be used for the http://www.wipo.int/standards/XMLSchema/ST96/Trademark
namespace., tbl: prefix (not tb:) must be used for the http://www.oasis-open.org/tables/exchange/1.0
namespace., mathml: prefix (not ma:) must be used for the http://www.w3.org/1998/Math/MathML3
namespace. |
| SD-15/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-15/4.xsd |
Successfully validated: No error for schema: 4.xsd. |
| SD-15/5.xsd |
Successfully validated: Identified error for schema: 5.xsd. uscom: prefix (not usco:)
must be used for the urn:us:gov:doc:uspto:common namespace., uspat: prefix (not uspa:)
must be used for the urn:us:gov:doc:uspto:patent namespace., usdgn: prefix (not usdg:)
must be used for the urn:us:gov:doc:uspto:design namespace., ustmk: prefix (not ustm:)
must be used for the urn:us:gov:doc:uspto:trademark namespace., uscor: prefix (not
uscorp:) must be used for the urn:us:gov:doc:uspto:corporate namespace., usdis: prefix
(not usdi:) must be used for the urn:us:gov:doc:uspto:dissemination namespace., usleg:
prefix (not usle:) must be used for the urn:us:gov:doc:uspto:legal namespace., tbl:
prefix (not tb:) must be used for the http://www.oasis-open.org/tables/exchange/1.0
namespace., mathml: prefix (not ma:) must be used for the http://www.w3.org/1998/Math/MathML3
namespace. |
|
Auto |
Pass |
| SD-16 |
Every schema MUST declare the target namespace using the xsd:targetNamespace attribute.
| SD-16/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-16/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
xsd:schema has no targetNamespace attribute.
|
|
Auto |
Pass |
| SD-17 |
The schema’s targetNamespace MUST match the namespace name of one of the declared
namespaces, but not the W3C namespace.
| SD-17/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-17/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
@targetNamespace must not equal http://www.w3.org/2001/XMLSchema.
|
| SD-17/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
@targetNamespace must be one of the declared namespaces.
|
|
Auto |
Pass |
| SD-18 |
Common Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/Common
as the target namespace.
| SD-18/Common/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-18/Common/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the Common subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Common |
| SD-18/Common/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
For XSD found in the Common subdirectory, @targetNamespace
(urn:us:gov:doc:uspto:common) must equal http://www.wipo.int/standards/XMLSchema/ST96/Common |
|
Auto |
Pass |
| SD-19 |
Patent Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/Patent
as the target namespace.
| SD-19/Patent/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-19/Patent/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the Patent subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Patent |
| SD-19/Patent/Document/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-19/Patent/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
For XSD found in the Patent subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Patent |
|
Auto |
Pass |
| SD-20 |
Trademark Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/Trademark
as the target namespace.
| SD-20/Trademark/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-20/Trademark/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the Trademark subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Trademark |
| SD-20/Trademark/Document/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-20/Trademark/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
For XSD found in the Trademark subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Trademark |
|
Auto |
Pass |
| SD-21 |
Design Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/Design
as the target namespace.
| SD-21/Design/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-21/Design/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the Design subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Design |
| SD-21/Design/Document/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-21/Design/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
For XSD found in the Design subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Design |
|
Auto |
Pass |
| SD-22 |
Schemas SHOULD NOT use default namespace.
| SD-22/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-22/2.xsd |
Successfully validated: No error for schema: 2.xsd. |
| SD-22/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
xsd:schema uses default namespace http://www.wipo.int/standards/XMLSchema/ST96/Patent.
|
|
Auto |
Pass |
| SD-23 |
New minor versions of Schemas MUST be able to validate all instance documents created
with previous minor versions of that Schema with the same major version. |
Manual |
None |
| SD-24 |
The Schema major version MUST be incremented if the new schema is not able to validate
existing XML instance documents created with the current major version. |
Manual |
None |
| SD-25 |
Deleted |
|
|
| SD-26 |
Deleted |
|
|
| SD-27 |
The major and/or minor version number of a schema SHOULD be changed when an included
or imported schema is updated. |
Manual |
None |
| SD-28 |
When any schema construct is altered, all schemas in the release MUST undergo the
same version number increment.
|
Auto |
Pass |
| SD-29 |
When creating a new schema, the most recent versions of all the included or imported
schemas SHOULD be used. |
Manual |
None |
| SD-30 |
The W3C Schema version attribute MUST consist of both major version number and a minor
version number, and optional patch version number for each schema file in the following
format: “V”<major version number>”_”<minor version number>{“_”<patch version number>}.
| SD-30/bad.xsd |
Successfully validated: Identified error for schema: bad.xsd.
The version attribute is not specified.
|
| SD-30/bad2.xsd |
Successfully validated: Identified error for schema: bad2.xsd.
"1.0" does not follow the
form "V<MajorNumber>_<MinorNumber>_<OptionalPatchNumber>"
|
| SD-30/good.xsd |
Successfully validated: No error for schema: good.xsd. |
| SD-30/good2.xsd |
Successfully validated: No error for schema: good2.xsd. |
| SD-30/OrphanWorkAlternativeTitleBag.xsd |
Successfully validated: Identified error for schema: OrphanWorkAlternativeTitleBag.xsd.
"V4_01" does not follow the
form "V<MajorNumber>_<MinorNumber>_<OptionalPatchNumber>"
|
| SD-30/OrphanWorkTitleBagType.xsd |
Successfully validated: Identified error for schema: OrphanWorkTitleBagType.xsd.
"V4_01" does not follow the
form "V<MajorNumber>_<MinorNumber>_<OptionalPatchNumber>"
|
|
Auto |
Pass |
| SD-31 |
The schema for a Document component MUST declare a required attribute named st96Version
on the root element with a fixed value that matches the ST.96 XML Schema release version
in the following format: “V”<major version number>“_”<minor version number>“_”<patch
version number>.
| SD-31/Document/1.xsd |
Successfully validated: Identified error for schema: 1.xsd.
Document components must require root elements to have a st96Version attribute value
of the form V<major version number>_<minor version number>{_<patch version number>}.
|
| SD-31/Document/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
Document components must require root elements to have a st96Version attribute value
of the form V<major version number>_<minor version number>{_<patch version number>}.
|
| SD-31/Document/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
Document components must require root elements to have a st96Version attribute value
of the form V<major version number>_<minor version number>{_<patch version number>}.
|
| SD-31/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
Document components must require root elements to have a st96Version attribute value
of the form V<major version number>_<minor version number>{_<patch version number>}.
|
|
Auto |
Pass |
| SD-32 |
ST.96 Schemas SHOULD be developed with the same level of cardinality and granularity
to facilitate the transformability of ST.96 instances with instances of ST.36, ST.66
or ST.86. |
Manual |
None |
| SD-33 |
Enumerations contained in Schemas SHOULD NOT include the values “Other” or “Unknown”
unless they are needed.
| SD-33/1.xsd |
Successfully validated: Identified error for component: "Enum2". The Enum2 enumeration
should not include "Other" value unless needed. |
| SD-33/1.xsd |
Successfully validated: Identified error for component: "Enum4". The Enum4 enumeration
should not include "Unknown" value unless needed. |
| SD-33/2.xsd |
Successfully validated: No error for component: "Enum1". |
|
Auto |
Pass |
| SD-34 |
MathML, version 2.0 (Second Edition), SHOULD be used for mathematical formulas.
| SD-34/1.xsd |
Successfully validated: Identified error for schema: 1.xsd.
Element MathEquation: mathml:math should be used for math data. Uses namespace http://www.w3.org/1998/Math/MathML3
and not http://www.w3.org/1998/Math/MathML.
| ComplexType MathType: mathml:math should be used for math data. Uses namespace
http://www.w3.org/1998/Math/MathML3 and not http://www.w3.org/1998/Math/MathML. |
| SD-34/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
Element MathStuff: mathml:math should be used for math data. Uses namespace and not
http://www.w3.org/1998/Math/MathML.
|
| SD-34/4.xsd |
Successfully validated: No error for schema: 4.xsd. |
| SD-34/5.xsd |
Successfully validated: Identified error for schema: 5.xsd.
Element MathJunk: mathml:math should be used for math data. Uses namespace and not
http://www.w3.org/1998/Math/MathML.
|
| SD-34/6.xsd |
Successfully validated: Identified error for schema: 6.xsd.
Element AlgebraThing: mathml:math should be used for math data. Uses namespace http://www.w3.org/1998/Math/MathML
and not http://www.w3.org/1998/Math/MathML.
| ComplexType MathType: mathml:math should be used for math data. Uses namespace
and not http://www.w3.org/1998/Math/MathML. |
| SD-34/7.xsd |
Successfully validated: No error for schema: 7.xsd. |
| SD-34/8.xsd |
Successfully validated: No error for schema: 8.xsd. |
|
Auto |
Pass |
| SD-35 |
OASISTable.xsd, based on the OASIS Exchange Table schema, SHOULD be used for tables.
| SD-35/1.xsd |
Successfully validated: No error for component: "TableType". |
| SD-35/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
Element TableStuff must use tbl:OASISTableType for table data.
|
| SD-35/4.xsd |
Successfully validated: No error for component: "SpecialTable". |
| SD-35/4.xsd |
Successfully validated: No error for component: "MyNewTableType". |
| SD-35/5.xsd |
Successfully validated: Identified error for component: "TableJunk".
Element TableJunk must use tbl:OASISTableType for table data.
|
|
Auto |
Pass |
| SD-36 |
Industry-standard schemas SHOULD be incorporated by reference only and after prior
approval by the Committee on WIPO Standards.
| SD-36/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-36/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
Import of namespace foo does not appear to designate MathML, OASIS Table, or a WIPO
or IPO namespace.
|
|
Auto |
Pass |
| SD-37 |
Schemas SHOULD use simple types to the maximum extent possible. |
Manual |
None |
| SD-38 |
Code lists SHOULD be declared as an enumeration list in a simple type.
| SD-38/ApplicationLanguageCode.xsd |
Successfully validated: No error for component: "ApplicationLanguageCode". |
| SD-38/DASAccessCode.xsd |
Successfully validated: Identified error for component: "DASAccessCode".
Code list DASAccessCode is not declared as an enumeration list in a simpleType. It
is declared as xsd:simpleType xsd:restriction xsd:pattern.
|
| SD-38/DASAccessCodeType.xsd |
Successfully validated: Identified error for component: "DASAccessCodeType".
Code list DASAccessCodeType is not declared as an enumeration list in a simpleType.
It is declared as xsd:simpleType xsd:restriction xsd:pattern.
|
| SD-38/ExtendedISOLanguageCodeType.xsd |
Successfully validated: No error for component: "ExtendedISOLanguageCodeType". |
| SD-38/ISOFormerLanguageCodeType.xsd |
Successfully validated: No error for component: "ISOFormerLanguageCodeType". |
| SD-38/Trademark/NationalEventCodeType.xsd |
Successfully validated: Identified error for component: "NationalEventCodeType".
Code list NationalEventCodeType is not declared as an enumeration list in a simpleType.
It is declared as xsd:simpleType xsd:restriction.
|
|
Partial |
Pass |
| SD-39 |
A code list MAY be declared as a union of simple types. |
Manual |
None |
| SD-40 |
WIPO Standard ST.3 two-letter codes MUST be used for representing IPOs and for priority
and designated country/organization. For example, PriorityCountryCode="EP".
| SD-40/1.xsd |
Successfully validated: No error for component: "x". |
| SD-40/3.xsd |
Successfully validated: Identified error for component: "MyOfficeCode". Element MyOfficeCode
must use com:WIPOST3CodeType or WIPO Standard ST.3 two-letter codes for IP office
codes.
|
| SD-40/4.xsd |
Successfully validated: No error for component: "DestinationOfficeCode". |
| SD-40/5.xsd |
Successfully validated: Identified error for component: "OfficeCodeJunk". Element
OfficeCodeJunk must use com:WIPOST3CodeType or WIPO Standard ST.3 two-letter codes
for IP office codes.
|
| SD-40/RegionalOfficeCode.xsd |
Successfully validated: No error for component: "RegionalOfficeCode". |
|
Partial |
Pass |
| SD-41 |
ISO 3166-1-Alpha-2 Code Elements (2 letter country codes) MUST be used for the representation
of the names of countries, dependencies, and other areas of particular geopolitical
interest, on the basis of lists of country names obtained from the United Nations.
| SD-41/1.xsd |
Successfully validated: No error for component: "x". |
| SD-41/3.xsd |
Successfully validated: Identified error for component: "MyCountry". Element must
use com:ISOCountryCodeType for country data and WIPO Standard ST.3 for IPO or designated
country/organizations. MyCountry uses .
|
| SD-41/4.xsd |
Successfully validated: No error for component: "DestinationCountry". |
| SD-41/5.xsd |
Successfully validated: Identified error for component: "CountryJunk". Element must
use com:ISOCountryCodeType for country data and WIPO Standard ST.3 for IPO or designated
country/organizations. CountryJunk uses .
|
|
Partial |
Pass |
| SD-42 |
ISO 639-1 (2-Letter Language Codes) MUST be used for Language Codes.
| SD-42/1.xsd |
Successfully validated: No error for component: "x". |
| SD-42/3.xsd |
Successfully validated: Identified error for component: "MyLanguage". Element MyLanguage
must use com:ISOLanguageCodeType or com:ExtendedISOLanguageCodeType for language codes.
|
| SD-42/4.xsd |
Successfully validated: No error for component: "DestinationLanguage". |
| SD-42/5.xsd |
Successfully validated: Identified error for component: "LanguageJunk". Element LanguageJunk
must use com:ISOLanguageCodeType or com:ExtendedISOLanguageCodeType for language codes.
|
| SD-42/originalLanguageCode.xsd |
Successfully validated: No error for component: "originalLanguageCode". |
|
Auto |
Pass |
| SD-43 |
Schemas MUST declare elements and attributes for date and time values using W3C schema
date and time data types.
| SD-43/1.xsd |
Successfully validated: No error for component: "DateOfBirth". |
| SD-43/2.xsd |
Successfully validated: No error for component: "TimeOfBirth". |
| SD-43/3.xsd |
Successfully validated: No error for component: "x". |
| SD-43/4.xsd |
Successfully validated: No error for component: "DateOfBirthB". |
| SD-43/5.xsd |
Successfully validated: No error for component: "DateOfBirthD". |
| SD-43/6.xsd |
Successfully validated: No error for component: "DateOfBirthE". |
| SD-43/7.xsd |
Successfully validated: No error for component: "DocumentLoadedDateTime". |
| SD-43/8.xsd |
Successfully validated: Identified error for component: "DateOfBirth_BAD". Element
DateOfBirth_BAD must use xsd:date for date data.
|
| SD-43/8.xsd |
Successfully validated: Identified error for component: "TimeOfBirth_BAD". Element
TimeOfBirth_BAD must use xsd:time for time data.
|
| SD-43/8.xsd |
Successfully validated: Identified error for component: "DateOfBirthA_BAD". Element
DateOfBirthA_BAD must use xsd:date for date data.
|
| SD-43/8.xsd |
Successfully validated: Identified error for component: "x_BAD". Element x_BAD must
use xsd:date for date data.
|
| SD-43/8.xsd |
Successfully validated: Identified error for component: "DateOfBirthD_BAD". Element
DateOfBirthD_BAD must use xsd:date for date data.
|
| SD-43/8.xsd |
Successfully validated: Identified error for component: "DateOfBirthE_BAD". Element
DateOfBirthE_BAD must use xsd:date for date data.
|
| SD-43/Common/creationDate.xsd |
Successfully validated: No error for component: "creationDate". |
| SD-43/LegalEffectStartTimeCategory.xsd |
Successfully validated: No error for component: "LegalEffectStartTimeCategory". |
| SD-43/otherDateCategory.xsd |
Successfully validated: No error for component: "otherDateCategory". |
|
Auto |
Pass |
| SD-44 |
ISO 4217-Alpha (3-Letter Currency Codes) MUST be used for Currency Codes.
| SD-44/1.xsd |
Successfully validated: No error for component: "x". |
| SD-44/3.xsd |
Successfully validated: Identified error for component: "MyCurrency". Element MyCurrency
must use com:ISOCurrencyCodeType for currency codes.
|
| SD-44/4.xsd |
Successfully validated: No error for component: "DestinationCurrency". |
| SD-44/5.xsd |
Successfully validated: Identified error for component: "CurrencyJunk". Element CurrencyJunk
must use com:ISOCurrencyCodeType for currency codes.
|
| SD-44/currencyCode.xsd |
Successfully validated: No error for component: "currencyCode". |
|
Auto |
Pass |
| SD-45 |
The characters used in enumerations MUST be restricted to the following set: ‘a-z,
A-Z, 0-9, space “ “ and underscore “_”’.
| SD-45/1.xsd |
Successfully validated: Identified error for component: "e1". The enumeration value
"BAD.enumeration" has invalid characters: ..| The enumeration value "BAD-enumeration"
has invalid characters: -.| The enumeration value "BADΔenumeration" has invalid characters:
Δ. |
| SD-45/2.xsd |
Successfully validated: No error for component: "e2". |
|
Auto |
Pass |
| SD-46 |
Enumeration values SHOULD be semantically sufficient, in English, and use as few characters
as possible. The values SHOULD be drawn from common intellectual property business
language. |
Manual |
None |
| SD-47 |
Abstract complex types MAY be used. |
Manual |
None |
| SD-48 |
Schemas SHOULD only use attributes to define non-business data. For example, it is
permissible to use an attribute named sequenceNumber for sequence numbers. |
Manual |
None |
| SD-49 |
An occurrence indicator SHOULD NOT be used to specify a restriction that is the default
within a schema. For example, minOccurs="1" and maxOccurs="1" SHOULD NOT be used
but minOccurs="2" and maxOccurs="3" are acceptable.
| SD-49/1.xsd |
Successfully validated: No error for component: "e". |
| SD-49/11.xsd |
Successfully validated: No error for component: "ct7". |
| SD-49/12.xsd |
Successfully validated: Identified error for component: "ct8".
@minOccurs is set to the default value (1) for xs:all.
|
| SD-49/13.xsd |
Successfully validated: Identified error for component: "ct9".
@maxOccurs is set to the default value (1) for xs:all.
|
| SD-49/14.xsd |
Successfully validated: No error for component: "ct10". |
| SD-49/15.xsd |
Successfully validated: Identified error for component: "ct11".
@minOccurs is set to the default value (1) for xs:choice.
|
| SD-49/16.xsd |
Successfully validated: Identified error for component: "ct12".
@maxOccurs is set to the default value (1) for xs:choice.
|
| SD-49/17.xsd |
Successfully validated: No error for component: "g1". |
| SD-49/18.xsd |
Successfully validated: No error for component: "ct13". |
| SD-49/19.xsd |
Successfully validated: Identified error for component: "ct14".
@minOccurs is set to the default value (1) for xs:group.
|
| SD-49/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
@minOccurs is set to the default value (1) for xs:element (e3).
|
| SD-49/20.xsd |
Successfully validated: Identified error for component: "ct15".
@maxOccurs is set to the default value (1) for xs:group.
|
| SD-49/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
@maxOccurs is set to the default value (1) for xs:element (e3).
|
| SD-49/4.xsd |
Successfully validated: No error for component: "ct1". |
| SD-49/5.xsd |
Successfully validated: Identified error for component: "ct2".
@minOccurs is set to the default value (1) for xs:sequence.
|
| SD-49/6.xsd |
Successfully validated: Identified error for component: "ct3".
@maxOccurs is set to the default value (1) for xs:sequence.
|
| SD-49/7.xsd |
Successfully validated: No error for component: "ct4". |
| SD-49/8.xsd |
Successfully validated: Identified error for component: "ct5".
@minOccurs is set to the default value (1) for xs:any.
|
| SD-49/9.xsd |
Successfully validated: Identified error for component: "ct6".
@maxOccurs is set to the default value (1) for xs:any.
|
|
Auto |
Pass |
| SD-50 |
Empty elements MUST NOT be defined in schemas except for line break.
| SD-50/1.xsd |
Successfully validated: No error for component: "Br". |
| SD-50/2.xsd |
Successfully validated: No error for component: "e". |
| SD-50/3.xsd |
Successfully validated: Identified error for component: "f".
The f element is empty.
|
| SD-50/4.xsd |
Successfully validated: Identified error for component: "g".
The g element is empty.
|
| SD-50/5.xsd |
Successfully validated: Identified error for component: "h".
The h element is empty.
|
| SD-50/MarkRecordType.xsd |
Successfully validated: Identified error for component: "MarkRecordType".
The complexType MarkRecordType has no mandatory components.
|
| SD-50/OppositionEventType.xsd |
Successfully validated: Identified error for component: "OppositionEventType".
The complexType OppositionEventType has no mandatory components.
|
|
Auto |
Pass |
| SD-51 |
The use attribute in an attribute usage SHOULD be omitted when the referenced attribute
is optional since use="optional" is the default.
| SD-51/1.xsd |
Successfully validated: No error for component: "a1". |
| SD-51/1.xsd |
Successfully validated: Identified error for component: "a2". Attribute a2
has a
use of "optional", the default value. |
| SD-51/1.xsd |
Successfully validated: No error for component: "a3". |
|
Auto |
Pass |
| SD-52 |
Schemas SHOULD NOT use the all compositor.
| SD-52/1.xsd |
Successfully validated: Identified error for component: "ct". "ct" uses
xsd:all. |
| SD-52/2.xsd |
Successfully validated: Identified error for component: "e". "e" uses
xsd:all. |
|
Auto |
Pass |
| SD-53 |
Schemas MAY use occurrence indicators in xsd:sequence and xsd:choice compositors. |
Manual |
None |
| SD-54 |
A Schema MUST NOT contain a complex type with xsd:any for extensibility.
| SD-54/1.xsd |
Successfully validated: Identified error for component: "ct". "ct" uses xsd:any. |
| SD-54/2.xsd |
Successfully validated: Identified error for component: "e". "e" uses xsd:any. |
|
Auto |
Pass |
| SD-55 |
Schemas MUST NOT use substitution groups.
| SD-55/1.xsd |
Successfully validated: Identified error for component: "woodWidget". Element
woodWidget uses
substitution groups. |
| SD-55/1.xsd |
Successfully validated: Identified error for component: "plasticWidget".
Element plasticWidget uses
substitution groups. |
|
Auto |
Pass |
| SD-56 |
Schemas SHOULD use xsd:key/xsd:keyref/xsd:unique and/or xsd:ID/xsd:IDREF/xsd:IDREFS
to identify constraints as appropriate. |
Manual |
None |
| SD-57 |
Schemas SHOULD use xsd:ID/xsd:IDREF/xsd:IDREFS for a single reference or multiple
references within the current XML document to identify constraints as appropriate. |
Manual |
None |
| SD-58 |
All schemas for elements and attributes MUST include schema construct documentation
using the xsd:documentation element. Schemas for type definitions MAY include schema
construct documentation as needed. Documentation SHOULD NOT contain implementation
details or other information not directly related to the meaning of the construct.
| SD-58/1.xsd |
Successfully validated: No error for component: "e1". |
| SD-58/2.xsd |
Successfully validated: No error for component: "a1". |
| SD-58/3.xsd |
Successfully validated: Identified error for component: "e2".
The e2 element
is missing xsd:documentation.
|
| SD-58/4.xsd |
Successfully validated: Identified error for component: "a2".
The a2 attribute
is missing xsd:documentation.
|
|
Partial |
Pass |
| SD-59 |
Comments (i.e., <!--comment -->) SHOULD NOT be used in schema.
| SD-59/1.xsd |
Successfully validated: Identified error for schema: 1.xsd.
Outside of the root element, there are XML comments containing
the following text: Comment outside root element. |
Element (xs:schema) has XML comments
containing the following text: SD-59 |
Element (xs:element) has XML comments
containing the following text: another comment |
|
Auto |
Pass |
| SD-60 |
Documentation SHOULD NOT be substituted for code lists using enumeration.
| SD-60/ocrConfidenceCode.xsd |
Successfully validated: Identified error for component: "ocrConfidenceCode".
Code list ocrConfidenceCode is not declared as an enumeration list in a simpleType,
and documentation states "Optical Character Recognition Confidence Code in the form
of numerical values in the range of 1 to 9 for each character".
|
|
Partial |
Pass |
| SD-61 |
Document level schemas MUST include schema header documentation containing references
to the created date, last modified date and contact point as mandatory and optionally
a URL where the release notes of the schema are published.
| SD-61/Document/bad.xsd |
Successfully validated: Identified error for schema: bad.xsd.
The xsd:schema does not contain an xsd:annotation/xsd:documentation element.
|
| SD-61/Document/bad2.xsd |
Successfully validated: Identified error for schema: bad2.xsd.
The xsd:annotation/xsd:appinfo element does not contain the required "com:SchemaCreatedDate"
element.
|
The xsd:annotation/xsd:appinfo element does not contain the required "com:SchemaContactPoint"
element.
|
| SD-61/Document/bad3.xsd |
Successfully validated: Identified error for schema: bad3.xsd.
The xsd:annotation/xsd:appinfo element does not contain the optional "com:SchemaReleaseNoteURL"
element.
|
| SD-61/Document/good.xsd |
Successfully validated: No error for schema: good.xsd. |
| SD-61/Document/good2.xsd |
Successfully validated: No error for schema: good2.xsd. |
| SD-61/gooda.xsd |
Successfully validated: No error for schema: gooda.xsd. |
|
Auto |
Pass |
| SD-62 |
Schemas SHOULD use xsd:key/xsd:unique/xsd:keyref within a scope where uniqueness has
to stay entirely within that scope. |
Manual |
None |
| SD-63 |
The schema for a Document component MUST declare an optional ipoVersion attribute
on the root element with a fixed value that matches the IPO’s implementation release
version in the following format: <ST.3 Code>“_” “V”<major version number>“_”<minor
version number>“_”<patch version number>, for example, US_V2_0, KR_V4_0_1.
| SD-63/Document/3.xsd |
Successfully validated: Identified error for schema: 3.xsd.
Root element does not declare optional ipoVersion attribute
with a fixed value of the form <ST3CODE>_V<major version>_<minor version>{_<patch
version>}.
|
@ipoVersion=US_V1.0 is fixed but does not have the format <ST.3 Code>_V<major version
number>_<minor version number>_<optional patch number>.
|
| SD-63/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
Root element does not declare the ipoVersion attribute
|
Root element does not declare the ipoVersion attribute as optional
|
| SD-63/Document/5.xsd |
Successfully validated: No error for schema: 5.xsd. |
| SD-63/Document/6.xsd |
Successfully validated: Identified error for schema: 6.xsd.
Root element does not declare optional ipoVersion attribute
with a fixed value of the form <ST3CODE>_V<major version>_<minor version>{_<patch
version>}.
|
@ipoVersion=V1_0 is fixed but does not start with a valid ST.3 code.
|
@ipoVersion=V1_0 is fixed but does not have the format <ST.3 Code>_V<major version
number>_<minor version number>_<optional patch number>.
|
| SD-63/Document/7.xsd |
Successfully validated: Identified error for schema: 7.xsd.
@ipoVersion=ZZ_V1_0 is fixed but does not start with a valid ST.3 code.
|
|
Auto |
Pass |
| SD-64 |
Schema release folder, a document level schema filename and a flattened schema filename
MUST contain matching version information comprising the major and minor version number,
and optional patch version number.
| SD-64/bad_release_dir/goodB.xsd |
Successfully validated: No error for schema: goodB.xsd. |
| SD-64/bad_release_dir/SchemaV2-0/Patent/Document/badA_V2_0.xsd |
Successfully validated: Identified error for schema: badA_V2_0.xsd.
No schema release folder was found with the required version information V<MajorVersionNumber>_<MinorVersionNumber>{_<OptionalPatchNumber>}
for Document XSD named badA_V2_0.xsd. In the ST.96 schema release folder structure,
the release version number is followed by component types. For example, the version
3.0 of Contact component is placed in the folder, ST96/V3_0/Common.
|
| SD-64/goodA.xsd |
Successfully validated: No error for schema: goodA.xsd. |
| SD-64/ST96/bad_version_dir/good.xsd |
Successfully validated: No error for schema: good.xsd. |
| SD-64/ST96/bad_version_dir/Patent/Document/bad_V2_0.xsd |
Successfully validated: Identified error for schema: bad_V2_0.xsd.
No schema release folder was found with the required version information V<MajorVersionNumber>_<MinorVersionNumber>{_<OptionalPatchNumber>}
for Document XSD named bad_V2_0.xsd. In the ST.96 schema release folder structure,
the release version number is followed by component types. For example, the version
3.0 of Contact component is placed in the folder, ST96/V3_0/Common.
|
| SD-64/ST96/V2_0/FlattenedDocumentSchema/badD.xsd |
Successfully validated: Identified error for schema: badD.xsd.
The flattened schema file name badD.xsd does not contain version information in the
required format <ComponentName>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| SD-64/ST96/V2_0/FlattenedDocumentSchema/goodD_V2_0.xsd |
Successfully validated: No error for schema: goodD_V2_0.xsd. |
| SD-64/ST96/V2_0/Patent/Document/badC.xsd |
Successfully validated: Identified error for schema: badC.xsd.
The Document schema file name badC.xsd does not contain version information in the
required format <ComponentName>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| SD-64/ST96/V2_0/Patent/Document/badC_V1_0.xsd |
Successfully validated: Identified error for schema: badC_V1_0.xsd.
The Document schema file name badC_V1_0.xsd has a major version number (1) that does
not match the release major version number (2).
|
| SD-64/ST96/V2_0/Patent/Document/badC_V2.0.xsd |
Successfully validated: Identified error for schema: badC_V2.0.xsd.
The Document schema file name badC_V2.0.xsd does not contain version information in
the required format <ComponentName>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| SD-64/ST96/V2_0/Patent/Document/badC_v2_0.xsd |
Successfully validated: Identified error for schema: badC_v2_0.xsd.
The Document schema file name badC_v2_0.xsd does not contain version information in
the required format <ComponentName>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| SD-64/ST96/V2_0/Patent/Document/badC_V2_0_0.xsd |
Successfully validated: Identified error for schema: badC_V2_0_0.xsd.
The Document schema file name badC_V2_0_0.xsd does not contain version information
in the required format <ComponentName>{_V<MajorVersionNumber>_<MinorVersionNumber>_<OptionalPatchVersionNumber>}.<FileExtension>
|
| SD-64/ST96/V2_0/Patent/Document/badC_V2_1.xsd |
Successfully validated: Identified error for schema: badC_V2_1.xsd.
The Document schema file name badC_V2_1.xsd has a minor version number (1) that does
not match the release minor version number (0).
|
| SD-64/ST96/V2_0/Patent/Document/goodC_V2_0.xsd |
Successfully validated: No error for schema: goodC_V2_0.xsd. |
|
Auto |
Pass |
| SD-65 |
Geographical Indication Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/GeographicalIndication
as the target namespace.
| SD-65/GeographicalIndication/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-65/GeographicalIndication/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the GeographicalIndication subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/GeographicalIndication |
| SD-65/GeographicalIndication/Document/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-65/GeographicalIndication/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
For XSD found in the GeographicalIndication subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/GeographicalIndication |
|
Auto |
Pass |
| SD-66 |
Copyright Component Schemas MUST use http://www.wipo.int/standards/XMLSchema/ST96/Copyright
as the target namespace.
| SD-66/Copyright/1.xsd |
Successfully validated: No error for schema: 1.xsd. |
| SD-66/Copyright/2.xsd |
Successfully validated: Identified error for schema: 2.xsd.
For XSD found in the Copyright subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Copyright |
| SD-66/Copyright/Document/3.xsd |
Successfully validated: No error for schema: 3.xsd. |
| SD-66/Copyright/Document/4.xsd |
Successfully validated: Identified error for schema: 4.xsd.
For XSD found in the Copyright subdirectory, @targetNamespace
(http://www.wipo.int/standards/XMLSchema/ST96/BAD) must equal http://www.wipo.int/standards/XMLSchema/ST96/Copyright |
|
Auto |
Pass |
| SD-67 |
A patched version MAY not be able to validate all instance documents created with
previous minor versions. |
Manual |
None |