You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the number data type serves both as a data type and a semantic type, causing inconsistency across the code base.
The PR #2616 initiated some harmonization steps, but there are still dual definitions for the number type:
One in DataType (XSD:number)
One in SemanticType (SO:number)
I propose supporting number solely as a data type and eliminating its role as a semantic type.
However, prior to making this change, it's crucial to assess which pipeline elements rely on number as a semantic type.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.
The text was updated successfully, but these errors were encountered:
Body
Currently, the number data type serves both as a data type and a semantic type, causing inconsistency across the code base.
The PR #2616 initiated some harmonization steps, but there are still dual definitions for the number type:
DataType
(XSD:number
)SemanticType
(SO:number
)I propose supporting number solely as a data type and eliminating its role as a semantic type.
However, prior to making this change, it's crucial to assess which pipeline elements rely on number as a semantic type.
StreamPipes Committer
I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.
The text was updated successfully, but these errors were encountered: