-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Just a question,
In this Cross Industry Invoice, it includes the fields
"applicableHeaderTradeSettlement": {
"specifiedTradeSettlementPaymentMeans": {
"payerPartyDebtorFinancialAccount": {
"typeCode": false
}
}
}
And in the JSONLD Spec, also under uncefact, I believe the equivalent would be:
https://vocabulary.uncefact.org/applicableTradeSettlement
https://vocabulary.uncefact.org/specifiedPaymentMeans
https://vocabulary.uncefact.org/payerPartyFinancialAccount
https://vocabulary.uncefact.org/debtorFinancialAccountTypeCode
Which follow the same nested pattern.
Is there a reason for the subtle differences between the naming? Are we able to translate easily between names or is any standardisation happening between the JSON Schemas and the JSON LD Project.
Cheers,
Metadata
Metadata
Assignees
Labels
No labels