UBL Naming and Design Rules SC

 View Only

[ubl-ndrsc] Naming conventions of business documents?

  • 1.  [ubl-ndrsc] Naming conventions of business documents?

    Posted 03-04-2003 08:09
     MHonArc v2.4.5 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl-ndrsc message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: [ubl-ndrsc] Naming conventions of business documents?


    Title: Naming conventions of business documents?

    Hello all,

    I have a question to the naming conventions of the name of business documents.

    Every name of business documents exists of three parts:

            - Object: PurchaseOrder, Invoice, DeliverySchedule, etc.
            - Method: Transfer, Create, Update, Delete
            - Activity: Notification, Query, Response, Collaboration, Negotiation, Request, Confirmation

    How can we assembly this three parts in names business documents? Like: "Create. Delivery. Notification"
    Is the name of the generic header the same as the name of the business document?
    Do some rules existing now? Do we assembling like that: Method. Object. Acitivity?
    Should we use for the activity verbs or nouns?
    Are the terms "Object", "Method" and "Ativity" enough or too much?
    Do you have another suggestions?

    It would be very glad, if you can help me.
    Thank you very much.

    Kind regards,

            Gunther



    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]