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 11202 - Transfer: Factory needs to advertise the schemas it supports
Summary: Transfer: Factory needs to advertise the schemas it supports
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Transfer (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-02 20:19 UTC by Doug Davis
Modified: 2011-02-01 18:26 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2010-11-02 20:19:55 UTC 
Right now the Transfer Factory Policy is this:
<wst:TransferResourceFactory ...>
  <wst:Dialect URI="xs:anyURI" ...>
    xs:any*
  </wst:Dialect> *
  xs:any*
</wst:TransferResourceFactory>

This means that a client has no way of knowing what kinds of resources
the service can support creating.  Once a resource is created a client
can ask for the root element of the resource via its policy:
     <wst:Resource ...> xs:QName </wst:Resource> ?
but this is only useful after the resource has been created.

We need a way for the client to get this info prior to creating
the resource.

Proposal:
add
    <wst:Resource ...> xs:QName </wst:Resource> *
to the  wst:TransferResourceFactory policy assertion. 
Each wst:Resource element represents the QName/GED of
one type of Resource supported by this factory.  Its expected that there's
one wst:Resource element per type of resource that can be created.
There will be no requirement for the factory to support more than one.