Schema Differences between Version 5.4.4 and Version 6.0
Version 5.4.4 Schema File: cwe_schema_v5.4.4.xsd -> Version 6.0 Schema File: cwe_schema_v6.0.xsd
Major changes from 5.4.4 --> 6.0:
- Make the <Weakness_Catalog> the only valid root element. The previous 5.4.4 schema allows any number of elements to be valid root elements. As part of this change, make the the other children (Weaknesses, Views, Categories, and External_References) become optional. The previous <Weakness_Catalog> requires the existence all of the child element, even if they are empty. For example, the empty element <Views/> is required to produce valid XML in schema 5.4.4.
- The <Compound_Element> has been removed. The rationale for this is that named chains and composites are weaknesses themselves and should therefore be defined by <Weakness> elements. To enable the distinction of the compound elements going forward, we will add a new "structure" attribute to <Weakness> element with values of: simple, chain, composite.
- Add the <External_References> element to the weakness catalog. In the previous 5.4.4 schema, references were defined inside an individual weakness, but assigned an ID so that they could be reused if the reference was used elsewhere. It is cleaner and easier to understand if there is a central collection of references that individual weaknesses can pull from as needed. As a side benefit, there is no longer a need to have a local reference ID as the main ID can be used.
Tweak the child elements of a <View> :
||Note / Reason
|View_Structure||moved to the "Type" attribute|
|View_Audience||Audience||changed to require description|
|Relationships||Members||only allowed relationship is <Has_Member>|
|Relationship_Notes||combined with <Notes>|
|Maintenance_Notes||combined with <Notes>|
|Other_Notes||Notes||added "Type" attribute |
|Alternate_Terms||doesn't make sense for views|
|Research_Gaps||doesn't make sense for views|
Tweak the child elements of a <Category> as it currently uses the same Common_Attributes group as weaknesses do. Many of these fields are not applicable to categories. The following set of fields are children of the <Category> element in the 6.0 schema.
- Relationships (memberOf and hasMember)
- Notes (with new Type attribute)
The removed fields are:
Remove the following child elements of <Weakness> as they are only used in a limited manner and did not hold any unique information.
- Time_of_Introduction (combined with Mode_of_Introduction)
- Research_Gaps (moved to a Note)
- Within the Applicable_Platform element, move the CPE platform reference element to be an optional attribute on <Operating_System>. The reason is that CPE is only applicable for the OS field and not languages, architectures, paradigms, or environments.
- For weaknesses, tweak the names of the "Description" elements. Previously there was a <Description> element with two children; the short description was named <Description_Summary>, and the long was named <Extended_Description>. The 6.0.0 schema removes the nested elements and just had two top-level elements: <Description> and <Extended_Description>.
- Change the <Relationships> element to only be used for views and categories. Also limit the values to memberOf and hasMember since these are the only ones that are appropriate for views and categories. For weaknesses, add a new <Related_Weaknesses> element that holds all the different types of relationships that weaknesses can have with each other. The reason for this change is to eliminate the incorrect use memberOf and hasMember relationships with weaknesses, and the incorrect use of parentOf and childOf with views and categories.
- Combine all the different note elements into a single <Notes> element. Add a type attribute that allows for a distinction between: maintenance, platform, relationship, terminology, theoretical, other. This is done to simplify the schema and the resulting XML by having less elements.
- Rewrite the StructuredTextType and add a new StructuredCodeType as the previous Structured_Text_Type was cumbersome and unnecessary. It was in place for two primary reasons: First was to enable the encoding of bulleted lists and indention within text fields. Second was to provide formatting options such as new lines and shading for code examples. The first can be solved easily by leveraging the existing XHTML standard. The new StructuredTextType does this. The second is accomplished by the new StructuredCodeType which also leverages XHTML but includes a couple of existing attributes (language, nature)
More information is available — Please select a different filter.