Use a resource for the resource examples

modelica · Oct 25, 2024 · d00ef43 · d00ef43
1 parent 0c1b1fe
commit d00ef43
Show file tree

Hide file tree

Showing 5 changed files with 10 additions and 10 deletions.
diff --git a/docs/4___common_content.adoc b/docs/4___common_content.adoc
@@ -519,7 +519,7 @@ If the attribute is missing or is specified as `file`, the source is resolved ag
 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 the component (for example an FMU) through relative URIs.
+The last option allows the specification of meta data sources that reside inside a resource (for example an FMU) through relative URIs.
 |===
 
 ===== Content
@@ -577,5 +577,5 @@ In this case the URI is resolved against the (resolved) source URI of the contai
 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 the component (for example an FMU), or the meta data through relative URIs.
+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.
 |===
diff --git a/docs/5___ssd.adoc b/docs/5___ssd.adoc
@@ -436,7 +436,7 @@ If the attribute is missing or is specified as `SSD`, the source is resolved aga
 
 If the attribute is specified as `component` the URI is resolved against the (resolved) source URI of the component.
 
-The last option allows the specification of parameter sources that reside inside the component (for example an FMU) through relative URIs.
+The last option allows the specification of parameter sources that reside inside a resource (for example an FMU) through relative URIs.
 |prefix |Defines the optional prefix for name resolution and mapping purposes for this binding.
 If this attribute is empty or not supplied no prefix is used for name resolution and mapping, otherwise the specified prefix is prepended to all names in the parameter source prior to processing the normal name resolution or name mapping rules.
 This allows the user to apply a parameter set normally intended for a component (and thus containing bare parameter names) at a system level targeted to one element of the system by supplying the name of the element plus a dot as a prefix on the binding, thus causing all parameter names in the parameter set to be treated as if they were specified with proper hierarchical names.
@@ -484,7 +484,7 @@ If the attribute is missing or is specified as `SSD`, the source is resolved aga
 
 If the attribute is specified as `component` the URI is resolved against the (resolved) source URI of the component.
 
-The last option allows the specification of parameter mapping sources that reside inside the component (for example an FMU) through relative URIs.
+The last option allows the specification of parameter mapping sources that reside inside a resource (for example an FMU) through relative URIs.
 |===
 
 The contents of the element *MUST* be empty if the source attribute is present.

diff --git a/schema/SystemStructureCommon.xsd b/schema/SystemStructureCommon.xsd
@@ -330,7 +330,7 @@
                                 the containing model element.
 
                                 The last option allows the specification of meta data sources that
-                                reside inside the component (for example an FMU) through relative URIs.
+                                reside inside a resource (for example an FMU) through relative URIs.
                             </xs:documentation>
                         </xs:annotation>
                         <xs:simpleType>
@@ -413,7 +413,7 @@
                     of the meta data source.
 
                     The last two options allow the specification of signature sources that
-                    reside inside the component (for example an FMU), or the meta data
+                    reside inside a resource (for example an FMU), or the meta data
                     through relative URIs.
                 </xs:documentation>
             </xs:annotation>

diff --git a/schema/SystemStructureDescription.xsd b/schema/SystemStructureDescription.xsd
@@ -968,7 +968,7 @@
                                             URI of the containing file.  If the attribute is specified as component
                                             the URI is resolved against the (resolved) source URI of the component.
                                             The last option allows the specification of parameter sources that
-                                            reside inside the component (for example an FMU) through relative URIs.
+                                            reside inside a resource (for example an FMU) through relative URIs.
                                         </xs:documentation>
                                     </xs:annotation>
                                     <xs:simpleType>
@@ -1015,7 +1015,7 @@
                                 URI of the containing file.  If the attribute is specified as component
                                 the URI is resolved against the (resolved) source URI of the component.
                                 The last option allows the specification of parameter mapping sources
-                                that reside inside the component (for example an FMU) through relative
+                                that reside inside a resource (for example an FMU) through relative
                                 URIs.
                             </xs:documentation>
                         </xs:annotation>

diff --git a/schema/SystemStructureDescription11.xsd b/schema/SystemStructureDescription11.xsd
@@ -915,7 +915,7 @@
                                             URI of the containing file.  If the attribute is specified as component
                                             the URI is resolved against the (resolved) source URI of the component.
                                             The last option allows the specification of parameter sources that
-                                            reside inside the component (for example an FMU) through relative URIs.
+                                            reside inside a resource (for example an FMU) through relative URIs.
                                         </xs:documentation>
                                     </xs:annotation>
                                     <xs:simpleType>
@@ -962,7 +962,7 @@
                                 URI of the containing file.  If the attribute is specified as component
                                 the URI is resolved against the (resolved) source URI of the component.
                                 The last option allows the specification of parameter mapping sources
-                                that reside inside the component (for example an FMU) through relative
+                                that reside inside a resource (for example an FMU) through relative
                                 URIs.
                             </xs:documentation>
                         </xs:annotation>