RE: [sca-assembly] ISSUE 11: Define Conformance Targets

["Michael Rowley" <mrowley@bea.com>]

My thoughts on possible targets:

- Deployment infrastructure 
   * e.g. MUST generate deployment errors

- Runtime
   * e.g. MUST support a default binding (binding.sca) for
communication?

- Binding Type
   * e.g. a valid binding type MUST declare the intents it
"alwaysProvides"

- Implementation Type
   * e.g. implementation types SHOULD support conversational interfaces

- Interface Type
   * e.g. any valid interface type MUST be translatable to/from WSDL 1.1
   (but does that mean any software has to actually do the translation?)

Michael


-----Original Message-----
From: Scott Vorthmann [mailto:scottv@tibco.com] 
Sent: Monday, October 22, 2007 11:35 AM
To: OASIS Assembly
Subject: [sca-assembly] ISSUE 11: Define Conformance Targets


ISSUE LOGGED:

http://www.osoa.org/jira/browse/ASSEMBLY-11


On Oct 22, 2007, at 4:42 AM, Martin Chapman wrote:

> TARGET: SCA Assembly Specification
>
> DESCRIPTION: In order to write a normative statement or conformance  
> clause using RFC2119 language, the target or subject of the rule
> needs to be included. Some of these are obvious, as we have rules  
> governing components, composites, services, references etc. Other
> targets are less so, especially when it comes to conformance, as we  
> need to identify artefacts that vendors can claim they handle
> according to the rules of the spec. We should enumerate a list of  
> conformance targets early on, so that every time we use a MUST,
> MAY, or SHOULD, we know to what the rule applies to.
>
> PROPOSAL: none
>
> _________________________________________________________________
> Martin Chapman
> Consulting Member of Technical Staff
> Oracle
> P: +353 87 687 6654
> e: martin.chapman@oracle.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs  
> in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php