Skip to content
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

DT-1821-Updated the request json examples from the latest API spec #184

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

palatsangeetha
Copy link
Collaborator

No description provided.

Comment on lines 137 to 148
"partyName": "Hyundai",
"address": {
"street": "The street name would be here",
"city": "... and here the city",
"countryCode": "KR"
"street": "Ruijggoordweg",
"city": "Amsterdam",
"countryCode": "NL"
},
"identifyingCodes": [
{
"codeListProvider": "SMDG",
"codeListName": "LCL",
"partyCode": "HMM"
"codeListProvider": "W3C",
"partyCode": "MSK",
"codeListName": "DID"
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

The party code is for MSK (and should probably not use W3C + DID. It looks like an SMDG code instead). However, the partyName is for Hyundai (HMM).

I assume the original example is wrong. Probably the issuing party should be made a placeholder that the issuer can provide.

Comment on lines 119 to 123
{
"codeListProvider": "EPUI",
"codeListProvider": "W3C",
"partyCode": "CONSIGNEE_PARTY_CODE_PLACEHOLDER",
"codeListName": "CONSIGNEE_CODE_LIST_NAME_PLACEHOLDER"
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think these need to be turned into a placeholder objects. It is exceedingly likely that the parties do not have a fixed codeListProvider for this party.

I feel this basically applies to all parties with placeholders in them.

@nt-gt
Copy link
Collaborator

nt-gt commented Oct 8, 2024

The more I think about this, the more I feel this ends up overlapping with DT-1832 (assigned to me). I am not sure how best to go about this (how best to resolve the overlap). Maybe we just cut my comments out and leave them for me to deal with as a part of DT-1832 and then move forward with this as-is.

@palatsangeetha
Copy link
Collaborator Author

The more I think about this, the more I feel this ends up overlapping with DT-1832 (assigned to me). I am not sure how best to go about this (how best to resolve the overlap). Maybe we just cut my comments out and leave them for me to deal with as a part of DT-1832 and then move forward with this as-is.

Thanks Niels. I will go ahead and merge this PR then.

@palatsangeetha palatsangeetha merged commit 85e40cb into dev Oct 8, 2024
1 check passed
@palatsangeetha palatsangeetha deleted the DT-1821-Update-issuance-requestjson branch October 8, 2024 15:01
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