xPDK_Header
Most is optional and extension capability is the idea.
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.
<xPDK_Header pdk_name="..." ... > ...
<MRL> ... </MRL> optional
<TRL> ... </TRL> optional
<attribute> ... </attribute> list
<doc> ... </doc> list
<global> ... </global> list
<groupRef> ... </groupRef> list
<license> ... </license> optional
<mpw_run> ... </mpw_run> list optional
<provider> ... </provider> optional
<tex> ... </tex> list
<version> ... </version> list
</xPDK_Header>
XSD The schema file can be downloaded or viewed at xPDK_Base.
Details
MRL
Type pdaMRL documentation: Manufacturing Readiness Level (MRL) as defined by the EU.TRL
Type pdaTRL documentation: Technology Readiness Level (TRL) as defined by the EU.attribute
Type pdaAttributeType documentation: and views with information that is likely to be software specific. So it is more a 'flag' then a value. The value is just a string and not something with an expression in it.doc
Type pdaDocumentation documentation:This field allows some (short, few lines) documentation to be written. It can be a long string, but the idea is not to replace a design manual.
This fields is like
tex
which allows documentation in LaTex format; doc
is restricted to plain text.global
Type pdaNamedValue documentation:groupRef
Type pdaIdentifier documentation:Identifiers are used in the Python library for the
getName() and
setName() function and can thus be used to identify the different elements in list
s.In text the specification is a letter, followed by letters, numbers, underscore. The XSD schema validation is a regular expression: [A-Za-z]([A-Za-z0-9_])*
license
Type pdaLicense documentation:State the basic conditions of using the file and typically refer to legal documents.
License information should be compact enough to be clear as reference. The reference is expected to be to signed documents like Non Disclose Agreements (NDA) or service contracts and so on.
mpw_run
other data file can be applied. Type pdaMPWrun documentation: library.pdk_name
under the same provider name.The
pdk_name at the start (just
below the xsi:noNamespaceSchemaLocation defines the design kit name and is
intended as a relatively short name. It should be unique enough to avoid confusion by
designers.
Type pdaPDKname documentation:
general then the pdaIdentifier. In text this is a letter or number, followed by letters, numbers or underscore. The check is regular expression: [A-Za-z0-9]([A-Za-z0-9_])*
provider
Type pdaProvider documentation: provider, so a full company or institute name for example, instead of the smaller pdk_name.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.