Scribd
Upload
74 views3 pages

XML Document of Purchase Order - : Name Type Details

The document describes an XML document structure for purchase orders. It defines the root element of <PurchaseOrder> which contains attributes for the order number, date, type, and customer. Address elements contain sub-elements for names, streets, cities, states, zip codes, and countries. An <Items> element lists purchased items, with <Item> elements having attributes for part numbers, conditions, and prices. The document aims to organize purchase order data in a structured XML format.

Uploaded by

Ashish Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
74 views3 pages

XML Document of Purchase Order - : Name Type Details

The document describes an XML document structure for purchase orders. It defines the root element of <PurchaseOrder> which contains attributes for the order number, date, type, and customer. Address elements contain sub-elements for names, streets, cities, states, zip codes, and countries. An <Items> element lists purchased items, with <Item> elements having attributes for part numbers, conditions, and prices. The document aims to organize purchase order data in a structured XML format.

Uploaded by

Ashish Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

1.

XML Document of Purchase order –

2. Documentation of element, attribute, and attribute value -

Name Type Details


PurchaseOrder Element PurchaseOrder is the root element of the
document that encapsulate all other elements.
OrderNumber Attribute Attribute of root element “PurchaseOrder” that
contains unique order number.
OrderDate Attribute Attribute of root element “PurchaseOrder” that
contains order placed date.
OrderType Attribute Attribute of root element “PurchaseOrder” that
contains information whether order placed online
or in-store.
OrderCustomerTyp Attribute Attribute of root element “PurchaseOrder” that’s
e contains information whether customer is existing
or new.
Address Element XML doc can contain multiple Address element
block to keep records of Shipping address and
Billing address.
Type Attribute Attribute of element Address that contains address
type whether Shipping or billing.
Name Element It’s sub-element of address that contains name of
customer for either billing or shipping items.
Street Element It’s sub-element of address that contains
customer’s street address to ship items or billing
City Element It’s sub-element of address that contains name of
city
State Element It’s sub-element of address that contains name of
state
Zip Element It’s sub-element of address that contains zip code
of customer
Country Element It’s sub-element of address that contains
customer’s country name
DeliveryNotes Element Element that’s contains note if customer want to
inform shipper for special shipping instructions.
Items Element Items element contains list of purchased item that
user placed either online or in-store.
Item Element Item element contains details of purchased items
PartNumber Attribute Attribute of item that contains item’s unique part
number
ItemCondition Attribute Attribute that contains information about item
condition whether it’s new or refurbished.
ProductName Element It contains name of the product
Quantity Element It contains number of quantities of product
purchased by customer
USPrice Element It contains items’ price per item calculate final
price * items
ShipDate Element Element contains expected ship date of purchased
items based on customer’s zip code and availability
in warehouse.

Q - How did you decide to represent the data in the way that you did? Why did you choose the
elements and attributes that you did?

A – Analyzed text data that was in CSV format and identified common information (elements)
to group together and information (attributes) that seems unique for placed order. I added
parent element PurchaseOrder for all items that was ordered by customer in same date and
order number was same. Grouped all purchased Item under Items parent’s element.

Q - What were the hardest decisions you had to make in this design process?
A – Analyzed and included all data after identifying common elements and unique attributes
and grouped together to form a complete PurchaseOrder schema, so note taken any hard
decision to leave any information or placed order that was in CSV format.
Q – How does your DTD design support data independence?
A – DTD designed to operates on a subset of attributes of a relation. In current DTD designed it
should not be affected later when new attributes are added to the same relation. 

Q - How may your DTD design support the overarching goals of data curation (revisit objectives
and activities of Week 1)?
A - Schema designed in relational model and relation schema support overreaching goal of data
curation.
 Supports data organization by defining the model
 Data preservation by ensuring understandability and future usability
 Data discovery by ensuring and supporting the ability to search and locate relevant data
 Data accessibility by helping in retrieving and distributing data.
 Data identification

Q - What are the pros and cons of your DTD design?


A – Pros –
 Meets the goal of Data curation.
 Structured markup translation is easy and quick
 Data integration is seamless.
 Flexible design

Cons –
 Additional effort required for efficient data handshake in case data construction
deviates

You might also like