Skip to content

Semantic Linking definition #15

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SpyQuel
Copy link
Contributor

@SpyQuel SpyQuel commented Jun 15, 2022

The first draft of the Semantic Linking structure.
This field is an array containing objects with three fields that let the user identify the local field, the remote field, and the output port to which the remote field belongs.

@SpyQuel SpyQuel linked an issue Jun 15, 2022 that may be closed by this pull request
@SpyQuel SpyQuel marked this pull request as ready for review June 15, 2022 10:03
@agile-lab
Copy link
Contributor

@SpyQuel I think it should be more "semantic" and rely less on ID

@agile-lab
Copy link
Contributor

@SpyQuel we should merge this, I think is already used

#SemanticLink: {
fieldName: string
referenceOutputPort: #ExternalComponentId
refrenceFieldName: string

Choose a reason for hiding this comment

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

Minor typo on line 57

semanticLinking:
- fieldName: name
referenceOutputPort: urn:dmb:cmp:other_domain:other_data_product:2:other_event_port
refrenceFieldName: nameReference

Choose a reason for hiding this comment

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

Minor typo

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

Successfully merging this pull request may close these issues.

Define a structure for Semantic Linking
3 participants