Private Dictionary and Part 3 as XML - DICOM

This is a discussion on Private Dictionary and Part 3 as XML - DICOM ; Hi there, I have created a central XML file that gather all private DICOM data elements (just like Part 6 for public elements). A couple of things: - It's XML so this is trivial to transform to (almost)anything else - ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Private Dictionary and Part 3 as XML

  1. Private Dictionary and Part 3 as XML

    Hi there,

    I have created a central XML file that gather all private DICOM data
    elements (just like Part 6 for public elements). A couple of things:
    - It's XML so this is trivial to transform to (almost)anything else
    - It's generation process allows one to simply 'append' any new DCS
    from a private vendor.

    The result file is:
    http://gdcm.svn.sourceforge.net/view...ml?view=markup

    But the actual real one is this one:
    http://gdcm.svn.sourceforge.net/view...ml?view=markup

    The syntax is extremly simple. Anyone can simply add an XML file
    representing the dict of a particular private vendor. If anyone is
    interested in doing so, please send me your private dict.
    I encourage such people to read a couple of other private dictionary
    to understand what is required, for instance:

    http://gdcm.svn.sourceforge.net/view...ml?view=markup

    The file naming convention is simply to use the same basename as the
    DCS, and -most important thing- to include the URL to the DCS, which
    potentially allow other people to validate/verify a particular XML-
    DCS.

    As of today the merging process is quite limited, and whichever file
    comes first will be used in case of duplicate data elements. A notion
    of date is already present and will be used in a more advanced merging
    process.

    ---------------------------------------:


    I have previously send this newsgroup, an XML version of PS 3.6 -
    2008. I am now sending a *partial* PS 3.3 - 2008 XML file:
    http://gdcm.svn.sourceforge.net/view...ml?view=markup

    Three types of tables are present: macro, iod and module. Some work
    still need to be done to polish/reformat Enumerated Values / Defined
    Terms, and some section are still missing (work in progress).
    This file is for the most part automatically generated from the .doc
    file from the official medical.nema.org website.

    Looking for your comments and/or bug report

    Thanks for your time,
    -Mathieu
    Ps: you are -of course- encouraged to use the svn command to retrieve
    those files instead of your web browser. See:
    http://sourceforge.net/svn/?group_id=137895

  2. Re: Private Dictionary and Part 3 as XML

    Fantastic work Mathieu!

    Best regards,
    Razvan C.B.


    > Hi there,
    >
    > I have created a central XML file that gather all private DICOM data
    > elements (just like Part 6 for public elements). A couple of things:
    > - It's XML so this is trivial to transform to (almost)anything else
    > - It's generation process allows one to simply 'append' any new DCS
    > from a private vendor.
    >
    > The result file is:
    > http://gdcm.svn.sourceforge.net/view...vate.xml?view=...
    >
    > But the actual real one is this one:
    > http://gdcm.svn.sourceforge.net/view...ex.xml?view=ma...
    >
    > The syntax is extremly simple. Anyone can simply add an XML file
    > representing the dict of a particular private vendor. If anyone is
    > interested in doing so, please send me your private dict.
    > I encourage such people to read a couple of other private dictionary
    > to understand what is required, for instance:
    >
    > http://gdcm.svn.sourceforge.net/view...s/contour72.xm...
    >
    > The file naming convention is simply to use the same basename as the
    > DCS, and -most important thing- to include the URL to the DCS, which
    > potentially allow other people to validate/verify a particular XML-
    > DCS.
    >
    > As of today the merging process is quite limited, and whichever file
    > comes first will be used in case of duplicate data elements. A notion
    > of date is already present and will be used in a more advanced merging
    > process.
    >
    > ---------------------------------------:
    >
    > I have previously send this newsgroup, an XML version of PS 3.6 -
    > 2008. I am now sending a *partial* PS 3.3 - 2008 XML file:http://gdcm.svn.sourceforge.net/view...e/InformationO...
    >
    > Three types of tables are present: macro, iod and module. Some work
    > still need to be done to polish/reformat Enumerated Values / Defined
    > Terms, and some section are still missing (work in progress).
    > This file is for the most part automatically generated from the .doc
    > file from the official medical.nema.org website.
    >
    > Looking for your comments and/or bug report
    >
    > Thanks for your time,
    > -Mathieu
    > Ps: you are -of course- encouraged to use the svn command to retrieve
    > those files instead of your web browser. See:http://sourceforge.net/svn/?group_id=137895



+ Reply to Thread