Skip to content

Conversation

@ronaldtse
Copy link
Contributor

No description provided.

@TRThurman
Copy link

@ronaldtse @stuartgalt, I question whether we should take credit for semantics, as we don't provide sufficient information for a post-processor to easily evaluate whether the EXPRESS declarations are valid.
I intend to write a Jira issue requiring express links and changes to the 'source' element to reference the schema instead of the part.
With that change (ediition 2 of this document?) , I think it is safe to claim support for semantics.
thoughts?

@ronaldtse
Copy link
Contributor Author

I started this document because I was trying to understand the mapping symbols and get a validator working.

The document is clearly in draft, so let's say it is "forward looking". In that sense, why don't we directly require the source being the schema (instead of part)? That makes lots of sense.

@TRThurman
Copy link

TRThurman commented Oct 21, 2025 via email

Copy link
Contributor Author

@ronaldtse ronaldtse left a comment

Choose a reason for hiding this comment

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

As agreed with @TRThurman we will first publish this and then supplement additional content regarding semantics later.

@ronaldtse ronaldtse force-pushed the rt-add-mapping-spec branch from f282cd9 to f68db43 Compare January 8, 2026 04:25
@ronaldtse ronaldtse merged commit 611e377 into main Jan 8, 2026
2 checks passed
@ronaldtse ronaldtse deleted the rt-add-mapping-spec branch January 8, 2026 04:42
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.

3 participants