Skip to content

Question on Naming Scheme Compatibility with JSONLD #4

@ChrisJMacdonald

Description

@ChrisJMacdonald

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions