OASIS Business Document Exchange (BDXR) TC

 View Only

FW: [bdxr-comment] ePrior requirements

  • 1.  FW: [bdxr-comment] ePrior requirements

    Posted 05-05-2015 15:39




    Dear Thomas Small


    Through Ole Madsen from DIGST in Denmark, the OASIS BDXR TC received the below comments from ePrior to our recent public review of the Business Document Envelope (BDE) draft committee specification version 1.0. On behalf of the TC I would appreciate if
    you can help me clarify the following two items:



    “Only one receiver ID is supported, it is therefore not possible to specify several schemes (i.e. one or several receivers – recipient
    list, multicast)”


    The BDE has been designed for point-to-point scenarios, such as 4-cornered architectures. Notwithstanding, we would be interested in understanding and assessing any specific use cases for multicasting. Does ePrior have such a use case that we can have
    a look at?





    “External references do not seem to support "external attachments" using URL, file path, MIME part reference (for multi parts items) ”


    The purpose of this requirement/comment is not immediately clear to us, and we are not sure whether this is actually a requirement for the content of the envelope (any given business document) or a requirement for the envelope itself. Could you please
    elaborate a bit on this comment and possibly send us one or two examples or use cases for where this is required?



    Thank you in advance.


    Best regards,


    Kenneth Bengtsson
    Chair, OASIS BDXR TC










    From: Ole Ellerbæk Madsen
    Date: Friday, April 24, 2015 at 4:08 AM
    To: " bdxr-comment@lists.oasis-open.org "
    Subject: [bdxr-comment] ePrior requirements








     
    Videresendt fra ePrior:
     
    The Envelope specifications have been reviewed by our team in regard of the ePrior requirements.
     
    Please find below the comments raised during the review:
    -          
    Binary files are included in the envelope, which might generate issues with very large files (parsing highly time consuming)
    -          
    Only one receiver ID is supported, it is therefore not possible to specify several schemes (i.e. one or several receivers
    – recipient list, multicast)
    -          
    External references do not seem to support "external attachments" using URL, file path, MIME part reference (for multi
    parts items)
     
    May you need further clarifications, do not hesitate to contact us.
     
     
    Venlig hilsen/Best Regards
    Ole Madsen