[OASIS Issue Tracker] (UBL-67) Principle of providing codes as text is not implement for the fulfillment documents.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/UBL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66758#comment-66758 ] 

Kees Duvekot commented on UBL-67:
---------------------------------

this is also related to UBL-66.

We need to go through all code elements to find the equivalent "non code" elements to see if we have a 1 to 1 match between the two (if we really want to update all elements)
Is there a "design rule" where you always provide a "non code" equivalent element?


> Principle of providing codes as text is not implement for the fulfillment documents.
> ------------------------------------------------------------------------------------
>
>                 Key: UBL-67
>                 URL: https://issues.oasis-open.org/browse/UBL-67
>             Project: OASIS Universal Business Language (UBL) TC
>          Issue Type: Improvement
>          Components: Documents and business objects
>            Reporter: Ken Holman
>            Assignee: Ken Holman
>            Priority: Minor
>
> General comment: The 2.1 principle of providing codes as text is not implement for the fulfillment documents.
> https://lists.oasis-open.org/archives/ubl-comment/201702/msg00001.html



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)