-- XSD schema extracted from ITU-T J.177 (11/2005)

<?xml version="1.0" encoding="UTF-8"?>
<!--
	An example illustrating how to extend a Pcsp object.
	This example extends  the PcspService object with additional 
	fields and call features.
	
	See details below.
-->
<PcspService xmlns="http://www.cablelabs.com/Pcsp/I01/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:pcsp="http://www.cablelabs.com/Pcsp/I01/schema">
	<!--
		The main body of the Service object is filled with sample data that will
		allow the object to validate.
	-->
	<ServiceId>5551212</ServiceId>
	<AdminStatus>0</AdminStatus>
	<BillingId>5551212</BillingId>
	<ExternalId>5551212</ExternalId>
	<IsPrimary>true</IsPrimary>
	<PrimaryRing/>
	<DisplayName/>
	<DisplayNumber/>
	<Password/>
	<Announcements>
		<Language>EN</Language>
		<Timezone>+0500</Timezone>
	</Announcements>
	<InterExchange>
		<PIC>0</PIC>
		<LPIC>0</LPIC>
		<IPIC>0</IPIC>
	</InterExchange>
	<LNP>
		<PortingStatus>1</PortingStatus>
		<LNPT>true</LNPT>
	</LNP>
	<!--
		A Service object can be extended in two locations:
			1. The main body of the object.
			2. The call feature list.
			
		Here we extend the set of call features with the CfXYZ call feature.
		
		1. The VendorExt element must specify a valid namespace for the extension's schema. This allows the parsing system to locate the schema file for the extension.
		2. Any content within the VendorExt element must be namespace qualified, enabling validation against the extension's schema.
	-->
	<ListOfCallFeatures>
		<Extension xmlns:ext="http://www.cablelabs.com/SampleExtension">
			<ext:CfXYZ>
				<ext:Subscribed>true</ext:Subscribed>
				<ext:Enabled>true</ext:Enabled>
			</ext:CfXYZ>
		</Extension>
	</ListOfCallFeatures>
	<!--
		Here, we extend the data content of main body of the Service object.
	-->
	<Extension xmlns:ext="http://www.cablelabs.com/SampleExtension">
		<ext:A>Sample extension A</ext:A>
		<ext:B>Sample extension B</ext:B>
		<ext:C>Sample extension C</ext:C>
	</Extension>
</PcspService>