Module 2: Examining Web Storage System Schema Contents Overview Schema Function Schema Structure Creating a Custom Schema 11 Lab A: Extending the Web Storage System Schema 19 Review 25 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2000 Microsoft Corporation All rights reserved Microsoft, Active Directory, ActiveX, FrontPage, Hotmail, JScript, MSN, Outlook, PowerPoint, Visual Basic, Visual C++, Window Media, Visual InterDev, Visual Studio, Win32, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries Other product and company names mentioned herein may be the trademarks of their respective owners Project Lead: Samantha Smith Instructional Designers: Sangeeta Garg (NIIT (USA) Inc.), Marilyn McCune Instructional Software Design Engineer: William Rebozo Subject Matter Experts: Jayme Bowers (ECMS Inc.), John Christian (ECMS Inc.), Robert Ginsburg (ECMS Inc.), Frederick Volking (ECMS Inc Technical Contributors: Thomas Rizzo, Brent Ingraham, Navin Kachroo, Robert Brown, Alex Hopmann, Jim Reitz Graphic Artist: Kirsten Larson (S&T Consulting) Editing Manager: Lynette Skinner Editors: Kelly Baker, Nancy Finch Copy Editor: Ed McKillop (S&T Consulting) Production Manager: Miracle Davis Print Coordinator: Marlene Lambert (Online Training Solutions Inc.) Online Production Coordinator: Jenny Boe Test Manager: Eric R Myers Creative Director, Media/Sim Services: David Mahlmann Web Development Lead: Lisa Pease CD Build Specialist: Eric Wagoner Localization Manager: Rick Terek Operations Coordinator: John Williams Manufacturing Support: Laura King; Kathy Hershey Lead Product Manager, Release Management: Bo Galford Program Manager, Knowledge Management: Josh Barnhill Lead Product Manager, Knowledge Management: Janet Wilson Group Manager, Courseware Infrastructure: David Bramble Director, Developer Training: Juan Fernando Rivera General Manager: Robert Stewart Module 2: Examining Web Storage System Schema iii Instructor Notes Presentation: 45 Minutes Lab: 20 Minutes This module provides students with an introduction to Microsoft® Web Storage System schema and explains how the schema promotes interoperability and reuse by using its properties, namespaces, and content classes Creating custom schemas is also covered Module lecture content and learning objectives are reinforced by a hands-on lab, Lab A, Extending the Web Storage System Schema After completing this module, students will be able to: ! Describe how schema properties, namespaces, and content classes function to define Web Storage System schema ! Create a custom schema Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module Required Materials To teach this module, you need the following materials: ! Microsoft PowerPoint® file 2019A_02.ppt ! Module 2, “Examining Web Storage System Schema” ! Web Storage System Explorer tool is required for the "Using the Web Storage System Explorer" demonstration Preparation Tasks To prepare for this module, you should: ! Read all of the materials for this module ! Complete the lab ! Read the topics in the Exchange 2000 software development kit (SDK) that discuss Web Storage System schema iv Module 2: Examining Web Storage System Schema Discussion This section provides discussion notes that will not fit in the margin notes or are not appropriate for the student notes Discussion: Default Properties and Namespaces The objective of this instructor-led group discussion is to introduce the students to some of the more common default properties and namespaces that are available in Web Storage System schema The goal is to present how the properties are used in different circumstances You not need to discuss in detail how to implement these properties; just give an overview of property function Begin by defining the properties in the "DAV:" namespace Mention that the values for many of the properties in the "DAV:" namespace not have to be set explicitly because they are automatically assigned values by the Web Storage System Discuss how the properties of the "DAV:" namespace are defined by Internet standards organizations to promote interoperability between applications and platforms Define the "http://schemas.microsoft.com/exchange" namespace as a set of properties implemented by Microsoft Exchange 2000 Server Note that these properties can have predefined programming enumerations associated with them that you can use when you set the value For example, the http://schemas.microsoft.com/exchange/sensitivity properties can be represented by the CdoSensitivityValues Collaboration Data Objects (CDO) enumeration Ask for an example of a registered domain name used by a student’s company, and create some examples of property names such as http://schemas/domainname/propertyname When discussing the "urn:schemas:calendar", "urn:schemas:contacts", "urn:schemas:httpmail", and "urn:schemas:mailheader" namespaces, discuss how the properties are defined by Internet standards organizations Discuss the difference between the "urn:schemas:httpmail" and the "urn:schemas:mailheader" namespaces The properties for the “urn:schemas:httpmail” namespace are expressed as Unicode characters and the properties for the “urn:schemas:mailheader” namespace are expressed as ASCII characters When discussing the "http://schemas.microsoft.com/exchange/events/" and "urn:schemas-microsoft-com:office:forms" namespaces, define event registrations and Web form registrations Explain how to use these properties to create a decision table Mention that you will be going into greater detail about how to use the properties in these namespaces in later sections When discussing the "urn:schemas-microsoft-com:xml-data", "urn:schemasmicrosoft-com:datatypes" and "urn:schemas-microsoft-com:exch-data" namespaces, explain how to use them to create custom properties Mention that you will be going into greater detail about how to use the properties in these namespaces in later sections Module 2: Examining Web Storage System Schema When discussing the "http://schemas.microsoft.com/exchange/security/" namespace, explain how it uses Extensible Markup Language (XML) to establish role-based security on an item or folder level (Read the article at http://www.msdn.microsoft.com/library /default.asp?URL=/library/techart/secroles.htm) v vi Module 2: Examining Web Storage System Schema Demonstration This section provides demonstration procedures that will not fit in the margin notes or are not appropriate for the student notes Demonstration: Using the Web Storage System Explorer ! Prepare for the demonstration by completing the following steps: Start Exchange System Manager Create a new public folder in the Public Folders tree and name it ExpenseReport Create another public folder in the Public Folders tree and name it ExpenseReportSchema Open the Web Storage System Explorer tool Type the username, password, and the URL of the ExpenseReportSchema folder as http://localhost/public/expensereportschema Select the baseschema property and set it equal to the non_ipm_subtree/schema location For example, set it to http://localhost/public/non_ipm_subtree/schema/ Create a new property definition, and give it a unique name using a namespace, such as http://schemas/domainname/expensereport/state Save the property definition as State Set the data type to String and specify that the property is indexed Create a new content class and give it a unique name using a namespace such as http://schemas/domainname/expensereport/ Save the content class as Expensereport Using the Web Storage System Explorer, specify that your new content class extends the urn:content-classes:item content class 10 Add the custom property you created, http://schemas/domainname /expensereport/state/, to the content class, and then save your changes 11 Using the Web Storage System Explorer, open the ExpenseReport folder that you created earlier 12 Set the schema-collection-ref property equal to the URL of the schema folder you created earlier, http://localhost/public/ExpenseReportSchema 13 Explain the results of what you just did You created a schema folder and set its baseschema property to the non_ipm_subtree/schema directory so that you can use all the existing properties of the Web Storage System You created a new property and used a namespace to differentiate it from other properties You created a custom content class that extends the urn:content-classes:item content class and uses the custom property that you created earlier Module 2: Examining Web Storage System Schema vii Module Strategy Use the following strategy to present this module: ! Schema Function Define the terms schema, and schema-aware application Present Web Storage System schema as a flexible operating environment for storing, sorting, searching, and indexing resources ! Schema Structure Describe how properties and namespaces function in the Web Storage System and emphasize that each collection of properties defines a namespace List the set of default namespaces used by the Web Storage System to define resources Present the function of content class Explain how to read and set the content class of a resource by using the DAV:contentclass schema property List the predefined content classes provided by Exchange 2000 Use the example of an expensereport content class to explain how to extend a schema ! Creating a Custom Schema Use the example of an expense report to explain how to create a custom schema by appending a property and how to create a custom content class Define schema scope Present the two folder properties that are used to configure folder schema scope Describe the procedures for creating a schema, property definitions, and content class definitions Module 2: Examining Web Storage System Schema Overview Topic Objective To provide an overview of the module topics and objectives ! Schema Function Lead-in ! Schema Structure ! Creating a Custom Schema The Web Storage System schema platform allows applications to share data Microsoft® Web Storage System schema provides a flexible operating environment for storing, sorting, searching, and indexing resources in the Web Storage System After completing this module, you will be able to: ! Describe the function of schema ! Describe how properties, namespaces, and content classes function to define Web Storage System schema ! Create a custom schema Module 2: Examining Web Storage System Schema Schema Function Topic Objective To present the function of a Web Storage System schema Lead-in Schemas enable schemaaware applications to interpret the properties of a resource maintained by the Web Storage System Mechanism for Schema-Aware Applications to Discover the Properties That are Used by Resources in the Web Storage System A schema is a collection of properties that define all the resources, such as folders, items, and Web files, found in the Web Storage System Schema structure is not as rigidly enforced in the Web Storage System as it is in a relational database system, such as Microsoft SQL Server™ Instead, a schema in the Web Storage System is used primarily to provide a mechanism for schema-aware applications to interpret the properties that are used by a resource in a particular application A schema-aware application is an application that can access and modify the schema properties associated with resources to sort, query, and index resources in the Web Storage System Note The properties that can be applied to resources in the Web Storage System are interpreted by using multiple application programming interfaces (APIs) and protocols, such as OLE DB, MAPI and Hypertext Transfer Protocol (HTTP) Microsoft Outlook® 2000 uses MAPI to communicate with resource properties in Microsoft Exchange 2000 Server 12 Module 2: Examining Web Storage System Schema Scenario for Creating a Custom Schema Topic Objective To show examples of using predefined properties to describe an expense report The slide also shows an example of extending a predefined content class and adding additional properties to describe an expense report Lead-in When using a schema to define resources, you can use existing properties or create your own urn:content-classes:item An Instance of an Expense Report DAV:href DAV:href = “http://server/public/expsereports/expensereopt1” DAV:creationdate DAV:creationdate = 6/22/2000 2:47:24 AM urn:schemas:httpmail:expiry-date urn:schemas:httpmail:expiry-date = 10/20/2000 2:47:24 AM urn:schemas:person:email1 = “paulwest@contoso.msft“ http://schemas/contoso.msft /expensereport An Instance of an Expense Report DAV:href DAV:href = “http://server/public/expsereports/expensereopt1” DAV:creationdate DAV:creationdate = 6/22/2000 2:47:24 AM urn:schemas:httpmail:expiry-date urn:schemas:httpmail:expiry-date = 10/20/2000 2:47:24 AM http://schemas/contoso.msft/ expensereport/total http://schemas/contoso.msft/expensereport/ total = $500 http://schemas/contoso.msft/ expensereport/state http://schemas/contoso.msft/expensereport/ state = “approved” Most of the properties and content classes that exist in the Web Storage System schema provide the data types required to build custom applications For example, you can build an expense report application that uses all the properties of the urn:content-classes:item content class Creating a Custom Schema by Extending an Existing Content Class You can easily append properties to your expense report that not exist in the urn:content-classes:item content class For example, suppose the expense report application assigns an accountant to instances of expense reports by appending the accountant’s e-mail address This is accomplished by appending the urn:schemas::person:email1 property to an instance of an expense report Creating a Custom Schema by Creating a New Content Class You can also create a custom content class that includes all of the properties required by expense reports in your application After you create the custom content class, you can create a new content class called http://schemas/yourdomainname/expensereport that extends the urn:content-classes:item content class You can create a numeric property that identifies the total of the expense report and call it http://schemas/yourdomainname/expensereport/total; or you can create an indexed string property that determines the state of an expense report such as open, closed, or blocked You can call that http://schemas/yourdomainname/expensereport/state/ Module 2: Examining Web Storage System Schema 13 Associating a Schema with an Application Topic Objective To show how to associate schema information with an application folder Application Folder Lead-in Use either the urn:schemas-microsoftcom:exch-data:schemacollection-ref property or the urn:schemasmicrosoft-com:exchdata: baseschema property to configure schema scope Schema-collection-ref Schema-collection-ref Schema Folder A baseschema baseschema Schema Folder B baseschema baseschema Schema Folder C baseschema baseschema non_ipm_sub tree/schema The application folder, which contains the resources for which you created property definitions, must be able to locate its schema folder A schema folder contains definitions for all the properties an application uses to describe resources To enable the application folder to locate the schema folder, you must associate the schema with the application For example, suppose you create an expense report folder where users can post expense reports to a public folder Create a custom content class called expensereport Choose a folder in which to store your schema information You can store this in the same folder as your application data, but it is recommended that you use a separate subfolder Note If your application does not require any custom property definitions, you can use the default Web Storage System properties located in the Foldertree/non_ipm_subtree/schema folder for the store Each store you create has a copy of this folder Defining a Schema Scope A schema scope is defined as the set of folders, identified by a Uniform Resource Identifier (URI), which is traversed when searching for schema definition items You must configure your application folder's schema scope so that it includes your schema definition items 14 Module 2: Examining Web Storage System Schema Configuring a Folder’s Schema Scope You can configure a folder's schema scope by using two folder properties: To avoid confusion between the property names in the illustration and these property names, explain how the workbook uses the full property name, while the illustration uses a short version of the name to conserve space ! urn:schemas-microsoft-com:exch-data:schema-collection-ref This single-valued property, which you can set on any folder, specifies the URL that points to the first folder that contains applicable schema definition items If this property is empty, the default location is the non_ipm_subtree/schema folder of the public or private store To create your own schema definition items and apply them to items in your application folders, set this property on each of your application folders The schema scope for any folder always starts with a single folder in the store You can further expand the scope by setting the urn:schemasmicrosoft-com:exch-data:baseschema field on the first and subsequent schema folders Normally, applications terminate the schema scope with the non_ipm_subtree/schema folder, which contains the global Web Storage System schema definition items ! urn:schemas-microsoft-com:exch-data:baseschema This multi-valued field, which you can set on any folder, specifies the URLs for folders that contain additional, or base, schema definition items When an application constructs the list of folders that are in a particular folder's schema scope, each folder—identified by this property—is added to the list in the order in which it appears in this field Note that, by convention, you set this field for designated application schema folders and not for the application folder itself The order in which folders are searched is significant: if two or more definition items exist that have the same name set in the definition item's urn:schemas-microsoft-com:xml-data#name property, only the first definition is used Module 2: Examining Web Storage System Schema 15 Creating a Schema Topic Objective To present the steps to complete for creating schema for an application Lead-in There are four steps involved in creating schema Create a schema folder in which to store your custom properties and content classes Create schema definition items by creating the property definitions and the content class definitions Configure the schema-collection-ref property of your application folders to map to your custom schema folder Configure the baseschema property of your custom schema folder to map to the non_ipm_subtree/schema folder To create the schema definition, you create the property and the content class definitions After you define a location to store your custom schema information, you are ready to create properties and content classes There are visual tools to enable this or you can write code to create these items Regardless of the method you use, the steps and properties you use remain the same To create schemas for your application: Create a schema folder in which to store your custom properties and content classes Create schema definition items by creating the property definitions and the content class definitions These definitions store the metadata of the item you are defining For example, for an expense report tracking application you create a content class called expensereport that extends the urn:content-classes:item content class You then create custom properties and associate them with your content class Configure the urn:schemas-microsoft-com:exch-data: schema-collection-ref property of your application folders to map to your custom schema folder Configure the urn:schemas-microsoft-com:exch-data:baseschema property of your custom schema folder to map to the non_ipm_subtree/schema folder so your application can access all the Exchange 2000 schema information 16 Module 2: Examining Web Storage System Schema Defining a Custom Property Topic Objective To present the steps involved in defining a custom property Lead-in Four steps are involved in defining a custom property Create an item in a schema folder Set the item's DAV:contentclass to the value "urn:content-classes:propertydef" Set the name of the property by using the urn:schemas3 microsoft-com:xml-data#name property for the item Set the property's data type by using the urn:schemas4 microsoft-com:datatypes#type field You can define a custom property by configuring properties on a resource that indicate the name, data type, default value, and other characteristics of a property To create a property definition, perform the following steps: Create an item in a schema folder Set the item's DAV:contentclass to the value "urn:contentclasses:propertydef" This identifies the item as a property definition Set the name of the property by using the urn:schemas-microsoft-com: xml-data#name property for the item Use this name to refer to the property definition Note that this name is not the URL for the item For example, a property definition located at the URL http://server/public/myapplication/schema/property1 may have the name "http://domainname/myapplication/schema/property1" This name is used to refer to the property in applicable item fields Set the property's data type by using the urn:schemas-microsoft-com: datatypes#type field Define characteristics of the property, such as its default value (urn:schemasmicrosoft-com:exch-data:default) and whether the property is multi-valued (urn:schemas-microsoft-com:exch-data:ismultivalued), or if a value is required for the property (urn:schemas-microsoft-com:exchdata:isrequired) Module 2: Examining Web Storage System Schema 17 Defining a Custom Content Class Topic Objective To present the steps involved in defining a custom content class Lead-in There are four steps involved in defining a custom content class 1 Create a new item in the schema folder and set the item's DAV:contentclass field to the value urn:contentclasses:contentclassdef 2 Set the content class's name using the urn:schemasmicrosoft-com:xml-data#name property for the item Prefix the content class with a unique name Extend other content classes by setting the urn:schemas3 microsoft-com:xml-data#extends property for the item Specify the names of property definitions to associate with the content class You can define a custom content class by configuring properties that define the name, the properties associated with a content class, and whether or not the property extends to other content classes To create a content class definition item, perform the following steps: Create a new item in the schema folder and set the item's DAV:contentclass field to the value urn:content-classes:contentclassdef This identifies the item as a content class definition Set the content class's name using the urn:schemas-microsoft-com:xmldata#name property for the item Prefix the content class with a unique name, such as your domain name, to avoid name conflict Extend other content classes by setting the urn:schemas-microsoftcom:xml-data#extends property for the item This property is an array of strings, in which each string is the name of a content class as designated by the urn:schemas-microsoft-com:xmldata#name field of the class When you extend other content class definition items, your class inherits the property definitions set for each of these classes For example, you would use this property to extend the urn:content-classes:person content class to the patient content class you are creating Specify the names of property definitions to associate with the content class If this class extends others, you not need to specify property names for those classes; they are inherited To specify the names of property definitions, set the urn:schemas-microsoft-com:xml-data#element property for the item This property is an array of strings, in which each string is the name of a property definition in the schema scope 18 Module 2: Examining Web Storage System Schema Demonstration: Using the Web Storage System Explorer Topic Objective To demonstrate how to create custom properties and content classes Lead-in This demonstration will show you how to use the Web Storage System Explorer to create custom properties and custom classes, to associate custom properties and content classes with an application folder, and to access the default properties used by Exchange 2000 This demonstration shows you how to use the Web Storage System Explorer to create custom properties and custom content classes, to associate custom properties and content classes with an application folder, and to access the default properties used by Exchange 2000 in the non_ipm_subtree/schema/ folder of a particular store Module 2: Examining Web Storage System Schema 19 Lab A: Extending the Web Storage System Schema Topic Objective To introduce the lab Lead-in In this lab, you will explore the content classes and schema in the Web Storage System and also create and manage content classes and schema Explain the lab objectives Objectives After completing this lab, you will be able to: ! Explore the content classes and schema in the Web Storage System by using ActiveX® Data Objects (ADO), Collaboration Data Objects (CDO) for Exchange, Web Distributed Authoring Version (WebDAV), MAPI and CDO version 1.2.1, and Outlook Object Model ! Create and manage content classes and schema stored in the Web Storage System Prerequisites Before working on this lab, you must have: ! An understanding of the functionality of Web Storage System in Exchange 2000 ! An understanding of Web Storage System content classes and schema ! Experience using Microsoft Visual Basic® 6.0 Scenario This lab uses a Visual Basic application, named Exchange 2000 Explorer (ExExplore), which was developed specifically for you to use as a learning aid This utility is a working example of the various techniques that you can use to expose and manipulate content stored in the Web Storage System in Exchange 2000 Although all source code has been provided, many of the routines in ExExplore have little or no error checking capabilities This was done intentionally to focus on process rather than the application You are not prevented from making errors when using this utility, and error conditions can cause the utility to fail Estimated time to complete this lab: 20 minutes 20 Module 2: Examining Web Storage System Schema Exercise Exploring Content Classes using CDO, ADO, MAPI, WebDAV, and XML In this lab, you will learn various techniques to access Web Storage System content classes and schema ! Start ExExplore Click Start, point to Programs, point to Microsoft Visual Studio 6.0, and then click Microsoft Visual Basic 6.0 In the New Project dialog box, click the Existing tab Open C:\Msdntrain\2019a\ExExplore\ExExplore.vbp If you are prompted to add the project to SourceSafe, click No Press F5 to compile and start ExExplore ! Access Web Storage System data by using MAPI and CDO 1.21 In the Exchange 2000 Explorer window, type the following information in the appropriate fields: Into field You type Server Name StudentXX (where XX is the number of your computer, such as Student01) User Name Administrator Password password Confirm password Click MAPI/CDO-1.21, and then click Browse The MAPI and CDO 1.21 window opens In the InfoStores/Folders pane, expand Public Folders, expand All Public Folders, and then click MyFolder Note that the MyFolder properties appear in the Folder properties pane In the Messages / HiddenMessages pane, expand Messages, and then click Hello World Notice that the Hello World message properties appear in the Message properties pane Close the MAPI and CDO 1.21 window Module 2: Examining Web Storage System Schema 21 ! Access Web Storage using ADO and CDO for Exchange In the Exchange 2000 Explorer window, click ADO / CDO-3, and then click Browse The ADO 2.5 / CDO 3.0 for Exchange window opens Note This window differs slightly from the MAPI and CDO 1.21 window Both windows are capable of essentially the same functionality; this window has additional functionality not available in the MAPI and CDO 1.21 window In the InfoStores / Folders pane, expand Public Folders, and then click MyFolder In the Items pane, expand Messages, and then click Hello Team.eml In the ADO/CDO Properties pane, expand CDO 3.0 Click the Subject property What is the Property Value displayed in the lower text box? _ Hello Team In the ADO/CDO Properties pane, expand ADO 2.5 Click the urn:schemas:mailheader:subject property You may have to scroll down to find the property What is the property value of urn:schemas:mailheader:subject? _ Hello Team What are the differences between the ADO and the CDO property name constructions? _ _ _ When using CDO, the property name of the subject of the message is Subject, and in ADO, the property name is urn:schemas:mailheader:subject However, both protocols are retrieving the same property from the Web Storage System Close the ADO 2.5 / CDO 3.0 for Exchange window 22 Module 2: Examining Web Storage System Schema ! Access Web Storage System data using WebDAV In the Exchange 2000 Explorer window, click the WebDAV option button, and then click Browse The WebDAV window opens In the InfoStores / Folders pane, expand Public Folders, and then click MyFolder In the Messages/HiddenMessages pane, expand Messages Click Hello Team / urn:content-classes:message In the Properties pane, expand DAV:propstat, and then expand DAV:prop Select the urn:schemas:mailheader:subject property Notice the difference in name construction between WebDAV, ADO, and CDO Click Schema An Internet Explorer window opens and displays the schema of Hello Team as expressed as XML Notice that there are numerous xmlns (xml namespaces) used to describe the schema for this item Close the Internet Explorer window ! Examine all properties expressed in XML Click XML An Internet Explorer window opens displaying all properties of the Hello Team item expressed as XML On the Edit menu of Internet Explorer, click Find (on This Page) The Find dialog box appears In the Find what text box, type subject Click Find Next Make note of the xmlns (xml namespace) prefix _ d: Click the Find Next button repeatedly Where else does Subject appear? Make note of the xmlns prefix for every occurrence _ e: Close the Find dialog box Scroll to the beginning of the file Locate the corresponding xmlns prefix assignment (d: and e:) Module 2: Examining Web Storage System Schema 23 Construct the entire name for each xmlns occurrence you found Example: xmlns:d="urn:schemas:mailheader: Test Message 2 Result: urn:schemas:mailheader:subject _ _ urn:schemas:mailheader:subject urn:schemas:httpmail:subject 10 Close the Internet Explorer window 11 In Properties pane of the WebDAV window, locate each instance of the name you constructed above Did you find the identical property each time in ADO, CDO, and WebDAV? _ _ ADO and WebDAV naming conventions are almost identical CDO uses a different convention 12 Click Schema Can you locate a schema item for each occurrence you found? _ _ Yes, because you are viewing the WebDAV protocol, which matches the naming convention that you constructed 13 Close the Internet Explorer window 14 Close the WebDav window 24 Module 2: Examining Web Storage System Schema Exercise Creating a Customized Content Class In this lab, you will use the ExExplore application to manipulate Web Storage System content classes and schema ! Add a Web Storage System property using WebDAV In the Exchange 2000 Explorer window, click the WebDAV option button, and then click Browse The WebDAV window opens In the InfoStores/Folders pane, expand Public Folders, and then click MyFolder In the Messages / HiddenMessages pane, expand Messages, then select Hello Team / urn:content-classes:message In the Properties pane, expand DAV:propstat, and then expand DAV:prop Click AddProp In the Please enter a Property name dialog box, type archivedby and then click OK Note Note that archivedby should be lower case with no spaces In the Please enter a starting value dialog box, type your name and then click OK In the InfoStores / Folders pane, expand Public Folders, and then click MyFolder In the Messages / HiddenMessages pane, expand Messages, then click Hello Team 10 In the Properties pane, expand DAV:propstat, and then expand DAV:prop 11 Locate the new property The new property will resemble urn:domainXX-msft:archivedby, where XX is the number of your domain 12 Select the new property Your name appears 13 Close the WebDAV window 14 Quit Visual Basic 15 If prompted to save changes to ExExplore, click No Module 2: Examining Web Storage System Schema 25 Review Slide Topic To reinforce module objectives by reviewing key points ! Schema Function Lead-in ! Schema Structure ! Creating a Custom Schema The review questions cover the key concepts taught in the module Is the following statement true or false: A content class can only be composed of properties from a single namespace? False, because a content class can be composed of properties that reside in multiple namespaces Which property you modify to determine where a folder gets its schema information from? The URN-schemas-microsoft-com:exch-data:schema-collection-ref property What must you to enable an application folder to locate the schema folder? Associate the schema with the application THIS PAGE INTENTIONALLY LEFT BLANK ... Storage System schema ! Create a custom schema 2 Module 2: Examining Web Storage System Schema Schema Function Topic Objective To present the function of a Web Storage System schema Lead-in Schemas... created earlier Module 2: Examining Web Storage System Schema vii Module Strategy Use the following strategy to present this module: ! Schema Function Define the terms schema, and schema- aware application... PowerPoint® file 2019A_02.ppt ! Module 2, ? ?Examining Web Storage System Schema? ?? ! Web Storage System Explorer tool is required for the "Using the Web Storage System Explorer" demonstration Preparation