新书推介:《语义网技术体系》
作者:瞿裕忠,胡伟,程龚
   XML论坛     W3CHINA.ORG讨论区     计算机科学论坛     SOAChina论坛     Blog     开放翻译计划     新浪微博  
 
  • 首页
  • 登录
  • 注册
  • 软件下载
  • 资料下载
  • 核心成员
  • 帮助
  •   Add to Google

    >> XML与数字内容安全(DRM,XrML,RDD, MPEG-21, XACML), XML传输的安全, 基于XML的签名,基于XML的加密
    [返回] 中文XML论坛 - 专业的XML技术讨论区XML.ORG.CN讨论区 - 高级XML应用『 XML安全 』 → WS-Policy已于2006年4月26日提交给W3C 查看新帖用户列表

      发表一个新主题  发表一个新投票  回复主题  (订阅本版) 您是本帖的第 12050 个阅读者浏览上一篇主题  刷新本主题   树形显示贴子 浏览下一篇主题
     * 贴子主题: WS-Policy已于2006年4月26日提交给W3C 举报  打印  推荐  IE收藏夹 
       本主题类别:     
     admin 帅哥哟,离线,有人找我吗?
      
      
      
      威望:9
      头衔:W3China站长
      等级:计算机硕士学位(管理员)
      文章:5255
      积分:18406
      门派:W3CHINA.ORG
      注册:2003/10/5

    姓名:(无权查看)
    城市:(无权查看)
    院校:(无权查看)
    给admin发送一个短消息 把admin加入好友 查看admin的个人资料 搜索admin在『 XML安全 』的所有贴子 点击这里发送电邮给admin  访问admin的主页 引用回复这个贴子 回复这个贴子 查看admin的博客楼主
    发贴心情 WS-Policy已于2006年4月26日提交给W3C

    [URL=http://www.w3.org/Submission/]按此在新窗口浏览图片[/URL]| [URL=http://www.w3.org/Submission/]Submissions[/URL]

    Submission request to W3C ([URL=http://www.w3.org/Submission/2006/06/Comment]W3C Team Comment[/URL])

    WS-Policy Submission request to W3C
    Submitted Materials
    We, W3C Members Adobe Systems, BEA Systems, CA, Ericsson, IBM, IONA, Layer 7 Technologies, Microsoft, Nokia, Oracle, Ricoh Company, SAP, Sonic Software, Sun Microsystems, Inc., Systinet, A Mercury Division, TIBCO Software, VeriSign, webMethods and WSO2 hereby submit to the Consortium the following specification, comprising the following documents attached hereto:

    [URL=http://www.w3.org/Submission/WS-Policy/]WS-Policy[/URL]
    [URL=http://www.w3.org/Submission/WS-PolicyAttachment/]WS-PolicyAttachment[/URL]
    which is referred to as "the Submission". We request the Submission be known as the WS-Policy Submission.

    Abstract
    Web Services Policy defines a flexible policy data model and an extensible grammar for expressing the capabilities, requirements and general characteristics of a Web Service. It also describes mechanisms for associating policies with Web service constructs. It is used to convey the conditions for an interaction between a Web service requestor and a Web service provider.

    Intellectual Property Statements
    Copyrights
    BEA Systems
    BEA hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any BEA copyrights on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, BEA grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. BEA further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    IBM
    IBM hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any IBM copyrights on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, IBM grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. IBM further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    Microsoft
    Microsoft hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Microsoft copyrights on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, Microsoft grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. Microsoft further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    SAP AG
    SAP AG hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any SAP AG on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, SAP AG grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. SAP AG further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    Sonic Software
    Sonic hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any Sonic copyrights on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, Sonic grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. Sonic further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    VeriSign
    VeriSign hereby grants to the W3C a perpetual, nonexclusive, royalty-free, world-wide right and license under any VeriSign copyrights on this contribution, to copy, publish and distribute the contribution under the [URL=http://www.w3.org/Consortium/Legal/copyright-documents]W3C document licenses[/URL].

    Additionally, should the Submission be used as a contribution towards a W3C Activity, VeriSign grants a right and license of the same scope to any derivative works prepared by the W3C and based on, or incorporating all or part of, the contribution. VeriSign further agrees that any derivative works of this contribution prepared by the W3C shall be solely owned by the W3C.

    Trade and Service Marks
    The Submission request or Submission refers to the following trade and service marks (registered or not): none.

    Patents
    Adobe Systems
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    BEA Systems
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    CA
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Ericsson
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    IBM
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    IONA
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Layer 7 Technologies
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Microsoft
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Nokia
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Oracle
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Ricoh Company
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    SAP AG
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Sonic Software
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Sun Microsystems, Inc.
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Systinet, A Mercury Division
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    TIBCO Software
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    VeriSign
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    webMethods
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    WSO2
    The organization I represent on the W3C Advisory Committee agrees to offer licenses according to the W3C Royalty-Free licensing requirements described in [URL=http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements]section 5 of the 5 February 2004 W3C Patent Policy[/URL] for any portion of the Submission that is subsequently incorporated in a W3C Recommendation.

    Suggested action
    We suggest that the Consortium start a Working Group whose mission is to produce W3C Recommendations for Web Services Policy by refining the Submission, addressing implementation experience and interoperability feedback from the Submission, and considering composition with other components in the Web services architecture.

    Resources
    To help with this work, we expect to be able to provide customary resources (Working Group participants, editors and chairs according to each submitting company's ability).

    Contact
    Inquiries from the public or press about this Submission should be directed to: [URL=mailto:rmichals@adobe.com]Rebecca Michals[/URL] (Adobe Systems), [URL=mailto:kclarke@bea.com]Kelly Clarke[/URL] (BEA Systems), [URL=mailto:robert.gordon@ca.com]Robert Gordon[/URL] (CA), [URL=mailto:marc.leclerc@ericsson.com]Marc LeClerc[/URL] (Ericsson), [URL=mailto:favali@us.ibm.com]Ron Favali[/URL] (IBM), [URL=mailto:Robert.morton@iona.com]Robert Morton[/URL] (IONA), [URL=mailto:dsirota@layer7tech.com]Dimitri Sirota[/URL] (Layer 7 Technologies), [URL=mailto:arib@microsoft.com]Ari Bixhorn[/URL] (Microsoft), [URL=mailto:Bjorn.Wigforss@nokia.com]Bjorn Wigforss[/URL] (Nokia), [URL=mailto:teri.whitaker@oracle.com]Teri Whitaker[/URL] (Oracle), [URL=mailto:hitoshi@ussj.ricoh.com]Hitoshi Sekine[/URL] (Ricoh Company), [URL=mailto:lindsey.held@sap.com]Lindsey Held[/URL] (SAP AG), [URL=mailto:ckucera@sonicsoftware.com]Trip Kucera[/URL] (Sonic Software), [URL=mailto:Jacquelyn.Decoster@Sun.COM]Jacki DeCoster[/URL] (Sun Microsystems, Inc.), [URL=mailto:ibruce@mercury.com]Ian Bruce[/URL] (Systinet, A Mercury Division), [URL=mailto:hlawrenc@tibco.com]Holly Lawrence[/URL] (TIBCO Software), [URL=mailto:brlewis@verisign.com]Brenden Lewis[/URL] (VeriSign), [URL=mailto:jconley@webmethods.com]John Conley[/URL] (webMethods), and [URL=mailto:hasmin@wso2.com]Hasmin AbdulCader[/URL] (WSO2).

    Submitted
    this 13th day of April, 2006,

    [URL=mailto:crm@adobe.com]Charles Myers[/URL] (Adobe Systems), [URL=mailto:dorchard@bea.com]David Orchard[/URL] (BEA Systems), [URL=mailto:kirk.wilson@ca.com]Kirk Wilson[/URL] (CA), [URL=mailto:Per.Frojdh@ericsson.com]Per Fröjdh[/URL] (Ericsson), [URL=mailto:shh@us.ibm.com]Steve Holbrook[/URL] (IBM), [URL=mailto:Eric.Newcomer@iona.com]Eric Newcomer[/URL] (IONA), [URL=mailto:tboubez@layer7tech.com]Toufic Boubez[/URL] (Layer 7 Technologies), [URL=mailto:kyley@microsoft.com]Kyle Young[/URL] (Microsoft), [URL=mailto:art.barstow@nokia.com]Arthur Barstow[/URL] (Nokia), [URL=mailto:jeff.mischkinsky@oracle.com]Jeff Mischkinsky[/URL] (Oracle), [URL=mailto:mutsuo.ogawa@nts.ricoh.co.jp]Mutsuo Ogawa[/URL] (Ricoh Company), [URL=mailto:david.burdett@sap.com]David Burdett[/URL] (SAP AG), [URL=mailto:gdaniels@sonicsoftware.com]Glen Daniels[/URL] (Sonic Software), [URL=mailto:eduardo.gutentag@sun.com]Eduardo Gutentag[/URL] (Sun Microsystems, Inc.), [URL=mailto:pdvorak@mercury.com]Petr Dvorak[/URL] (Systinet, A Mercury Division), [URL=mailto:donmullen@tibco.com]Don Mullen[/URL] (TIBCO Software), [URL=mailto:pbaker@verisign.com]Phillip Hallam-Baker[/URL] (VeriSign), [URL=mailto:epeters@webmethods.com]Ed Peters[/URL] (webMethods), and [URL=mailto:sanjiva@wso2.com]Sanjiva Weerawarana[/URL] (WSO2).


       收藏   分享  
    顶(0)
      




    ----------------------------------------------

    -----------------------------------------------

    第十二章第一节《用ROR创建面向资源的服务》
    第十二章第二节《用Restlet创建面向资源的服务》
    第三章《REST式服务有什么不同》
    InfoQ SOA首席编辑胡键评《RESTful Web Services中文版》
    [InfoQ文章]解答有关REST的十点疑惑

    点击查看用户来源及管理<br>发贴IP:*.*.*.* 2006/4/27 17:15:00
     
     GoogleAdSense
      
      
      等级:大一新生
      文章:1
      积分:50
      门派:无门无派
      院校:未填写
      注册:2007-01-01
    给Google AdSense发送一个短消息 把Google AdSense加入好友 查看Google AdSense的个人资料 搜索Google AdSense在『 XML安全 』的所有贴子 点击这里发送电邮给Google AdSense  访问Google AdSense的主页 引用回复这个贴子 回复这个贴子 查看Google AdSense的博客广告
    2024/4/26 19:54:58

    本主题贴数1,分页: [1]

    管理选项修改tag | 锁定 | 解锁 | 提升 | 删除 | 移动 | 固顶 | 总固顶 | 奖励 | 惩罚 | 发布公告
    W3C Contributing Supporter! W 3 C h i n a ( since 2003 ) 旗 下 站 点
    苏ICP备05006046号《全国人大常委会关于维护互联网安全的决定》《计算机信息网络国际联网安全保护管理办法》
    5,328.125ms