Thanks for the advice...this XSLT is giving me issues how do i create a table based on ,how should the table look .
<suitablejobs xsi:noNamespaceSchemaLocation="SuitableJobsfinal.xsd" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<company>
<companyname>
<companyname>String</companyname>
</companyname>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
</company>
<company>
<companyname>
<companyname>String</companyname>
</companyname>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
<jobdescription>
<jobtitle>String</jobtitle>
<salaryammount>0</salaryammount>
<details>String</details>
</jobdescription>
</company>
</suitablejobs>
On Fri, Mar 11, 2011 at 9:40 AM,
<ashok+skunkworks@parliaments.info> wrote:
On Thu, Mar 10, 2011 at 11:36 AM, ibtisam jamal <
ibty.jamal@gmail.com> wrote:
> 4. Create an extended job seeker XSD document, and XML sample, to include
> provision for the
> following additional information:
> • How far away the job seeker is willing to travel for a new job
> • Whether the job seeker drives (should be either yes or no)
this is a xs:boolean ... i.e. something like
<xs:element name="drive" type="xs:boolean" default="false" />
> • Current experience – this should be a list of positions that the user has
> had, including the
> position title, the address of the employment, and a list of
> responsibilities
this is a case for a complexType since its not just one piece of
information but an aggregation of different types :
lets start with the last one "responsibilities" -- thats a plural so
its composed of multiple "responsiblity"
so you first define responsibility :
<xs:element name="responsiblity" type="xs:string"/>
and then responsibilities :
<xs:element name="responsibilities">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="responsiblity"/>
</xs:sequence>
</xs:complexType>
</xs:element>
and aggregate that into experience :
<xs:complexType name="experience">
<xs:sequence>
<xs:element name="title" type="xs:string" />
<xs:element name="start-date" type="xs:date" />
<xs:element name="end-date" type="xs:date" />
<xs:element ref="responsibilities"/>
</xs:sequence>
</xs:complexType>
so the way you have to do it is to identify and define the structure
of the individual attributes in the following way (and order i would
say ):
- singularity (title, start-date, end-date, responsibility)
- plurality (responsiblities )
- and composities (experience = title, start-date, end-date,
responsibilities )
If you break down the whole problem statement into such groupings --
you can easily define the schema from there ...
> 5. Create an XSLT file to display the suitable jobs document as HTML in a
> web browser. The
> resulting output should deal with as many jobs as are returned, and be
> simple and clear to view
> (a table structure works best).
>
Start here :
<http://www.w3schools.com/xsl/>
<http://www.dpawson.co.uk/xsl/sect2/N7450.html>
but to do the XSLT you will need to first define the schema and then
create some xml documents out of that schema ...