Merge pull request #206 from deeglaze/baseorstandard

Clarify "standard CoRIM type"

draft-ietf-rats-corim.md

@@ -431,8 +431,9 @@ The following describes each child element of this type.
 
 Profiling is the mechanism that allows the base CoRIM schema to be customised to fit a specific Attester.
 
-A profile defines which of the optional parts of a CoRIM are required, which are prohibited, and which extension points are exercised and how.
-A profile MUST NOT alter the syntax or semantics of a standard CoRIM type.
+A profile defines which of the optional parts of a CoRIM are required, which are prohibited and which extension points are exercised and how.
+A profile MUST NOT alter the syntax or semantics of CoRIM types defined in this document.
+
 A profile MAY constrain the values of a given CoRIM type to a subset of the values.
 A profile MAY extend the set of a given CoRIM type using the defined extension points (see {{sec-extensibility}}).
 Exercised extension points should preserve the intent of the original semantics.
@@ -453,6 +454,7 @@ that MUST have a different identifier.
 {::include cddl/profile-type-choice.cddl}
 ~~~
 
+
 ### Entities {#sec-corim-entity}
 
 The CoRIM Entity is an instantiation of the Entity generic
@@ -1352,7 +1354,7 @@ CDDL map extension points have the form `($$NAME-extension)` where "NAME" is the
 and '$$' signifies map extensibility. Typically, map extension requires a convention
 for code point naming that avoids code-point reuse.
 Well-known code points may be in a registry, such as CoSWID {{-coswid-reg}}.
-Additionally, a range of code points may be reserved for vendor-specific use such as negative integers.
+Non-negative integers are reserved for IANA to assign meaning globally.
 
 ### Data Type Extensions
 
@@ -2152,7 +2154,7 @@ Environments (CoRE) Parameters" Registry {{!IANA.core-parameters}}:
 
 --- back
 
-# Full CoRIM CDDL
+# Full CoRIM CDDL {#sec-corim-cddl}
 
 ~~~ cddl
 {::include cddl/corim-autogen.cddl}