Dan, Ah, thank you, I understand.
Is it permissible to modify the Capability URIs in muse.xml after code generation? I assume it won't cause any adverse affects? Thanks Jared -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 29, 2007 3:07 PM To: [email protected] Subject: Re: Capability URIs and Resource Property Namespaces I explained the convention in another reply, but to answer your question on standards-compliance: Muse uses the proper namespace URIs for standard properties and the proper capability URIs for standard capabilities; only custom capabilities are subject to our convention, because those are the ones we need to generate code for. Dan "Jared A. Zebedee" <[EMAIL PROTECTED]> wrote on 08/29/2007 02:36:02 PM: > I have built a Manageable Resource which includes custom Capabilities. > > It appears that Muse interprets each Resource Property Schema referenced in > the WSDL as a Capability. Each Capability is assigned a URI that matches > the namespace of the corresponding Resource Property Schema. > > In the WSDM specification, Capability URIs are not the same as Resource > Property namespaces: > > For example, the 'ResourceID' Resource Property is part of the 'Identity' > Capability. > > The 'Identity' Capability's URI is: > http://docs.oasis-open.org/wsdm/muws/capabilities/Identity > > The 'ResourceID' Property's Namespace is: > http://docs.oasis-open.org/wsdm/muws1-2.xsd > > But for each of my custom Capabilities, the Capability URI is the same as > the Namespace URI of all the Properties that are part of the Capability. I > personally like the idea of them being the same, but I'm not sure if this is > allowable by the Standard. Am I doing something wrong, or is this how Muse > is designed to deal with Capabilities? > > Jared Zebedee > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
