| Predicate | Value |
|---|---|
| http://data.semanticweb.org/ns/swc/ontology#hasLocation | http://data.semanticuniverse.com/resource/regency-ballroom-i |
| http://data.semanticweb.org/ns/swc/ontology#isPartOf | http://data.semanticuniverse.com/resource/semtech-2008-semantic-soa-(service-oriented-architecture) |
| http://data.semanticweb.org/ns/swc/ontology#isPartOf | http://data.semanticuniverse.com/resource/semtech-2008-knowledge-engineering-and-management |
| http://data.semanticweb.org/ns/swc/ontology#isPartOf | http://data.semanticuniverse.com/resource/semtech-2008-foundational-topics |
| http://purl.org/dc/elements/1.1/abstract | Service-Oriented Architectures (SOA) are part of "silver bullet" technologies that are compelling but fail to live up to their promise. Reasons for this failure are beginning to be well-understood; We can salvage the vision with new uses of established technologies from the Web. |
| http://purl.org/dc/elements/1.1/audience | Technology - Intermediate |
| http://purl.org/dc/elements/1.1/creator | http://data.semanticuniverse.com/resource/uche-ogbuji |
| http://purl.org/dc/elements/1.1/creator | http://data.semanticuniverse.com/resource/brian-sletten |
| http://purl.org/dc/elements/1.1/description | Service-Oriented Architectures (SOA) are part of a long string of "silver bullet" technologies that are compelling and well-intentioned, but ultimately fail to live up to their promise. The reasons for this failure are beginning to be well-understood, however, and we can salvage the vision with some new uses of established technologies from the Web. <P> Physical architectures do not focus on a single aspect of the concrete instance; neither should our software. We need to focus on the physical and logical connections between a system's components and the flow of information through it. Additionally, we need to track information about the architecture and its data, map the business goals into the systems that support them and consider how our designs enable or inhibit regulatory compliance. This demanding set of requirements must be balanced by leveraging existing systems, team skills and an eye toward sustainable maintenance. <P> Semantically-enabled SOAs require the ability to express business concepts in the language of the implementation technologies in ways that are accessible to the non-technical stakeholders. This is a hard challenge to meet, but the Web and its semantic-oriented technologies continue to prove themselves in meeting this challenge. This tutorial will demonstrate the vision, the concepts, the patterns and guidance on implementation roadmaps for successful SOAs by leveraging these technologies. Specifically, we will cover: <P> addressing your documents, data, services and concepts with consistent, well-designed, long-lived logical names using a consistent metadata strategy for describing the topics of interest to your business use and reuse of existing systems, databases, services and components with minimal effort supporting a transparent architectural migration strategy driven by business, not technical, requirements passing around references to data rather than data itself to enable context-specific access control and logging strategies transforming the structure and level-of-detail of your information as it is being accessed while simultaneously enabling efficient use of computational resources decreasing the cost of and increasing the success rates for supporting regulatory compliance <P> |
| http://purl.org/dc/elements/1.1/title | T2: Semantically-Enabled Service Oriented Architectures |
| http://purl.org/net/biblio#presentedAt | http://data.semanticuniverse.com/resource/semtech-2008 |
| http://www.w3.org/1999/02/22-rdf-syntax-ns#type | http://www.w3.org/2002/12/cal/icaltzd/Vevent |
| http://www.w3.org/1999/02/22-rdf-syntax-ns#type | http://data.semanticweb.org/ns/swc/ontology#TutorialEvent |
| http://www.w3.org/2000/01/rdf-schema#label | T2: Semantically-Enabled Service Oriented Architectures |
| http://www.w3.org/2002/12/cal/icaltzd/dtEnd | 2008-05-19T12:00:00-07:00^^http://www.w3.org/2001/XMLSchema#dateTime |
| http://www.w3.org/2002/12/cal/icaltzd/dtStart | 2008-05-19T08:30:00-07:00^^http://www.w3.org/2001/XMLSchema#dateTime |
