Skip to content

Commit

Permalink
Update from modelica/ssp-standard@1e04553
Browse files Browse the repository at this point in the history
  • Loading branch information
modelica committed Oct 25, 2024
1 parent 9776682 commit af50938
Show file tree
Hide file tree
Showing 6 changed files with 118 additions and 111 deletions.
Binary file modified static/docs/main/images/SystemStructureCommon_MetaData.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified static/docs/main/images/SystemStructureCommon_Signature.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
81 changes: 55 additions & 26 deletions static/docs/main/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -586,7 +586,7 @@
<div id="header">
<h1>System Structure and Parameterization</h1>
<div class="details">
<span id="revnumber">version 6cdd1f4,</span>
<span id="revnumber">version 1e04553,</span>
<span id="revdate">2024-10-25</span>
</div>
<div id="toc" class="toc2">
Expand Down Expand Up @@ -2541,10 +2541,7 @@ <h5 id="_metadata">4.5.4.1. MetaData</h5>
<td class="tableblock halign-left valign-top"><p class="tableblock">source</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Optional attribute indicating the source of the meta data as a URI (cf. RFC 3986).
For purposes of the resolution of relative URIs the base URI is the URI of the SSD, if the sourceBase attribute is not specified or is specified as <code>SSD</code>, and the URI of the containing model element (e.g. component) if the base attribute is specified as <code>component</code>.</p>
</div>
<div class="paragraph">
<p>This allows the specification of meta data sources that reside inside the component (for example an FMU) through relative URIs.</p>
The base URI for the resolution of relative URIs is determined by the sourceBase attribute.</p>
</div>
<div class="paragraph">
<p>If the source attribute is missing, the meta data <strong>MUST</strong> be provided inline as contents of a Content element, which <strong>MUST NOT</strong> be present otherwise.</p>
Expand All @@ -2553,8 +2550,17 @@ <h5 id="_metadata">4.5.4.1. MetaData</h5>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">sourceBase</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Defines the base the source URI is resolved against:
If the attribute is missing or is specified as <code>SSD</code>, the source is resolved against the URI of the SSD, if the attribute is specified as <code>component</code> the URI is resolved against the (resolved) URI of the model element (e.g. component) source.</p>
<p>Defines the base the source URI is resolved against:</p>
</div>
<div class="paragraph">
<p>If the attribute is missing or is specified as <code>file</code>, the source is resolved against the URI of the containing file.</p>
</div>
<div class="paragraph">
<p>If the containing model element has a source attribute, the sourceBase attribute can be specified as <code>resource</code>.
In this case the URI is resolved against the (resolved) source URI of the containing model element.</p>
</div>
<div class="paragraph">
<p>The last option allows the specification of meta data sources that reside inside a resource (for example an FMU) through relative URIs.</p>
</div></div></td>
</tr>
</tbody>
Expand Down Expand Up @@ -2640,10 +2646,7 @@ <h5 id="_signature">4.5.4.3. Signature</h5>
<td class="tableblock halign-left valign-top"><p class="tableblock">source</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Optional attribute indicating the source of the signature as a URI (cf. RFC 3986).
For purposes of the resolution of relative URIs the base URI is the URI of the SSD, if the sourceBase attribute is not specified or is specified as <code>SSD</code>, the URI of the containing model element (e.g. component) if the base attribute is specified as <code>component</code>, or the URI of the meta data source if the sourceBase attribute is specified as <code>metaData</code>.</p>
</div>
<div class="paragraph">
<p>This allows the specification of signature sources that reside inside the component (for example an FMU), or the meta data through relative URIs.</p>
The base URI for the resolution of relative URIs is determined by the sourceBase attribute.</p>
</div>
<div class="paragraph">
<p>If the source attribute is missing, the signature <strong>MUST</strong> be provided inline as contents of a Content element, which <strong>MUST NOT</strong> be present otherwise.</p>
Expand All @@ -2652,9 +2655,21 @@ <h5 id="_signature">4.5.4.3. Signature</h5>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">sourceBase</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Defines the base the source URI is resolved against:
If the attribute is missing or is specified as <code>SSD</code>, the source is resolved against the URI of the SSD, if the attribute is specified as <code>component</code> the URI is resolved against the (resolved) URI of the model element (e.g. component) source, or if the attribute is specified as <code>metaData</code> the URI is resolved against the (resolved) URI of the meta data source.
The value <code>metaData</code> is only valid if the Signature element is contained within a MetaData element.</p>
<p>Defines the base the source URI is resolved against:</p>
</div>
<div class="paragraph">
<p>If the attribute is missing or is specified as <code>file</code>, the source is resolved against the URI of the containing file.</p>
</div>
<div class="paragraph">
<p>If the containing model element has a source attribute, the sourceBase attribute can be specified as <code>resource</code>.
In this case the URI is resolved against the (resolved) source URI of the containing model element.</p>
</div>
<div class="paragraph">
<p>If the Signature element is contained within a MetaData element, the sourceBase attribute can be specified as <code>metaData</code>.
In this case the URI is resolved against the (resolved) URI of the meta data source.</p>
</div>
<div class="paragraph">
<p>The last two options allow the specification of signature sources that reside inside a resource (for example an FMU), or the meta data through relative URIs.</p>
</div></div></td>
</tr>
</tbody>
Expand Down Expand Up @@ -3460,19 +3475,26 @@ <h4 id="_parameterbindings">5.2.3. ParameterBindings</h4>
<td class="tableblock halign-left valign-top"><p class="tableblock">source</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Optional attribute indicating the source of the parameters as a URI (cf. RFC 3986).
For purposes of the resolution of relative URIs the base URI is the URI of the SSD, if the sourceBase attribute is not specified or is specified as SSD, and the URI of the referenced component if the base attribute is specified as component.</p>
</div>
<div class="paragraph">
<p>This allows the specification of parameter sources that reside inside the component (for example an FMU) through relative URIs.</p>
The base URI for the resolution of relative URIs is determined by the sourceBase attribute.</p>
</div>
<div class="paragraph">
<p>If the source attribute is missing, the parameter set <strong>MUST</strong> be provided inline as contents of a ParameterValues element, which <strong>MUST NOT</strong> be present otherwise.</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">sourceBase</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Defines the base the source URI is resolved against:
If the attribute is missing or is specified as SSD, the source is resolved against the URI of the SSD, if the attribute is specified as component the URI is resolved against the (resolved) URI of the component source.</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Defines the base the source URI is resolved against:</p>
</div>
<div class="paragraph">
<p>If the attribute is missing or is specified as <code>SSD</code>, the source is resolved against the URI of the containing file.</p>
</div>
<div class="paragraph">
<p>If the attribute is specified as <code>component</code> the URI is resolved against the (resolved) source URI of the component.</p>
</div>
<div class="paragraph">
<p>The last option allows the specification of parameter sources that reside inside a resource (for example an FMU) through relative URIs.</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">prefix</p></td>
Expand Down Expand Up @@ -3549,19 +3571,26 @@ <h5 id="_parametermapping">5.2.3.2. ParameterMapping</h5>
<td class="tableblock halign-left valign-top"><p class="tableblock">source</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Optional attribute indicating the source of the parameter mapping as a URI (cf. RFC 3986).
For purposes of the resolution of relative URIs the base URI is the URI of the SSD, if the sourceBase attribute is not specified or is specified as SSD, and the URI of the referenced component if the base attribute is specified as component.</p>
</div>
<div class="paragraph">
<p>This allows the specification of parameter mapping sources that reside inside the component (for example an FMU) through relative URIs.</p>
The base URI for the resolution of relative URIs is determined by the sourceBase attribute.</p>
</div>
<div class="paragraph">
<p>If the source attribute is missing, the parameter mapping <strong>MUST</strong> be provided inline as contents of the ParameterMapping element, which <strong>MUST</strong> be empty otherwise.</p>
</div></div></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">sourceBase</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Defines the base the source URI is resolved against:
If the attribute is missing or is specified as SSD, the source is resolved against the URI of the SSD, if the attribute is specified as component the URI is resolved against the (resolved) URI of the component source.</p></td>
<td class="tableblock halign-left valign-top"><div class="content"><div class="paragraph">
<p>Defines the base the source URI is resolved against:</p>
</div>
<div class="paragraph">
<p>If the attribute is missing or is specified as <code>SSD</code>, the source is resolved against the URI of the containing file.</p>
</div>
<div class="paragraph">
<p>If the attribute is specified as <code>component</code> the URI is resolved against the (resolved) source URI of the component.</p>
</div>
<div class="paragraph">
<p>The last option allows the specification of parameter mapping sources that reside inside a resource (for example an FMU) through relative URIs.</p>
</div></div></td>
</tr>
</tbody>
</table>
Expand Down
84 changes: 37 additions & 47 deletions static/docs/main/schema/SystemStructureCommon.xsd
View file
Original file line number Diff line number Diff line change
Expand Up @@ -311,38 +311,31 @@
<xs:annotation>
<xs:documentation xml:lang="en">
This attribute indicates the source of the resource meta data as a
URI (cf. RFC 3986). For purposes of the resolution of relative URIs
the base URI is the URI of the STC, if the sourceBase attribute is
not specified or is specified as STC, and the URI of the referenced
resource if the sourceBase attribute is specified as resource.

This allows the specification of meta data sources that reside
inside the resource (e.g. an FMU) through relative URIs.

For meta data that are located alongside the STC, relative URIs
without scheme and authority can and should be used to specify the
meta data sources. For meta data that are packaged inside an SSP
that contains this STC, this is mandatory (in this way, the STC
URIs remain valid after unpacking the SSP into the filesystem).

If the source attribute is missing, the meta data is provided
inline as contents of the Content element, which must not be
present otherwise.
URI (cf. RFC 3986). The base URI for the resolution of relative URIs
is determined by the sourceBase attribute.

If the source attribute is missing, the meta data is provided inline
as contents of a Content element, which must not be present otherwise.
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="sourceBase" use="optional" default="SSD">
<xs:attribute name="sourceBase" use="optional" default="file">
<xs:annotation>
<xs:documentation xml:lang="en">
Defines the base the source URI is resolved against: If the attribute
is missing or is specified as SSD, the source is resolved against the
URI of the SSD, if the attribute is specified as resource the URI is
resolved against the (resolved) URI of the resource source.
is missing or is specified as file, the source is resolved against the
URI of the containing file. If the containing model element has a
source attribute, the sourceBase attribute can be specified as resource.
In this case the URI is resolved against the (resolved) source URI of
the containing model element.

The last option allows the specification of meta data sources that
reside inside a resource (for example an FMU) through relative URIs.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SSD"/>
<xs:enumeration value="file"/>
<xs:enumeration value="resource"/>
</xs:restriction>
</xs:simpleType>
Expand Down Expand Up @@ -397,40 +390,37 @@
<xs:annotation>
<xs:documentation xml:lang="en">
This attribute indicates the source of the digital signature as a
URI (cf. RFC 3986). For purposes of the resolution of relative URIs
the base URI is the URI of the SSD, if the sourceBase attribute is
not specified or is specified as SSD, the URI of the containing model
element (e.g. component) if the sourceBase attribute is specified as
component, or the URI of the meta data source if the sourceBase
attribute is specified as metaData.

This allows the specification of signature sources that reside
inside the component (for example an FMU), or the meta data
through relative URIs.

If the source attribute is missing, the signature is provided
inline as contents of the Content element, which must not be
present otherwise.
URI (cf. RFC 3986). The base URI for the resolution of relative URIs
is determined by the sourceBase attribute.

If the source attribute is missing, the signature must be provided
inline as contents of a Content element, which must not be present
otherwise.
</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="sourceBase" use="optional" default="SSD">
<xs:attribute name="sourceBase" use="optional" default="file">
<xs:annotation>
<xs:documentation xml:lang="en">
Defines the base the source URI is resolved against: If the attribute
is missing or is specified as SSD, the source is resolved against the
URI of the SSD, if the attribute is specified as component the URI is
resolved against the (resolved) URI of the model element (e.g.
component) source, or if the attribute is specified as metaData the
URI is resolved against the (resolved) URI of the meta data source.
The value metaData is only valid if the Signature element is contained
within a MetaData element.
Defines the base the source URI is resolved against: If the attribute
is missing or is specified as file, the source is resolved against the
URI of the containing file. If the containing model element has a
source attribute, the sourceBase attribute can be specified as resource.
In this case the URI is resolved against the (resolved) source URI of
the containing model element. If the Signature element is contained
within a MetaData element, the sourceBase attribute can be specified as
metaData. In this case the URI is resolved against the (resolved) URI
of the meta data source.

The last two options allow the specification of signature sources that
reside inside a resource (for example an FMU), or the meta data
through relative URIs.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="SSD"/>
<xs:enumeration value="component"/>
<xs:enumeration value="file"/>
<xs:enumeration value="resource"/>
<xs:enumeration value="metaData"/>
</xs:restriction>
</xs:simpleType>
Expand Down
Loading

0 comments on commit af50938

Please sign in to comment.