OASIS eXtensible Access Control Markup Language (XACML) TC

Back to discussions
Expand all | Collapse all

XACML Intellectual Property Control (IPC) profile

  • 1.  XACML Intellectual Property Control (IPC) profile

    Posted 09-30-2009 01:22 
    The following issues have been idientified in the submitted work products and must be corrected before they can be uploaded to docs.oasis-open.org and the public review announced:

    1. Title of Specification:
    should be:  XACML v3.0 Intellectual Property Control (IPC) Profile Version 1.0

    2. Stage:
    should be: Committee Draft 01

    3. Date:
    must be date that specification was approved as a CD by the technical committee: DD Month YYYY

    4. Specification URIs
    This Version:
      You can use the URI Generator if you are not sure how to construct these: http://www.oasis-open.org/committees/uri-block-generator.php
    Previous Version:
      Should be "N/A" since this is the first version to be uploaded to docs.oasis-open.org
    Latest Version:
      Again, refer to the URI Generatorf
    Latest Approved Version:
      This is no longer part of the template and must be removed.

    4. Authoritative format: One of the three formats must be declared as authoritative and noted following the URL (Authoritative)

    5. Technical Committee:
      The hypertext link behind the text is not correct. should be: http://www.oasis-open.org/committees/workgroup.php?wg_abbrev=xacml

    6. Related work:
      The specification should be hypertext-linked to the actual spec

    7. Declared XML Namespaces:
      If none, this section should be removed

    8. Status Section
      Hypertext links behind the text pointing to TC pages are incorrect

    9. Footer
      The document identifier (file name without filetype extension) and date the CD02 was approved must be added

    10. References
      Citations to the work of any OASIS Committee must be in the proper format as noted in the templates:

    OASIS 
    Stage (Committee Draft 01, Committee Draft 02, Committee Specifcation 01, etc. or Standard)
    Title (italicized or in quotation marks)
    Approval Date (Month YYYY)
    URI of the actual Authoritative Specification (namespace is not acceptable as the content changes over time)

    For example:

    [EDXL-HAVE]

    OASIS Standard, "Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 1.0", November 2008.
    http://docs.oasis-open.org/emergency/edxl-have/os/emergency_edxl_have-1.0-spec-os.doc

    11. Non-normative reference to XACMLIntro - should be only a single hypertext link on the OASIS site. Not sure why other organization URLs are listed.

    12. Acknowledgements
    This should be  a list of current committee members as prepared by the TC Chair and submitted to the membership for corrections / requests for removals. It should not contain voting status; only names and organizational names of organizational members (otherwise Individual or Associate). Please remove asterisks after company names.



    The TC can make the appropriate changes and resubmit the Committee Draft, or, as an alternative, OASIS Staff will make the necessary changes upon request.

    Regards,

    Mary

     
    Mary P McRae
    Director, Standards Development
    Technical Committee Administrator
    OASIS: Advancing open standards for the information society
    twitter: fiberartisan  #oasisopen
    phone: 1.603.232.9090

    Standards are like parachutes: they work best when they're open.



Related Content