"... In PAGE 8: ...able 1 - SCSI and Fibre Channel protocol functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Table2 - Discovery of FCP-2 capabilities .... In PAGE 29: ...7 Discovery of FCP capabilities A number of Fibre Channel protocol capabilities require the knowledge and agreement of both the target and the initiator that such capabilities may or shall be used. Table2 provides references to the discovery process for each of the Fibre Channel protocol capabilities. 4.... ..."

"... In PAGE 3: ... Thus the variety of browsers is becoming less of an issue than it used to be. See Table7 for further details of the different types of browser being used to access VLmp. Summary Period: 135 Days Daily Unique: Totals: Today 730 / 27 Apr, Thu, 2000 Unique Visitors 125729 - 68.... ..."

"... In PAGE 2: ... The following four are the most popularly used web browsers in the market today on the windows platform. The abbreviations listed in Table1... In PAGE 6: ... Table 12. Functions to be tested IE OP FF NS Lstrcat Lstrcpy Lstrcpyn Strncpy Wcscat Wcscpy Lstrcpy Lstrcpyn Wcscpy Lstrcat Lstrcpy Lstrcpyn Memcpy Strncpy Lstrcat Lstrcpy Lstrcpyn Memcpy Strncpy From Table1 4, functions that were commonly used by all the browsers were selected. Lstrcpy and Lstrcpyn are two functions that are used by all the four browsers.... ..."

"... In PAGE 3: ... A typical scenario for a browser would consist of a (rel- atively long) sequence of accesses to pages that present product-related information. Our tests use browser sessions of length 20, made up of individual page requests with the weights shown in Table2 . Each session is a logically or- ganized sequence of requests starting with the Main page.... ..."

"... In PAGE 8: ...integrates a diagnostic module for the prerequisite units in the presentation of the current unit. In Table2 some examples for the rules implemented in the system and the resulting presentation can be seen. Table 2: Example modifications of the default teaching strategies depending on learner characteristics Learner characteristic Teaching sequence, Presentation The learner did not work on the current unit and has specified no media preferences.... In PAGE 8: ... In Table 2 some examples for the rules implemented in the system and the resulting presentation can be seen. Table2 : Example modifications of the default teaching strategies depending on learner characteristics Learner characteristic Teaching sequence, Presentation The learner did not work on the current unit and has specified no media preferences. Default material sequences, no modifications.... In PAGE 19: ... Through a combination of different categories of sequencing algorithms specified by Frank [2] adaptive sequencing can be used in all three models of Salomon. Table2 gives an overview of adaptive sequencing algorithms used in ACE for different teaching goals. Adaptive sequencing can help to overcome knowledge deficits by adapting the complexity of learning material, compensate more general deficits through alternative learning sequences and adapt to individual preferences by selecting units or media.... ..."

"... In PAGE 3: ...Table1... In PAGE 4: ...Table1 . Also, each acquisition technique is associated to a certain source of information with its corresponding representation (Table 2).... In PAGE 4: ...each acquisition technique is associated to a certain source of information with its corresponding representation (Table 2). While specifying and refining the systematic presented in Table1 , we conducted three case studies. These helped us to experience in practice the need for a knowledge acquisition systematic within the DA context.... In PAGE 4: ... These directives allow the adaptation of the systematic regarding the phases, activities and techniques that should be used in a certain project . The domain analyst identifies the context of his specific project by analyzing each of the directives provided, establishing which phases and activities, as well as the corresponding techniques, from the knowledge acquisition process described in Table1 , will his knowledge acquisition process be composed of. Technique Sources Representation Protocol Analysis Existing systems Facets Scenarios Existing systems Refinement Itemized Cards LEL 2 Written references Domain Vocabulary Itemized Text Brainstorming Specialists Users Numbered Text Structured interviews Specialists Users Structured Text Delphi technique Specialists Users Previous Formatted Report Self-explanation Domain analyst Inferences and deductions Previous representations Table 2 .... ..."

"... In PAGE 16: ... The case description underscores how, in Anantapur district, the nature of communication underwent changes and transformation from the erstwhile instrumental mode to a stronger emphasis on commu- nicative action both in land/water development and use of technology therein. This is summarized in Table4 below. 6.... ..."

"... In PAGE 3: ... 4 Usage of the Information Object Design Pattern in KCOs The KCO is derived from the Information Object Design Pattern. It is divided into six quot;facets quot; which are semantically distinct components that refer to the actual content and the related domain specific meta data or knowledge ( Table1 ). Table 1.... ..."

"... In PAGE 5: ... Using the Collaboration Browser. queried, as summarised in Table1 , where the output of principal interest for a query is marked in boldface. These queries allow a user to ask about interfaces, collaborations and roles: Query about the interface of a class.... ..."

"... In PAGE 9: ...able 3-24 Interface getAccountRights ...........................................................................................54 Table4 -1 Adding semantic annotations to WSDL 1.1 service descriptionsError! Bookmark not defined.... In PAGE 9: ...1 service descriptionsError! Bookmark not defined. Table4 -2: Brief overview of the UDDI data model .... In PAGE 9: ...able 4-2: Brief overview of the UDDI data model ................................ Error! Bookmark not defined. Table4 -3: Overview of the Canonical tModels defined in (Colgrave et al, 2004)Error! Bookmark not defined. Table 4-4: Overview of additional Canonical tModels defined in our mapping methodology.... In PAGE 9: ...able 4-2: Brief overview of the UDDI data model ................................ Error! Bookmark not defined. Table 4-3: Overview of the Canonical tModels defined in (Colgrave et al, 2004)Error! Bookmark not defined. Table4 -4: Overview of additional Canonical tModels defined in our mapping methodology.... In PAGE 9: ...able 4-4: Overview of additional Canonical tModels defined in our mapping methodology..........Error! Bookmark not defined. Table4 -5: Mapping of WSDL 1.... In PAGE 9: ...able 4-5: Mapping of WSDL 1.1 entities and entity-related information in UDDI v2/v3................Error! Bookmark not defined. Table4 -6: Publication Manager - interfaces provided .... In PAGE 9: ...able 4-6: Publication Manager - interfaces provided ........................... Error! Bookmark not defined. Table4 -7: Discovery Manager - interfaces provided.... In PAGE 9: ...able 4-7: Discovery Manager - interfaces provided............................. Error! Bookmark not defined. Table4 -8: UDDI Server - interfaces provided to the Publication Manager moduleError! Bookmark not defined.... In PAGE 9: ...able 4-7: Discovery Manager - interfaces provided............................. Error! Bookmark not defined. Table 4-8: UDDI Server - interfaces provided to the Publication Manager moduleError! Bookmark not defined. Table4... In PAGE 64: ...0 documents as well. Table4 -1Error! Reference source not found. summarises the different type of semantics that can be captured by linking ontological concepts defined in the FUSION Ontology, through SAWSDL annotations, to WSDL 1.... In PAGE 64: ...1 entities in the WSDL interfaces of Enterprise Service mediators. Type of semantics FUSION Ontology Annotated WSDL entity SAWSDL extension attribute Functional semantics (used in discovery) Service Classification Taxonomy wsdl:portType sawsdl:modelReference Data semantics (used in discovery and mediation) Data facet wsdl:part, xs:complexType, or xs:element sawsdl:modelReference, sawsdl:loweringSchemaMapping sawsdl:liftingSchemaMapping Behavioural semantics (used in semi-automated composition) State ontology wsdl:operation sawsdl:modelReference Table4 -1 Adding semantic annotations to WSDL 1.1 service descriptions Since behavioural semantics are not intended to be used in the context of Web service discovery, but only in semi-automated service composition, the mapping methodology that is proposed in this specification considers only the case of functional and data semantics to be captured in UDDI.... In PAGE 67: ...xamine the mapping range, i.e. the UDDI data model. Table4 -2Error! Reference source not found. presents an overview of all entities in the UDDI v2 specification (UDDI, 2002), with an explanation of how they are utilised in the FUSION Semantic Registry.... In PAGE 68: ... They are used for representing: (i) wsdl:portType, wsdl:operation, or wsdl:binding entities, (ii) associations of wsdl:operations to FUSION Ontology Data Facet Entities (DFE) used as inputs, (iii) associations of wsdl:operations to FUSION Ontology Data Facet Entities (DFE) used as outputs, and (iv) association of a wsdl:portType to a FUSION Ontology Functional Facet Entity (FFE), to classify it for discovery. Table4... In PAGE 72: ...e. Table4 -3, lists the Canonical tModels defined in that OASIS Technical Note, along with a brief description on their intended purpose. Please note that the last one (WSDL Address) has not been adopted in our mapping methodology.... In PAGE 73: ...FUSION STREP- Project - No 027385 FUSION- Project FUSION Integration Mechanism STREP - Work package WP3 Document D3.1 Specifications of the Integration Mechanism Date 30 April 2007 FUSION-IST-63510: Business Process Fusion based on Semantically-enabled Service-Oriented Business Applications Strategic Objective: Strengthening the Integration of the ICT research effort in an Enlarged Europe Page 73 / 107 [uuid:ad61de98-4db8-31b2-a299-a2373dc97212] Table4 -3: Overview of the Canonical tModels defined in (Colgrave et al, 2004) An example usage of Canonical tModels to represent a binary relation among two WSDL entities, could be for specifying that a wsdl:operation is contained in a wsdl:portType. To achieve this, one would need to follow these steps: 1.... In PAGE 74: ... More specifically, to achieve a complete semantic categorisation of wsdl:portType and wsdl:operation entities, we need to cater for annotations intended to capture functional semantics, input data semantics, and output data semantics. To accommodate these requirements, we define the use of the following Canonical tModels ( Table4 -4), in addition to the ones listed in Table 4-3. New Canonical tModels Purpose WSDL Operation Reference tModel Used for specifying a relation among a tModel representing a WSDL entity, and another tModel representing a wsdl:operation entity [uuid:e0e06db0-0ebb-11dc-adb0-c68898adb764] Functional Semantics Categorisation Used for representing the notion of functional semantics... In PAGE 75: ...FUSION STREP- Project - No 027385 FUSION- Project FUSION Integration Mechanism STREP - Work package WP3 Document D3.1 Specifications of the Integration Mechanism Date 30 April 2007 FUSION-IST-63510: Business Process Fusion based on Semantically-enabled Service-Oriented Business Applications Strategic Objective: Strengthening the Integration of the ICT research effort in an Enlarged Europe Page 75 / 107 tModel [uuid:07275150-0ebc-11dc-9150-adc3500cd9dc] Input Semantics Categorisation tModel Used for representing the notion of input semantics categorisation with reference to some FUSION Ontology DFE [uuid:22c468d0-0ebc-11dc-a8d0-8edacb6ffb3e] Output Semantics Categorisation tModel Used for representing the notion of output semantics categorisation with reference to some FUSION Ontology DFE [uuid:37b8f120-0ebc-11dc-b120-cd432ecdaed9] Table4 -4: Overview of additional Canonical tModels defined in our mapping methodology Based on such an extended set of Canonical tModels, one could specify that a certain wsdl:portType (e.g.... In PAGE 76: ... ... lt;/categoryBag gt; lt;overviewDoc gt; lt;overviewURL gt;http://location/sample.wsdl lt;/overviewURL gt; lt;/overviewDoc gt; lt;/tModel gt; The two example tModels are also depicted in Figure 4-5, below: Figure 4-5: Example of semantic categorisation for a wsdl:portType and a wsdl:operation As a summary to all discussed so far, the following table ( Table4... In PAGE 78: ...FUSION STREP- Project - No 027385 FUSION- Project FUSION Integration Mechanism STREP - Work package WP3 Document D3.1 Specifications of the Integration Mechanism Date 30 April 2007 FUSION-IST-63510: Business Process Fusion based on Semantically-enabled Service-Oriented Business Applications Strategic Objective: Strengthening the Integration of the ICT research effort in an Enlarged Europe Page 78 / 107 wsdl:portType entity that the wsdl:binding imlplements of the tModel Type of WSDL entity keyedReference in the categoryBag of the tModel Target namespace keyedReference in the categoryBag of the tModel Local name Name of the tModel Location of WSDL file OverviewURL in the OverviewDoc of the tModel Functional Semantics Categorisation keyedReference in the categoryBag of the tModel wsdl:portType Contained wsdl:operation entities keyedReference(s) in the categoryBag of the tModel Type of WSDL entity keyedReference in the categoryBag of the tModel Target namespace keyedReference in the categoryBag of the tModel Local name Name of the tModel Location of WSDL file OverviewURL in the OverviewDoc of the tModel Input Semantics Categorisation keyedReference in the categoryBag of the tModel Output Semantics Categorisation keyedReference in the categoryBag of the tModel wsdl:operation Container portType entity keyedReference in the categoryBag of the tModel wsdl:message This entity does not need to be explicitly mapped wsdl:part This entity does not need to be explicitly mapped wsdl:types This entity does not need to be explicitly mapped Table4 -5: Mapping of WSDL 1.1 entities and entity-related information in UDDI v2/v3 4.... In PAGE 84: ...e. Table4 -6, summarises the interfaces that the Publication Manager module provides. The Publication Manager API is to be used for all write- operations on the Semantic Registry: creating, modifying, and deleting UDDI records representing service advertisements or host SOBA systems.... In PAGE 84: ... The UUID identifier of the service advertisement must be provided in the parameters list. Table4 -6: Publication Manager - interfaces provided 4.4.... In PAGE 84: ...4.2 Discovery Manager Interface Definition The table below, Table4 -7, summarises the interfaces that the Discovery manager module provides. The Discovery Manager API is to be used for three different types... In PAGE 86: ...e. Table4 -8, summarises the interfaces that the UDDI Server module provides to the Publication Manager and Discovery Manager modules of the Semantic Registry. These correspond to the standard Publish API and Inquiry API as specified in the UDDI specification ratified by OASIS.... In PAGE 87: ... There is no way to actually cause a tModel to be deleted, except by administrative petition. Table4 -8: UDDI Server - interfaces provided to the Publication Manager module The Publish API and Inquiry API functions of the UDDI Server (Table 4-9) are accessible through SOAP messages over HTTP. Therefore before making function- calls to the UDDI Server the Publication Manager and the Discovery Manager must create SOAP messages, using the appropriate structures as their body (e.... In PAGE 87: ... There is no way to actually cause a tModel to be deleted, except by administrative petition. Table 4-8: UDDI Server - interfaces provided to the Publication Manager module The Publish API and Inquiry API functions of the UDDI Server ( Table4 -9) are accessible through SOAP messages over HTTP. Therefore before making function- calls to the UDDI Server the Publication Manager and the Discovery Manager must create SOAP messages, using the appropriate structures as their body (e.... In PAGE 88: ... Returns a tModelDetail message. Table4 -9: UDDI Server - interfaces provided to the Discovery Manager module 4.5 Semantic Registry Implementation Guidelines To support the representation of syntactic properties and binary relations among WSDL entities in UDDI v2/v3, the mapping defined in (Colgrave et al, 2004) introduced a number of Canonical tModels that should be registered in a UDDI server installation before publication and discovery of WSDL documents could be enabled (i.... ..."