hyperledger / indy-hipe Goto Github PK

I have a few initial questions.

• It is unclear to me who is creating the schema @id, the client or server? Should the @id be included in the txn set request? If so, the rich schema example is missing an @id key in the data.schema dict. I think the @id needs to be created by the client because the client signs the txn before it is sent. If the server creates the @id and appends it into the schema, the signature for the data being stored in the rocks DB will be different than the original signed data in the txn, which does not feel right to me.
• Is txnId in the set response the same thing as @id?
• txnId in set response has the form of L5AD5g65TDQr1PPHHRoiGf1|recipeIngredient|1.0 , with '|' as the delimiter while the current txnIds have ':' as the delimiter, for example, FC4aWomrA13YyvYC1Mxw7:3:CL:14:some_tag. Is there a good reason to break up continuity and use '|' instead of ':'?

HIPE 138 for Rich Schema Contexts has been available for review for one month.
How much longer does the review window stay open before its status may change to accepted?