Please read in full to understand how typical and challenging is this schema. Most of them got failed and its your turn, Looks easy on first glance.
Here is the requirement:
1)A fixed set of elements will be there which will have different attributes.
2)Some of these elements will have enumerations.
3)This set will be used at different positions.
4)The enumeration values will be different at different places and some times these enumeration are disjoint sets.
Let us take an example to understand this:
A company has got different location representing houses, company wants’ to store this information on these and would like to have a schema for this
<Company name>
<head office>
<Address>
</Head office>
<BranchOne>
<Address>
</BranchOne>
<BranchTwo>
<Address>
</BranchTwo>
<Address>
<Street length =20 type =string>
<City length =20 type=string>
<State length =2 type=string>
<Zipcode length =5 type=int>
</Address>
</Company name>
Here are the constraint:
1)Head office will be in the state of “NY”
2)Branch office will be out of these states of “AZ, FL, OH” only within in these has to be checked.
3)Let us take Zip code for the branches should be out of these “12345, 23456, 34567”
4)Zip code for the head office can be of these “23456, 34567,45678”.
5)For head office we should not use “Street”.
How to represent this in the XML schema is the major
1)Only enumeration will be changing for most cases.
2)Only Street is removed for head office.
Note: Please don’t relate these with actual address and get not to go for logical conclusion on physical addresses, this is sample example taken for easy understand.
Actual schema will contain exact similar structure and conditions and it has more elements and more enumerations and more deleted elements while the set will be used many number of times in different places, In most of the cases element (here “Address”) is used exactly except few more enumeration values added to one of internal elements (Here any one of city, state, zip).
Thanks
Raju
Here is the requirement:
1)A fixed set of elements will be there which will have different attributes.
2)Some of these elements will have enumerations.
3)This set will be used at different positions.
4)The enumeration values will be different at different places and some times these enumeration are disjoint sets.
Let us take an example to understand this:
A company has got different location representing houses, company wants’ to store this information on these and would like to have a schema for this
<Company name>
<head office>
<Address>
</Head office>
<BranchOne>
<Address>
</BranchOne>
<BranchTwo>
<Address>
</BranchTwo>
<Address>
<Street length =20 type =string>
<City length =20 type=string>
<State length =2 type=string>
<Zipcode length =5 type=int>
</Address>
</Company name>
Here are the constraint:
1)Head office will be in the state of “NY”
2)Branch office will be out of these states of “AZ, FL, OH” only within in these has to be checked.
3)Let us take Zip code for the branches should be out of these “12345, 23456, 34567”
4)Zip code for the head office can be of these “23456, 34567,45678”.
5)For head office we should not use “Street”.
How to represent this in the XML schema is the major
1)Only enumeration will be changing for most cases.
2)Only Street is removed for head office.
Note: Please don’t relate these with actual address and get not to go for logical conclusion on physical addresses, this is sample example taken for easy understand.
Actual schema will contain exact similar structure and conditions and it has more elements and more enumerations and more deleted elements while the set will be used many number of times in different places, In most of the cases element (here “Address”) is used exactly except few more enumeration values added to one of internal elements (Here any one of city, state, zip).
Thanks
Raju