Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial draft of meta data element from SSP Traceability #28

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

pmai
Copy link
Collaborator

@pmai pmai commented Feb 2, 2024

This is the basic idea of porting the meta data container from SSP Traceability to SSD. Needs more refinement, and addition to other places, but should complement adding classifications for inline info vs. refering to external or different meta-data formats.

@pmai pmai added the enhancement New feature or request label Feb 2, 2024
@pmai pmai added this to the 2.0-alpha.1 milestone Feb 2, 2024
@pmai pmai self-assigned this Feb 2, 2024
@JochenKoehler
Copy link
Collaborator

Plan to discuss on April, 22. Dag and Klaus will review it (also Peter)

@JochenKoehler
Copy link
Collaborator

web meeting 2024-04-26
No reviews done so far - still pending

@peter-lobner
Copy link
Contributor

Personally I would vote to remove the signature stuff, as we don't have this for anything else in the SSP Standard currently.

@JochenKoehler
Copy link
Collaborator

Web meeting 2024-05-08
Discussion about adding signature.
Decision is pending where to add also the possibility to "attach" Meta data. And during this process it could be decided to add also signature for these parts.
More use of "complex type"? - Pierre will have some thoughts about it

@pmai pmai marked this pull request as ready for review May 9, 2024 08:51
@pmai
Copy link
Collaborator Author

pmai commented May 9, 2024

Added meta-data to the other places that reference resources; this raises a couple of questions, though:

  • The complex type for in-line content can't be reused, as most places where it would be used have additional content/checks, especially in the 1.1 schema.
  • As a couple of places directly inline the content (e.g. ParameterMapping, vs. ParameterBinding that has a separate element for the in-line content ParameterValues), this leads to the awkward situation that the MetaData element sits in the same place as the potential inline content; this really can't be expressed in 1.0 schema, and might still be a bit jarring in the 1.1 schema.
  • Relatedly, we might want to allow mixed-content (i.e. arbitrary text without any wrapping XML element) in some of those places, but that again does not work nicely if there is no wrapping element.

Changing any of this however would likely break back-ward compatibility and/or make the schema and handling more complex. So this is likely something that should be discussed at the F2F.

<xs:annotation>
<xs:documentation xml:lang="en">
This mandatory attribute specifies the MIME type of the resource meta data, which
does not have a default value. If no specific MIME type can be indicated, then
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

F2F 2024-06-12: Should maybe default to SRMD MIME Type? Better not, as that will likely lead to many non-SRMD files being attached but with the default MIME Type, which leads to problems.

@pmai
Copy link
Collaborator Author

pmai commented Jun 13, 2024

F2F 2024-06-12: Approach is sound, @pmai to add documentation changes based on the current proposal. Signature stuff stays in for now, as this would allow re-use of the definitions in the SSP Traceability Layer as-is. Decision might be revised prior to release if needed.

Copy link
Collaborator Author

@pmai pmai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CCB 2024-09-13: Signature element should also be added at the GMetaData level to allow signatures for the resources themselves and not only for their meta data. @pmai to make changes and PR to be rediscussed in next meeting for final merge.

@pmai
Copy link
Collaborator Author

pmai commented Sep 27, 2024

CCB 2024-09-27: GMetaData to be added at top-level to all other file formats, then PR can be merged by @pmai.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants