Joe, I didn't mean to imply you should redefine them. Just reference the core spec. Currently, the core spec isn't technically a domain.
Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM & Reporting Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: Joe Ross/Austin/IBM@IBMUS To: Arthur Ryman <[email protected]> Cc: [email protected], [email protected] Date: 08/26/2011 09:50 AM Subject: Re: [oslc-core] domain URL for Service that supports creation/query of Service Provider resources Arthr, We are actually representing most (if not all) of the core resource types (Service, CreationFactory, QueryCapability, etc.) in the Provider Registry records. Basically products register all of their capabilities and access points by OSLC core resource records in the Provider Registry. Most of the resources are in-line and part of the complete Service Provider record being registered. We will probably also need to register Resource Shapes and their properties for a complete understanding of provider capabilities. Since these resource types are already defined in the Core specification, I would prefer not to have to redefine them all in a domain spec. Thanks, ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311 From: Arthur Ryman <[email protected]> To: Joe Ross/Austin/IBM@IBMUS Cc: [email protected], [email protected] Date: 08/26/2011 07:00 AM Subject: Re: [oslc-core] domain URL for Service that supports creation/query of Service Provider resources Joe, Your Service Provider registry service sounds interesting. I am a little concerned about you using http://open-services.net/ns/core# as the domain since we haven't specified what that would mean. Here is the definition of what a Domain is: OSLC Domain: an OSLC Domain is one ALM or PLM topic area such as Change Management, Requirements management or Automation. Each OSLC Domain will have its own OSLC specification that complies with this Core specification. I think we should have a spec that outlines the types of resources in the domain. You have selected just one type of core resource. Perhaps you should specify that and coin a URI for it? Regards, ___________________________________________________________________________ Arthur Ryman DE, PPM & Reporting Chief Architect IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: Joe Ross <[email protected]> To: [email protected] Date: 08/25/2011 10:49 PM Subject: [oslc-core] domain URL for Service that supports creation/query of Service Provider resources Sent by: [email protected] In Tivoli, we are creating a Provider Registry that is itself implemented as a Service Provider (a Service Provider for Service Provider resources). We want to do this, so that we can support creation of Service Provider records using a Creation Factory and querying for Service Providers using a Query Capability. As part of defining the Service, we need to provide an oslc:domain with namespace URI. Does it make sense for us to use the OSLC Core namespace URI (http://open-services.net/ns/core# ) for this? That seems logical since all of the resources we are supporting in this Provider Registry Service Provider are defined in the OSLC Core spec. Thanks much, ================================================ Joe Ross/Austin/IBM, [email protected] Tivoli Autonomic Computing & Component Technologies 512-286-8311, T/L 363-8311_______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
