pdaReleaseNotesVersion

Structure

The attributes and elements are shown below, in a sorted per type fashion.
In case a list is printed after an element, it indicates that you can have many, otherwise it should be a single element. With a optional it tells the element is not required.

XSD

The schema file can be downloaded or viewed at xPDK_Layout.

Details

doc

Type pdaDocumentation documentation:
This field allows some (short, single line) documentation to be written. It can be a long string, but the idea is not to replace a design manual.
This field is like tex which allows documentation in LaTex format; doc is restricted to plain text.

markup

Type pdaMarkupDocumentation documentation: actual html.

pdkSelect

Type pdkSelect documentation:

release

Type pdaVersion documentation:
The version can be defined as:

major.minor
this is the short-hand version number. This can be a YYYY.MM (year.month) value also.
major.minor.patch
adds the patch to indicate small changes. This can be a YYYY.MM.DD (year.month.day) value also.
major.minor.patch.iteration
where the iteration is often relating to a (software) implementation and thus less typical in PDK or BB versions.
It can be useful in the compact model files to indicate that the same measurements or simulations have received a new model instance.

A major number change indicates something big changed, while the minor is for more incremental changes. The patch indicates normally small data updates like new measurements.

tex

Type pdaTexDocumentation documentation: doc , but tex can be a long text in LaTex format to document the layer in more detail if needed.

You can document anything relevant for the topic you want to define.

Multiple paragraphs is fine. Format is Latex, so more complex content is possible.