This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6803 - RT: Is this functionality required?
Summary: RT: Is this functionality required?
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: ResourceTransfer (show other bugs)
Version: FPWD
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Geoff Bullen
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on: 6413 7088
Blocks:
  Show dependency tree / graph
 
Reported: 2009-04-10 23:41 UTC by Geoff Bullen
Modified: 2009-07-14 21:35 UTC (History)
0 users

See Also:

Attachments

Description Geoff Bullen 2009-04-10 23:41:41 UTC 
Based on recent WG discussions, it is now unclear if the functionality mentioned below is required for RT or if it should be removed.

1)RT 3.2.1 QName Dialect
2)RT 3.2.2 XPath 1.0 Dialect
3)RT Put/Fragment/@Mode
4)RT 4. Faults
    a)ConcurrencyFault
    b)InvalidExpressionFault (re-named as 'InvalidExpression')
    c)GetFault
    d)ResourceValidityFault
    e)FragmentAlreadyExistsFault
    f)PutFault
    g)PutModeUnsupportedFault
    h)CreateFault
    i)InvalidMetadataFault
    j)MultipartExceededFault
    k)InvalidPutSyntaxFault
5)Appendix II Resource Metadata Content
6)Appendix II.A Lifecycle metadata
7)Appendix II.B Expression Dialect Metadata

Proposal: Remove functionality from RT specification.
Comment 1 Robert Freund 2009-07-14 21:34:53 UTC 
Overtaken by decision to create a fragment spec.
Closed without prejudice