Note:  This resume {next blog entry} was created in October 2007. I may or may not have a later version written. Please contact me if you want a newer resume or want a version in Word 2003 or Word 2007.

I am mainly looking for a full-time senior-level (or upper mid-level) position, or a very high paying contract ($50/hour+ in Louisville, $110/hour+ in New York City area, $85/hour+ elsewhere); position must have health-care benefits.

Note to employment agents: I will not work with agents who pronounce Louisville with four syllables - if you get the name of my city so wrong, I wonder what else about the position you may have wrong. Unless the position is international, I will not work with agents who are not in the United States. I would be willing to work internationally, but I would require "sponsorship" and would need to get a passport.

I would be available to start work immediately.

For personal reasons, I would not be able to take positions with alcohol, gambling, or tobacco corporations.

NOTE: Suggestions on improving my resume would be greatly appreciated. 

 

During my (hopefully) brief period of unemployment, I am studying for the 70-632 Exam (TS: Microsoft Office Project 2007, Managing Projects). I shall be publishing my study notes in the hopes that someone who is a project manager who uses these notes will hire me.

One thing I try to do for each exam is develop a glossary of terms. I print these off and peruse them during my down-times. Hopefully they will help you as well.

Here is a partial glossary taken from the help files for Microsoft Office Project Standard 2007 (split due to Spaces policy of not allowing large blogs for some reason).

actual: Information that shows what has actually occurred. For example, the actual start date for a task is the day that the task actually started.

actual cost: The cost that has actually been incurred to date for a task, resource, or assignment. For example, if the only resource assigned to a task gets paid $20 per hour and has worked for two hours, the actual cost to date for the task is $40.

ACWP [actual cost of work performed]: Shows actual costs incurred for work already performed by a resource on a task, up to the project status date or today's date.

actual duration: The amount of time a task has been in progress. When you enter the actual duration of a task, Project uses this value to calculate the remaining duration according to the formula Remaining Duration = Duration - Actual Duration.

actual work: The amount of work that has been performed on a task or assignment. When you enter actual work on a task, the remaining work is calculated using this formula: Remaining Work = Work - Actual Work. Actual work is often referred to as "actuals."

administrative closure: The process of documenting and archiving a project in a timely manner, as well as formally accepting the project's product and lessons learned.

administrator: Sets up and manages user accounts, assigns permissions, and helps users with network or server access issues. This person can also manage and customize various elements in Project Professional and in Project Server.

agile project management: A project management method that uses short iterations of up to four weeks, adaptive strategies, and collaboration among team members. Types of agile project management include Scrum, Critical Chain, and Extreme Programming.

assignment: A specific resource that is assigned to a particular task.

assignment units: The percentage of a work resource's time, or units, that the resource is assigned to a task.

authentication: The process of identifying a specific user and confirming that the user has permission to access Project Server.

AutoFilter: A way to filter information in a field [column]. By default, AutoFilters are off, but you can turn them on by clicking AutoFilter. Selecting a filter does not delete any information from your project; it only filters it from your view.

availability: Indicates when and how much of a resource's time can be scheduled for assigned work. Availability is determined by project and resource calendars, resource start and finish dates, or the level at which the resource is available for work.

base calendar: A calendar that can be used as a project and task calendar that specifies default working and nonworking time for a set of resources. Differs from a resource calendar, which specifies working and nonworking time for an individual resource.

baseline cost: The original project, resource, and assignment cost as shown in the baseline plan. The baseline cost is a snapshot of the cost at the time when the baseline plan was saved.

baseline plan: The original project plans [up to 11 per project] used to track progress on a project. The baseline plan is a snapshot of your schedule at the time that you save the baseline and includes information about tasks, resources, and assignments.

browser: A program that interprets the HTML delivered from Web servers, formats it, and displays it to the user.

budget: The estimated cost of a project that you establish in Project with your baseline plan.

BCWP [budgeted cost of work performed]: The earned value field that indicates how much of the task's budget should have been spent, given the actual duration of the task. Note that Project calculates BCWP at the task level differently than at the assignment level.

BCWS [budgeted cost of work scheduled]: The earned value field that shows how much of the budget should have been spent, in view of the baseline cost of the task, assignment, or resource. BCWS is calculated as the cumulative timephased baseline costs up to the status date or today's date.

buffer: Additional time added to a task's or project's scheduled duration that accounts for possible increases in the actual time required to complete the task or project.

calendar: The scheduling mechanism that determines working time for resources and tasks. Project uses four types of calendars: the base calendar, project calendar, resource calendar, and task calendar.

calendar view: A Project view that displays a project's tasks in a calendar format.

chart: A view or part of a view that represents project information graphically. For example, the Gantt Chart view consists of a sheet and a chart pane where tasks are represented as horizontal bars.

check out: The process of opening an enterprise project or an enterprise resource's record for editing.

combination view: A view containing two views. The bottom pane view shows detailed information about the tasks or resources in the top pane view. For example, the Gantt Chart view could be in the top pane and the Task Form view in the bottom pane.

consolidated project: A project containing one or more inserted projects [also known as subprojects]. These can retain links to their source projects and may be linked to one another. A consolidated project is also called a master project.

constraint: A restriction set on the start or finish date of a task. You can specify that a task must start on or finish no later than a particular date. Constraints can be flexible [not tied to a specific date] or inflexible [tied to a specific date].

contingency plan: A plan that identifies corrective steps to take if a risk event occurs.

contour: The shape of how scheduled work for an assignment is distributed across time. Use a contour to control how Project schedules the work of a resource. Contour examples include flat, back-loaded, front-loaded, bell, turtle, and more.

contract closeout: The completion of the contract [such as fixed price or lump sum, cost reimbursable, unit price contracts]. Closeout includes resolving all outstanding issues and items, such as inspections or invoices.

cost: The total scheduled cost for a task, resource, or assignment, or for an entire project. This is sometimes referred to as the current cost. In Project, baseline costs are usually referred to as "budget."

cost resources: Resources that don't depend on the amount of work on a task or the duration of a task, such as airfare or lodging.

CV [cost variances]: The difference between the budgeted cost of work performed [BCWP] on a task and the actual cost of work performed [ACWP]. If the CV is positive, the cost is currently under the budgeted amount; if the CV is negative, the task is currently over budget.

criteria: In a filter, the instructions that specify which tasks or resources should be displayed when the filter is applied. For example, the criterion for the Completed Tasks filter is any task that is 100 percent complete.

critical path: The series of tasks that must be completed on schedule for a project to finish on schedule. Each task on the critical path is a critical task.

critical task: A task that must be completed on schedule for the project to finish on time. If a critical task is delayed, the project completion date might also be delayed. A series of critical tasks makes up a project's critical path.

deadline: A target date indicating when you want a task to be completed. If the deadline date passes and the task is not completed, Project displays an indicator.

delay: The amount of time between the scheduled start of a task and the time when work should actually begin on the task; it is often used to resolve resource overallocations. There are two types of delay: assignment delay and leveling delay.

deliverable: A tangible and measurable result, outcome, or item that must be produced to complete a project or part of a project. Typically, the project team and project stakeholders agree on project deliverables before the project begins.

duration: The total span of active working time that is required to complete a task. This is generally the amount of working time from the start to finish of a task, as defined by the project and resource calendar.

earned value: A measure of the cost of work performed up to the status date or current date. Earned value uses your original cost estimates saved with a baseline and your actual work to date to show whether the actual costs incurred are on budget.

effort-driven scheduling: The default method of scheduling in Project; the duration of a task shortens or lengthens as resources are added or removed from a task, while the amount of effort necessary to complete a task remains unchanged.

embedded object: Information [the object] inserted in a file [the destination file]. Once embedded, the object becomes part of the destination file. When you double-click an embedded object, it opens in the program it was created in [the source program].

enterprise project: A project that is stored in Project Server to ensure information integrity. To make changes to an enterprise project, users with access permissions are required to check it in and out from Project Server.

enterprise resources: Resources that are part of an organization's entire list of resources. Enterprise resources can be shared across projects.

expected duration: The total span of active working time expected for a task, that is, the amount of time from the expected start to the expected finish of a task.

external dependency: A relationship in which the start or finish date of a task depends on a task in another project.

external task: A task that represents a linked task in another project, providing an easy way to review the attributes of linked tasks without switching between projects. An external task can be changed only in the source project.

field: A location in a sheet, form, or chart that contains a specific kind of information about a task, resource, or assignment. For example, in a sheet, each column is a field. In a form, a field is a named box or a place in a column.

filter: Specifies which task or resource information should be displayed or highlighted in a view. For example, when you apply the Critical filter, only critical tasks are displayed.

finish date: The date that a task is scheduled to be completed. This date is based on the task's start date, duration, calendars, predecessor dates, task dependencies, and constraints.

fixed-duration scheduling: A scheduling method in which the duration for a task remains the same regardless of the number of resources assigned to the task.

fixed-duration task: A task in which the duration is a fixed value and any changes to the work or the assigned units [that is, resources] don't affect the task's duration. This is calculated as follows: Duration x Units = Work.

fixed-unit task: A task in which the assigned units [or resources] is a fixed value and any changes to the amount of work or the task's duration do not affect the task's units. This is calculated as follows: Duration x Units = Work.

form: A type of view that gives you detailed information about an individual task or resource.

Gantt bar: A graphical element on the chart portion of the Gantt Chart view representing the duration of a task.

Gantt Chart view: A predefined view that displays project tasks on the left side of the view, and graphical bars corresponding to the task's durations on the right side of the view.

generic resources: Placeholder resources that are used to specify the skills required for a specific task.

global file: A Project file [Global.mpt] that contains information you can use for different projects. Information in a global file can include views, calendars, forms, reports, tables, filters, toolbars, menu bars, macros, and options settings.

grade: A rank or category assigned to a material resource that denotes functional use but not level of quality. A low-grade resource is not necessarily a low-quality resource.

group: To combine or rearrange tasks or resources in a project according to specific criteria, for example, task duration, priority, resource overallocation, or finish date; do not confuse this with the Group field, which is a resource field.

indenting: Moving a task to a lower outline level [to the right] in the Task Name field. When you indent a task, it becomes a subtask of the nearest preceding task at a higher outline level.

indicators: Small icons representing information for a task or resource that are displayed in the Indicators field. The Indicators field is located to the right of the ID field and appears in a number of tables.

inflexible constraint: A constraint that is inflexible because it ties a task to a date. The inflexible constraints are Must Finish On and Must Start On.

interim plan: A set of task start and finish dates that you can save at certain stages of your project. You can compare an interim plan with the baseline plan or current plan to monitor project progress or slippage. You can save up to 10 interim plans.

Internet: A worldwide network of thousands of smaller computer networks and millions of commercial, educational, government, and personal computers. Also known as the World Wide Web [WWW].

intranet: Any network that provides similar services within an organization to those provided by the Internet. An organization's intranet may or may not be connected to the Internet; its information might be distributed only within the company.

lag time: A delay between tasks that have a dependency. For example, if you need a 2-day delay between the finish of one task and the start of another, you can establish a finish-to-start dependency and specify a two-day lag time [has a positive value].

lead time: An overlap between tasks that have a dependency. For example, if a task can start when its predecessor is half-finished, you can specify a finish-to-start dependency with a lead time of 50 percent for its successor [has a negative lag value].

lessons learned: A review of best practices, project insights, and client information. As the project team disbands and new projects begin, reviewing the lessons learned lets you record information gathered and generated through the project.

leveling: Resolving resource conflicts or overallocations by delaying or splitting certain tasks. When Project levels a resource, its selected assignments are distributed and rescheduled.

link line: On the Gantt Chart and Network Diagram, the line that appears between two tasks to indicate a task dependency.

linking: In a project, establishing a dependency between tasks. Linking tasks defines a dependency between their start and finish dates. In OLE, establishing a connection between programs so that data in one document is updated when it changes in another.

macro: An action or a set of actions that you can use to automate tasks. Macros are recorded in the Visual Basic for Applications programming language.

master project: A project containing other projects [known as inserted projects or subprojects]. Also called a consolidated project.

material resource: The supplies or other consumable items that are used to complete tasks in a project.

material resources: Consumable materials or supplies, such as concrete, wood, or nails.

maximum units: The maximum percentage or number of units that a resource is available to be scheduled for any tasks. The maximum units value indicates the highest capacity at which the resource is available for work; the default value is 100 percent.

Microsoft Office Project Portfolio Server 2007: The Web-based user interface that is used with Project Server to help organizations achieve maximum portfolio value through managing investments and evaluating them against performance metrics and business objectives.

Microsoft Office Project Server 2007: A Project companion product that enables collaborative planning and status reporting among workgroup members, project managers, and other stakeholders by working with and exchanging project information on a Web site.

Microsoft Office Project Web Access 2007: The Web-based user interface that is used to access information in Project Server.

milestone: A reference point marking a major event in a project and used to monitor the project's progress. Any task with zero duration is automatically displayed as a milestone; you can also mark any other task of any duration as a milestone.

Network Diagram: A diagram that shows dependencies between project tasks. Tasks are represented by boxes, or nodes, and task dependencies are represented by lines that connect the boxes. In Project, the Network Diagram view is a network diagram.

noncritical task: A task with slack time that can be completed after its end date without delaying the project finish date. Slack is the amount of time that a task can slip before it affects another task's dates or the project finish date.

nonworking time: Hours or days designated in a resource or project calendar when Project should not schedule tasks because work is not done. Nonworking time can include lunch breaks, weekends, and holidays, for example.

note: Explanatory text that you can attach to a task, resource, or assignment.

Here is the second half of the glossary for 70-632 (split into two parts because the Spaces team has a limit that is too low on blog entry size (how can one ever put in a picture or video?).

objective: The quantifiable criteria that must be met for the project to be considered successful. Objectives must include, at least, cost, schedule, and quality measures. Unquantified objectives increase the risk that the project won't meet them.

optimistic duration: The best-case possibility for the total span of active working time expected for a task, that is, the amount of time from the optimistic start to optimistic finish of a task.

Organizer: The tabbed dialog box in which you can copy custom views, tables, filters, grouping definitions, calendars, reports, forms, toolbars, maps, field attributes, and VBA modules to other documents and to other users.

outdenting: Moving a task to a higher outline level [to the left] in the Task Name field.

outline: A hierarchical structure for a project that shows how some tasks fit within broader groupings. In Project, subtasks are indented under summary tasks.

outline number: Numbers that indicate the exact position of a task in the outline. For example, a task with an outline number of 7.2 indicates that it's the second subtask under the seventh top-level summary task.

overallocation: The result of assigning more tasks to a resource than the resource can accomplish in the working time available.

overtime: The amount of work on an assignment that is scheduled beyond the regular working hours of an assigned resource and charged at the overtime rate. Overtime work indicates the amount of the assignment's work that is specified as overtime work.

pane: A section of a window that contains a view. A combination view consists of two panes, for example, the Gantt Chart view in the top pane and the Task Form view in the bottom pane.

per-use cost: A set fee for the use of a resource that can be in place of, or in addition to, a variable. For work resources, a per-use cost accrues each time that the resource is used. For material resources, a per-use cost is accrued only once.

percent complete: A field that you use to enter or display how much of a task has been completed. This value is expressed as the percentage of the task duration that has been completed.

percent work complete: A percentage value that indicates the current status of a task, resource, or assignment, expressed as the percentage of work that has been completed.

pessimistic duration: The worst-case possibility for the total span of active working time expected for a task, that is, the amount of time from the pessimistic start to pessimistic finish of a task.

PERT analysis: PERT [Program, Evaluation, and Review Technique] analysis is a process by which you evaluate a probable outcome based on three scenarios: best-case, expected-case, and worst-case.

phase: A group of related tasks that completes a major step in a project.

PivotChart: Provides a graphical representation of the data in a PivotTable report, an interactive, crosstabulated report that summarizes and analyzes data. Use the Portfolio Analyzer to select the data that you display in a PivotChart.

PivotTable report: An interactive table that summarizes, or crosstabulates, large amounts of data. You can rotate its rows and columns to see different summaries of the source data, filter the data by displaying different pages, or display details.

placeholder resource: A temporary resource name that is added to a project plan to help estimate the types and numbers of resources needed. With placeholder resource names, you can develop your project proposal and obtain approvals.

plan: A schedule of task start and finish dates and resource and cost data. A baseline plan is the original plan that you save and use to monitor progress. An interim plan is a set of dates you save during the project to compare to other interim plans.

planned costs: The latest cost of tasks, resources, assignments, and the entire project, which Project displays in the Cost field as cost or total cost.)

predecessor: A task that must start or finish before another task can start or finish.

priority: An indication of a task's importance and availability for leveling [that is, resolving resource conflicts or overallocations by delaying or splitting certain tasks]. Tasks with the lowest priority are delayed or split first.

procure: To obtain the work and material resources required to complete a project.

progress lines: Visually represent the progress of your project, displayed in the Gantt Chart view. Progress lines connect in-progress tasks, creating a graph on the Gantt Chart indicating work that is behind and peaks indicating work that is ahead.

project assumptions: Factors that, for planning purposes, are considered to be true, real, or certain. Assumptions generally involve a degree of risk.)

project calendar: The base calendar used by a project.

project summary task: A task that summarizes the duration, work, and costs of all tasks in a project. The project summary task appears at the top of the project, its ID number is 0, and it presents the project's timeline from start to finish.

project triangle: The interrelationship of time, money, and scope. If you adjust any one of these elements, the other two are affected. For example, if you adjust the project plan to shorten the schedule, you might increase costs and decrease scope.

quality: The degree of excellence, or the desired standards, in a product, process, or project.

recurring task: A task that occurs repeatedly during the course of a project. For example, you might define the weekly status meeting as a recurring task.)

remaining cost: The estimated cost that is yet to be incurred for a task, resource, or assignment.

remaining duration: The amount of time left to work on a task before the task is completed. This is calculated as follows: Remaining Duration = Duration - Actual Duration.

remaining work: The amount of work, in terms of a time unit such as hours or days, that is left to be completed on a task. This is calculated as follows: Remaining Work = Work - Actual Work.

report: A format in which you can print schedule information that is appropriate for the intended recipients. You can use the predefined reports provided by Project or create custom reports.

resource allocation: The assignment of resources to tasks in a project.

resource calendar: A calendar that specifies working and nonworking time for an individual resource. A resource calendar differs from a base calendar, which specifies working and nonworking time for more than one resource.

resource information: The categories of information shown in the Resource Sheet view that specify details about a resource, such as name, type, group, maximum units, and standard rate. Apply a different table to the view for other resource information.

resource pool: A set of resources that is available for assignment to project tasks. A resource pool can be used exclusively by one project or can be shared by several projects.

resource usage: An account of how many hours a resource is scheduled to work within a given time period, and thus an indicator of a resources allocation within that time period.

resource view: A view that displays resource information. Resource views include the Resource Sheet, the Resource Graph, the Resource Usage, and the resource forms views.

resources: The people, equipment, and material that are used to complete tasks in a project.

risk: An event or situation that may negatively affect project scope, schedule, budget, or quality.

risk management plan: A document defining how risk will be managed throughout the project. It can include identified risks, probabilities, contingency plans and methods for implementing them, and a strategy for allocating resources if a risk event occurs.

schedule: The timing and sequence of tasks within a project. A schedule consists mainly of tasks, task dependencies, durations, constraints, and time-oriented project information.

scheduled or current cost: The latest cost of tasks, resources, assignments, and the entire project, which is displayed in the cost field as cost or total cost. It is kept up to date with cost adjustments that you make and with the project's progress.

scope: The combination of all project goals and tasks, and the work required to accomplish them.

sharer file: A file using resources from another file, which can be another project file or a file containing only resource information, called a resource pool.

sheet: A spreadsheet-like representation [in rows and columns] of task or resource information. Each row specifies an individual task or resource. Each column [field] specifies a type of information, such as start dates or standard rates.

side pane: A pane displayed on the left side of the Project and Project Web Access interfaces. In Project, the side pane contains Project Guide information; in Project Web Access, the side pane contains links.

skill codes: Skill codes are a type of enterprise outline code that allows you to specify the skills that a resource has.

skill set: A particular resource's skills.

slack: The amount of time that a task can slip before it affects another task or the project's finish date. Free slack is how much a task can slip before it delays another task. Total slack is how much a task can slip before it delays the project.

slippage: The amount of time that a task has been delayed from its original baseline plan. The slippage is the difference between the scheduled start or finish date for a task and the baseline start or finish date.

split task: A task whose schedule is interrupted. For example, a two-day task that does not require contiguous work might be split so that the first day of work is scheduled for Monday, and the second day is scheduled for Thursday.

stakeholders: Individuals and organizations that are actively involved in the project or whose interests may be affected by the project.

standard rate: A base rate that you assign to resources [such as people, equipment, or material] and that Project uses to calculate resource cost totals.

start date: The date when a task is scheduled to begin. This date is based on the duration, calendars, and constraints of predecessor and successor tasks. A task's start date is also based on its own calendars and constraints.

status date: A date that you set [rather than the current date] for reporting the time, cost, or performance condition of a project.

subproject: A project that is inserted into another project. Use subprojects as a way to break complex projects into more manageable parts. Also known as an inserted project.

subtask: A task that is part of a summary task. The subtask information is consolidated into the summary task. You can designate subtasks by using the Project outlining feature.

successor: A task that cannot start or finish until another task starts or finishes.

summary task: A task that is made up of subtasks and summarizes those subtasks. Use outlining to create summary tasks. Project automatically determines summary task information [such as duration and cost] by using information from the subtasks.

supplier: A contractor, vendor, or other agency that supplies a material, product, or service that is required to complete a project.

task: An activity that has a beginning and an end. Project plans are made up of tasks.

task calendar: The base calendar that you can apply to individual tasks to control their scheduling, usually independent of the project calendar or any assigned resources' calendars. By default, all tasks use the project calendar.

task dependencies: A relationship between two linked tasks; linked by a dependency between their finish and start dates. There are four kinds of task dependencies: Finish-to-start [FS], Start-to-start [SS], Finish-to-finish [FF], and Start-to-finish [SF].

task type: A characterization of a task based on which aspect of the task is fixed and which aspects are variable. There are three task types: Fixed Units, Fixed Work, and Fixed Duration. The default task type in Project is Fixed Units.

template: A Project file format [*.mpt] that lets you reuse existing schedules as the starting point for creating new schedules. Task and resource information, formatting, macros, and project-specific settings can all become part of a template.

timephased: Task, resource, or assignment information that is distributed over time. You can review timephased information in any available time period in the fields on the right side of the Task Usage and Resource Usage views.

timescale: The time period indicator at the top of the Gantt views, the Resource Graph view, the Task Usage view, and the Resource Usage view. You can customize it to show up to three tiers that can display various time units: top, middle, and bottom.

toolbar: A bar with buttons and options used to carry out commands. To display a toolbar, point to Toolbars on the View menu, and then click the toolbar you want. To see more buttons, click Toolbar Options at the end of the toolbar.

total cost: The calculated cost of a project, task, resource, or assignment over the life of the project.

total slack: The amount of time that the finish date of a task can be delayed without delaying the finish date of the project.

tracking: Viewing and updating of the actual progress of tasks so that you can see progress across time, evaluate slippage of tasks, compare scheduled or baseline data to actual data, and check the completion percentage of tasks and your project.) (underallocation: Assigning a resource to work fewer hours than the resource has available.

unit availability: Amount of time, expressed as a percentage or a decimal number, that a resource can be scheduled for assigned work. It refers to the availability of a resource; for example, a resource may be available 50%, 100%, or 300% of full time.

units: The quantity of a resource assigned to a task. The maximum units is the maximum number of units available for the resource. For example, if you have three plumbers, the maximum units is 300 percent or three plumbers working full-time.

URL: Uniform Resource Locator, which is a standard for naming and locating an object on the Internet, such as a file or newsgroup. URLs are used extensively on the World Wide Web. They are used in HTML documents to specify the target of a hyperlink.

variance: The difference between baseline and scheduled task or resource information, they usually occur when you set a baseline plan and begin entering actual information into your schedule. Variances can occur in work, costs, and schedule.

view: The combination of one or more views [Gantt Chart, Resource Sheet, and so on] and if applicable, a table and a filter. Use views to work with information in a variety of formats. There are three types of views: Charts or graphs, Sheets, and Forms.

WBS [work breakdown structure]: A hierarchical structure that is used to organize tasks for reporting schedules and tracking costs. With Project, you can represent the work breakdown structure by using task IDs or by assigning your own WBS code to each task.

work: For tasks, the total labor required to complete a task. For assignments, the amount of work to which a resource is assigned. For resources, the total amount of work to which a resource is assigned for all tasks. Work is different from task duration.

work resource: People and equipment resources that perform work to accomplish a task. Work resources consume time [hours or days] to accomplish tasks.)

working time: Hours designated in a resource or project calendar during which work can occur.

WWW: A subset of the Internet that uses a graphical user interface as opposed to a text-based user interface. The pages or Web sites that display are formatted using by HTML. Web browsers make it possible for users to view Web sites.

XML: Extensible Markup Language [XML] is a format for delivering rich, structured data from an application in a standard, consistent way. XML describes the content of a document, whereas HTML tags describe how the document looks.