OASIS Charter Submission Discuss

Re: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

  • 1.  Re: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

    Posted 10-27-2010 16:20
    
    
    
    
    
    
    
    
    
    
    From an MoU/Management Group perspective, it is not clear what differentiates this from "yet another messaging specification'

    Howard Mason (via Blackberry)
    Corporate IT Office
    Tel: +44 1252 383129
    Mob: +44 780 171 3340
    Eml: howard.mason@baesystems.com

    BAE Systems plc
    Registered Office: 6 Carlton Gardens, London, SW1Y 5AD, UK
    Registered in England & Wales No: 1470151


    From: Martin Chapman <MARTIN.CHAPMAN@oracle.com>
    To: Pim van der Eijk <pvde@sonnenglanz.net>; Ray Denenberg, Library of Congress <rden@loc.gov>; oasis-charter-discuss@lists.oasis-open.org <oasis-charter-discuss@lists.oasis-open.org>
    Sent: Wed Oct 27 17:11:52 2010
    Subject: RE: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

                        *** WARNING ***

      This message has originated outside your organisation,
      either from an external partner or the Global Internet.
          Keep this in mind if you answer this message.

    I’m more concerned with the intention of the TC and the name of any eventual specifications than the name of the TC itself. I think Ed asks the most relevant question here. This TC seems to be more about protocols to exchange documents rather than about the content of any documents. This needs clarification.

    Martin.

    From: Pim van der Eijk [mailto:pvde@sonnenglanz.net]
    Sent: 27 October 2010 16:55
    To: Ray Denenberg, Library of Congress; oasis-charter-discuss@lists.oasis-open.org
    Subject: RE: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

    Very funny.   (At least,  I'm assuming this is intended to be funny.  But I can't really tell, as I'm not a native speaker of English).

     

    You may have noted that some of the co-proposers of this charter are native speakers of English.   I will check again,  but as far as I know it was one of them that actually proposed this abbreviation.   I never questioned the abbreviation as I only got involved in the discussions when the abbreviation "BusDox" was already there.  

     

    FYI, there is also an OASIS DITA BusDocs SC. 

    http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-busdocs 

    DITA BusDocs means "DITA Enterprise Business Documents SC"

    It looks like the vast majority of the members of this SC are native speakers of English.  

     

    A quick Internet search seems to show that BIZdocs is some trademark, so it would violate the following TC process rule:

    "The name of the TC, such name not to have been previously used for an OASIS TC and not to include any trademarks or service marks not owned by OASIS".

    http://www.oasis-open.org/committees/process.php

     

    I'm tempted to continue but I think I should stop here.

     

     


    From: Ray Denenberg, Library of Congress [mailto:rden@loc.gov]
    Sent: 27 October 2010 17:27
    To: oasis-charter-discuss@lists.oasis-open.org
    Subject: RE: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

    "they will
    assume that the work of the group has something to do with buses
    and then puzzle unfruitfully over what "dox" could refer to."

    I didn't have any trouble with "dox". I assume it meant "docks" and that the spec had to do with where to park buses.

    --Ray


    ********************************************************************
    This email and any attachments are confidential to the intended
    recipient and may also be privileged. If you are not the intended
    recipient please delete it from your system and notify the sender.
    You should not copy it or use it for any purpose nor disclose or
    distribute its contents to any other person.
    ********************************************************************