UBL Naming and Design Rules SC

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

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

    Posted 03-04-2003 15:56
    I believe we have a rule about this, but it's very vague and just talks 
    about reflecting the "business process".  If it makes sense, we could 
    get more specific (but if we recommend a tripartite name with dots, 
    people might confuse it with CC names! :-).
    
    	Eve
    
    Stuhec, Gunther wrote:
    > 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
    > 
    
    -- 
    Eve Maler                                        +1 781 442 3190
    Sun Microsystems                            cell +1 781 354 9441
    Web Technologies and Standards               eve.maler @ sun.com
    
    
    ----------------------------------------------------------------
    To subscribe or unsubscribe from this elist use the subscription
    manager: <http://lists.oasis-open.org/ob/adm.pl>