split TripleId and PatternId #79
Description
Right now, a TripleId can have component values as 0 to be used as a pattern but then it is invalid as a triple.
Is that enough as a convention that is documented or should we split that?
{{ message }}
Right now, a TripleId can have component values as 0 to be used as a pattern but then it is invalid as a triple.
Is that enough as a convention that is documented or should we split that?