[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: External References in SOA-RM Reference Architecture
Everyone, When I suggested that we need to have an explicit box/conceptual place for "External References" beyond that allocated in Ken's diagram for 3rd Party Annotations from Identity & Provenance, and now in Danny's reworked diagram directly from Service Description, http://wiki.oasis-open.org/soa-rm/TheArchitecture/ServiceDescription#preview I meant that we should explicitly call out in our Reference Architecture External References such as the Web Services for Remote Portlets Specification 1.0, which can be found at: http://www.oasis-open.org/apps/org/workgroup/wsrp/documents.php?expand_folder_id=1085#folder_1085. V 2.0 is nearing readiness for an OASIS-wide vote. My expectation is that we will need to have a place in our architecture where references which specifically identify both the standards with which a service either complies or conforms and the source or custodian/location of the specification can be cited/invoked. I am not suggesting that this include any specific standards, nor proprietary offerings such as ESBs, but I think it is necessary for us to include an ability to reference such specifications within the Service Description because they can be, and, are becoming major, if not required components of a Service Description. I waited until after today's WSRP meeting to send this so that I could get a feel for whether anyone might be interested in pursuing this further, and it was suggested that I send more information about this to the wsrp list, so I am copying that list as well with this message. I think that this is an area where the apparently inactive SOA Blueprints TC could provide tech notes from the various Web Services TCs for connecting such specifications as WSS, SAML. XACML and the various Web Service Policy, WSBPEL, Web Services Reliable Messaging, etc., as well as WSRP. However, be that as it may, I believe our Reference Architecture ought to have a place for an obvious, extent set of external references to key resources. Cheers, Rex -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]