Skip to content

Commit 5ea051e

Browse files
committed
Add signature to GMetaData for component signatures
1 parent c682588 commit 5ea051e

File tree

3 files changed

+34
-20
lines changed

3 files changed

+34
-20
lines changed

docs/4___common_content.adoc

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -464,10 +464,10 @@ This attribute references another connector by name, that gives the size of this
464464
[#ssc_metadata]
465465
==== MetaData Sequence
466466

467-
image:images/SystemStructureCommon_GMetaData.png[image,width=597,height=146]
467+
image:images/SystemStructureCommon_GMetaData.png[image,width=597,height=196]
468468

469-
The MetaData element allows the specification of additional meta data for a given resource.
470-
Multiple (or no) MetaData elements may be present in a given resource.
469+
The MetaData element allows the specification of additional meta data for a given model element.
470+
Multiple (or no) MetaData elements may be present in a given model element.
471471

472472
[width="100%",cols="33%,67%",options="header",]
473473
|===
@@ -531,7 +531,9 @@ In that case there *SHOULD* be a layered specification that defines how embeddin
531531

532532
image:images/SystemStructureCommon_Signature.png[image,width=423,height=534]
533533

534-
This element specifies digital signature information on the meta data referenced by the enclosing MetaData element.
534+
This element specifies digital signature information on the data or meta data referenced by the enclosing element:
535+
If the Signature element is contained within a MetaData element, it refers to the meta data referenced by the MetaData element.
536+
If the Signature element is contained within any other element, it refers to the content of that element.
535537

536538
The Signature element is structured by the following subordinated elements.
537539

@@ -557,12 +559,13 @@ This mandatory attribute specifies the MIME type of the signature, which does no
557559
If no specific MIME type can be indicated, then the type `application/octet-stream` is to be used.
558560
|source a|
559561
Optional attribute indicating the source of the signature as a URI (cf. RFC 3986).
560-
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 containing model element (e.g. component) if the base attribute is specified as `component`, or the URI of the meta data source if the sourceBase attribute is specified as `metaData`.
562+
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 base attribute is specified as `component`, or the URI of the meta data source if the sourceBase attribute is specified as `metaData`.
561563

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

564566
If the source attribute is missing, the signature *MUST* be provided inline as contents of a Content element, which *MUST NOT* be present otherwise.
565567
|sourceBase a|
566568
Defines the base the source URI is resolved against:
567569
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.
570+
The value `metaData` is only valid if the Signature element is contained within a MetaData element.
568571
|===
2.39 KB
Loading

schema/SystemStructureCommon.xsd

Lines changed: 26 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -350,6 +350,15 @@
350350
<xs:attributeGroup ref="ssc:ABaseElement"/>
351351
</xs:complexType>
352352
</xs:element>
353+
<xs:element name="Signature" type="ssc:SignatureType" minOccurs="0" maxOccurs="unbounded">
354+
<xs:annotation>
355+
<xs:documentation xml:lang="en">
356+
This element can contain digital signature information on the data referenced
357+
by the enclosing element. It is left unspecified what types of signatures
358+
are used and/or available for now. Multiple or no signature elements may be present.
359+
</xs:documentation>
360+
</xs:annotation>
361+
</xs:element>
353362
</xs:sequence>
354363
</xs:group>
355364

@@ -387,20 +396,17 @@
387396
<xs:attribute name="source" type="xs:anyURI" use="optional">
388397
<xs:annotation>
389398
<xs:documentation xml:lang="en">
390-
This attribute indicates the source of the resource signature as a
399+
This attribute indicates the source of the digital signature as a
391400
URI (cf. RFC 3986). For purposes of the resolution of relative URIs
392-
the base URI is the URI of the STC, if the sourceBase attribute is
393-
not specified or is specified as STC, and the URI of the referenced
394-
resource if the sourceBase attribute is specified as resource.
401+
the base URI is the URI of the SSD, if the sourceBase attribute is
402+
not specified or is specified as SSD, the URI of the containing model
403+
element (e.g. component) if the sourceBase attribute is specified as
404+
component, or the URI of the meta data source if the sourceBase
405+
attribute is specified as metaData.
395406

396407
This allows the specification of signature sources that reside
397-
inside the resource (e.g. an FMU) through relative URIs.
398-
399-
For signatures that are located alongside the STC, relative URIs
400-
without scheme and authority can and should be used to specify the
401-
signature sources. For signatures that are packaged inside an SSP
402-
that contains this STC, this is mandatory (in this way, the STC
403-
URIs remain valid after unpacking the SSP into the filesystem).
408+
inside the component (for example an FMU), or the meta data
409+
through relative URIs.
404410

405411
If the source attribute is missing, the signature is provided
406412
inline as contents of the Content element, which must not be
@@ -411,16 +417,21 @@
411417
<xs:attribute name="sourceBase" use="optional" default="SSD">
412418
<xs:annotation>
413419
<xs:documentation xml:lang="en">
414-
Defines the base the source URI is resolved against: If the attribute
420+
Defines the base the source URI is resolved against: If the attribute
415421
is missing or is specified as SSD, the source is resolved against the
416-
URI of the SSD, if the attribute is specified as resource the URI is
417-
resolved against the (resolved) URI of the resource source.
422+
URI of the SSD, if the attribute is specified as component the URI is
423+
resolved against the (resolved) URI of the model element (e.g.
424+
component) source, or if the attribute is specified as metaData the
425+
URI is resolved against the (resolved) URI of the meta data source.
426+
The value metaData is only valid if the Signature element is contained
427+
within a MetaData element.
418428
</xs:documentation>
419429
</xs:annotation>
420430
<xs:simpleType>
421431
<xs:restriction base="xs:string">
422432
<xs:enumeration value="SSD"/>
423-
<xs:enumeration value="resource"/>
433+
<xs:enumeration value="component"/>
434+
<xs:enumeration value="metaData"/>
424435
</xs:restriction>
425436
</xs:simpleType>
426437
</xs:attribute>

0 commit comments

Comments
 (0)