kalavathi: 2008

Wednesday, May 21, 2008

kalavathi

Web Images News Orkut Groups Gmail more ▼ Books Scholar Blogs Calendar Photos Documents Reader even more » Sign in
Advanced Image Search
Preferences
Moderate SafeSearch is on

Images Results 1 - 20 of about 90,300 for jaipur palace photos. (0.19 seconds)
Show: All sizes - Extra Large - Large - Medium - Small

Jaipur
376 x 247 - 54k - jpg
www.jacekphoto.com ... the Jaipur City Palace.
600 x 393 - 64k - jpg
data1.blog.de He lives in a part of the Palace and ...
600 x 416 - 61k - jpg
data1.blog.de Jaipur Palace Of Winds
650 x 488 - 122k - jpg
www.pgsindia.net

... city of Jaipur, the City Palace ...
287 x 180 - 42k - gif
www.info2india.com The Palace on the Lake at Jaipur.
518 x 365 - 69k - jpg
homepages.tesco.net Museum attendant, palace of Jaipur
450 x 600 - 127k - jpg
www.pa-chouvy.org Sculptures on a wall of the palace ...
450 x 600 - 165k - jpg
www.pa-chouvy.org

Jaipur palace
720 x 564 - 68k - jpg
danny.oz.au Inside the Jaipur Palace Restaurant
1704 x 2272 - 229k - jpg
www.geocities.com Window in Jaipur palace
320 x 480 - 41k - jpg
www.europe-entry.com Then Jaipur itself and this is the ...
512 x 365 - 52k - jpg
www.physics.drexel.edu

Jaipur's palace complex
438 x 600 - 126k - jpg
www.pbase.com The palace at Jaipur is part of a ...
498 x 332 - 41k - jpg
www.grant.org The Umaid Bhavan Palace is owned by ...
1726 x 1112 - 86k - jpg
www.alovelyworld.com Jaipur Palace Hotel
732 x 575 - 51k - gif
www.indianholiday.com

Jaipur Palace Hotel
476 x 638 - 58k - gif
www.indianholiday.com Jaipur Palace Waiters.
610 x 458 - 76k - jpg
airpaharganj.com Jaipur Palace
639 x 479 - 41k - jpg
www.hoshimotors.net Big Sliver Pot - Jaipur Palace
225 x 300 - 11k -
www.travelblog.org

1
2
3
4
5
6
7
8
9
10
Next

--------------------------------------------------------------------------------

©2008 Google - Google Home - Advertising Programs - About Google

kalavathi

JAVA EJB XML LOG4J STRUTS ANT

Home | About us | Developer Forum | Code Library Forum | Contact us | Site map

HIBERNATE TUTORIAL

HIBERNATE

ABOUT THE AUTHOR:

Bhushan Dongare
A good developer and architect, having in depth knowledge of all the latest happenings in technology, the best thing with him is you talk to him on java he will talk java you talk to him on Microsoft he with talk Microsoft. He has a good experience into Java and J2EE designing and development. He has worked for many national and international clients as developer and designer on J2EE technologies.

Requirement Analysis and Designing and Project Estimation are his core competency, may be soon I will ask him to come up with some writings on Function Point and Use Case Analysis.

Here is a write-up by Mr. Bhushan Dongare on hibernate.

Abstract: Hibernate lets you develop persistent classes following common Java idiom - including association, inheritance, polymorphism, composition and the Java collections framework.

Hibernate not only takes care of the mapping from Java classes to database tables (and from Java data types to SQL data types), but also provides data query and retrieval facilities and can significantly reduce development time otherwise spent with manual data handling in SQL and JDBC. .

Topics Covered:
1. Introduction to Hibernate
2. Overview of Hibernate
3. Features of Hibernate
4. Getting Started with Hibernate
5. Hibernate O/R Mapping
6. Hibernate Mapping In Depth
7. Hibernate Query Language
8. Hibernate Complete Example

If you have questions, please mail it at mail@allapplabs.com

Hibernate tutorial
Introduction to Hibernate
Overview of Hibernate
Features of Hibernate
Getting Started with Hibernate
Hibernate O/R Mapping
Hibernate Mapping In Depth
Hibernate Query Language
Hibernate Complete Example

Use of this website constitutes acceptance of the AllAppLabs.com Terms and Conditions
AllAppLabs.com

kalavathi

JAVA EJB XML LOG4J STRUTS ANT

Home | About us | Developer Forum | Code Library Forum | Contact us | Site map

Java Collection Framework

We have tried you to make a walk through the Collection Framework. The Collection Framework provides a well-designed set if interface and classes for sorting and manipulating groups of data as a single unit, a collection.

The Collection Framework provides a standard programming interface to many of the most common abstractions, without burdening the programmer with too many procedures and interfaces.

The Collection Framework is made up of a set of interfaces for working with the groups of objects. The different interfaces describe the different types of groups. For the most part, once you understand the interfaces, you understand the framework. While you always need to create specific, implementations of the interfaces, access to the actual collection should be restricted to the use of the interface methods, thus allowing you to change the underlying data structure, without altering the rest of your code.

In the Collections Framework, the interfaces Map and Collection are distinct with no lineage in the hierarchy. The typical application of map is to provide access to values stored by keys.

When designing software with the Collection Framework, it is useful to remember the following hierarchical relationship of the four basic interfaces of the framework.

The Collection interface is a group of objects, with duplicates allowed.

Set extends Collection but forbids duplicates.

List extends Collection also, allows duplicates and introduces positional indexing.

Map extends neither Set nor Collection

Interface Implementation Historical
Set HashSet TreeSet
List ArrayList LinkedList Vector
Stack
Map HashMap Treemap Hashtable
Properties

The historical collection classes are called such because they have been around since 1.0 release of the java class libraries. If you are moving from historical collection to the new framework classes, one of the primary differences is that all operations are synchronized with the new classes. While you can add synchronization to the new classes, you cannot remove from the old.

Explore the Interface and Classes of Java Collection Framework

Collection Interface
Iterator Interface
Set Interface
List Interface
ListIterator Interface
Map Interface
SortedSet Interface
SortedMap Interface
HashSet & TreeSet Classes
ArrayList & LinkedList Classes
HashMap & Treemap Classes
Vector and Stack Classes

Collection Framework
Collection Interface
--------------------------------------------------------------------------------
Iterator Interface
--------------------------------------------------------------------------------
Set Interface
--------------------------------------------------------------------------------
List Interface
--------------------------------------------------------------------------------
ListIterator Interface
--------------------------------------------------------------------------------
Map Interface
--------------------------------------------------------------------------------
SortedSet Interface
--------------------------------------------------------------------------------
SortedMap Interface
--------------------------------------------------------------------------------
HashSet & TreeSet Classes
--------------------------------------------------------------------------------
ArrayList & LinkedList Classes

--------------------------------------------------------------------------------
HashMap & Treemap Classes
--------------------------------------------------------------------------------
Vector & Stack Classes

Use of this website constitutes acceptance of the AllAppLabs.com Terms and Conditions
AllAppLabs.com

kalavathi

Diamond Floating Heart Anklet In 14kt White Gold
Add a little pizazz to your flip flops and sandals this summer. A 14kt white gold anklet features diamond accents on a floating heart suspended from a rolo chain. Lobster clasp.
See more products like this
Related Searches:

* • anklet white gold
* • diamond anklet
* • heart anklets
* • anklets

$250

go to seller
Ross-Simons
.20 ct. t.w. Pave Diamond Anklet In 14kt White Gold

.20 ct. t.w. Pave Diamond Anklet In 14kt White Gold
Add a little sparkle to your step with this .20 ct. t.w. pave diamond station-style anklet. In 14kt white gold. 1mm cable chain with a lobster clasp. Available as :9.5-inch
See more products like this
Related Searches:

* • diamond anklet

$395

go to seller
Ross-Simons
10k Gold Heart Anklet 9''

10k Gold Heart Anklet 9''
Decorate your ankle with 10k gold hearts. An ankle bracelet that links one heart to another. Set in 10k gold, it shows that you're all heart. 9'' length. Imported.
See more products like this
Related Searches:

* • gold anklets
* • gold heart anklet

$99.99

go to seller
PalmBeach
14k Tri-Tone Gold Anklet

14k Tri-Tone Gold Anklet
This distinctively designed bracelet features beads of 14k yellow, white & rose gold floating on a fine yellow gold chain. Anklet measures 10" long.
See more products like this
Related Searches:

* • 14k anklets
* • anklets
* • anklet white gold

$150

go to seller
Diamonds Int
18k/Sterling Silver Ankle Bracelet

18k/Sterling Silver Ankle Bracelet
Diamond-accented ankle dressing.
See more products like this
Related Searches:

* • diamond ankle bracelet
* • ankle bracelet

$49.99

go to seller
PalmBeach
14k Two-Tone Gold Diamond Anklet (.03 ctw)

14k Two-Tone Gold Diamond Anklet (.03 ctw)
This stylish 14k white and yellow gold necklace has two bezel-set diamond (.03 ctw) accents.
See more products like this
Related Searches:

* • diamond anklet
* • anklets

$380

go to seller
Diamonds Int
Sterling Silver Cubic Zirconia Palm Tree Anklet

Sterling Silver Cubic Zirconia Palm Tree Anklet
This breezy Designer inspired diamond cubic zirconia palm tree anklet almost brings the air of tropical beaches to the senses as it dangles freely around the ankle.
See more products like this
Related Searches:

* • jewelry palm tree
* • palm tree

$26.00

go to seller
Amazon
LIMOGES JEWELRY Sterling Silver Script Name Anklet - Personalized Jewelry

LIMOGES JEWELRY Sterling Silver Script Name Anklet - Personalized Jewelry
Sterling Silver name anklet features a polished dainty script name with tail. Personalize with one name up to 12 letters.
See more products like this
Related Searches:

* • sterling silver anklets
* • anklets

$39.99

go to seller
LimogesJewel
Sparkling CZ By The Yard Anklet

Sparkling CZ By The Yard Anklet
This delicate Tiffany Inspired CZs by the yard anklet has 3 mm bezel set diamond cubic zirconias set in sterling silver and connected by a sterling silver rhodium finished rolo ...
See more products like this
Related Searches:

* • diamonds by the yard

$24.00

go to seller
evesaddictio
14K White Gold All Beaded Anklet 11''

14K White Gold All Beaded Anklet 11''
Show her you care with lovely gold bracelet. This All Beaded Anklet is crafted from 14K white gold.
See more products like this
Related Searches:

* • anklet white gold

$43.95

go to seller
Netaya.com
Two Tone Gold Men Bracelets 14k Gold Men Bracelet 8 1/4 "

Two Tone Gold Men Bracelets 14k Gold Men Bracelet 8 1/4 "
Two Tone Gold Men's Bracelets 14k Gold Men's Bracelet 8 1/4 " Made in Italy, this distinctive Two Tone Men's Gold Bracelet is 3/8 " wide, 21.6 grams.
See more products like this
Related Searches:

* • gold bracelets mens

$1,303

go to seller
JewelBasket
Cubic Zirconia Sterling Silver Dragonfly Anklet

Cubic Zirconia Sterling Silver Dragonfly Anklet
You will love the feeling of this sweet little cz dragonfly flitting around your ankle.
See more products like this
Related Searches:

* • dragonfly

$30.00

go to seller
evesaddictio
NOVICA Beaded anklet, 'Fire Dancer'

NOVICA Beaded anklet, 'Fire Dancer'
This anklet glistens with florid beauty. It is crafted by hand by Sheela in a design that evokes mystical Indian dancers.

$24.95

go to seller
Novica
14K Yellow Gold Beaded Anklet - 9''

14K Yellow Gold Beaded Anklet - 9''
This fashionable anklet is crafted of 14Kyellow gold and features a beaded link design. Anklet measures 9'' in length and weighs 1.37 grams.
See more products like this
Related Searches:

* • gold anklets

$49.95

go to seller
Netaya.com
.15 ct. t.w. Diamond Butterfly Charm Anklet In 14kt White Gold.

.15 ct. t.w. Diamond Butterfly Charm Anklet In 14kt White Gold.
Add a little pizazz to your flip flops and sandals this summer. Our 14kt white gold anklet dangles a .15 ct. t.w. flickering diamond butterfly from a 2mm rolo-link chain.
See more products like this
Related Searches:

* • diamond anklet
* • butterfly diamond
* • butterfly sandal

$295

go to seller
Ross-Simons

Hide images
Sort by: Best Match | Price
Results per Page: 15 | 30 | 60

« previous 1234567891011+ next »

kalavathi

Canon XTi 400D 10.1 MP Digital Camera - Black
The Canon EOS Digital Rebel XTi offers an unbeatable combination of performance ease-of-use and value.
See more products like this
Related Searches:

* • canon xti
* • canon rebel xti
* • digital camera
* • xti
* • cameras

$449 to $600

view 10 prices
Including: Dell Accesso:$500
BPAV.com:$540
DigiCombos:$493
Canon PowerShot SD870 8.0MP Digital Camera Silver

Canon PowerShot SD870 8.0MP Digital Camera Silver
From the very first glance, the smooth shape and bold lines of the stylish PowerShot SD870 IS Digital ELPH signal that this is no ordinary camera.
See more products like this
Related Searches:

* • canon 870
* • canon powershot sd 870 is
* • sd870
* • canon sd870
* • canon 870is digital camera

$235 to $409

view 25 prices
Including: Dell Accesso:$250
AbesOfMaine:$256
ButterflyPho:$256
Canon EOS-40D 10.1 Megapixel Digital Camera--Body Only

Canon EOS-40D 10.1 Megapixel Digital Camera--Body Only
Welcome to the next generation of digital SLR photography - the Canon EOS 40D.
See more products like this
Related Searches:

* • canon 40d
* • 40d
* • canon eos 40d
* • canon 40d body
* • digital camera

$847 to $1,300

view 23 prices
Including: BPAV.com:$1,180
Dell Accesso:$1,120
buydig.com:$935
Canon EOS Rebel Digital XTi 400D 10.1 Megapixel Digital Camera W/ 18-55mm

Canon EOS Rebel Digital XTi 400D 10.1 Megapixel Digital Camera W/ 18-55mm
Canon EOS Digital Rebel XTi (400D) 10.1 Megapixel Digital SLR Camera (Black) Kit with Canon Zoom Wide Angle-Normal 18-55mm f/3.5-5.6 Autofocus Lens
See more products like this
Related Searches:

* • canon rebel xti
* • canon xti
* • xti
* • canon eos 400d
* • canon 400d

$539 to $700

view 15 prices
Including: Dell Accesso:$590
ButterflyPho:$605
Newegg.com:$630
Nikon D300 12.3 MP SLR Digital Camera Body

Nikon D300 12.3 MP SLR Digital Camera Body
Nikon is pleased to announce the D300 digital single lens reflex (D-SLR) a camera that sets new standards of compact professional performance.
See more products like this
Related Searches:

* • nikon d300
* • d300
* • nikon d300 body
* • nikon
* • nikon 300d camera body

$1,397 to $1,800

view 18 prices
Including: AbesOfMaine:$1,699
42nd St. Pho:$1,670
DigiCombos:$1,550
Canon PowerShot G9 12MP Digital camera

Canon PowerShot G9 12MP Digital camera
12.1-megapixel recording (resolution up to 4000 x 3000),6X optical zoom lens with optical image stabilizer,3" LCD
See more products like this
Related Searches:

* • canon g9
* • canon powershot g9
* • digital camera
* • g9
* • powershot g9

$397 to $500

view 23 prices
Including: Dell Accesso:$425
ButterflyPho:$435
AbesOfMaine:$448
Nikon D40 6.1 Megapixel Digital Camera W/ 18-55mm Lens

Nikon D40 6.1 Megapixel Digital Camera W/ 18-55mm Lens
Nikon D40 6.1 Megapixel Digital SLR Camera Kit with Nikon 18-55mm f/3.5-5.6G ED II AF-S DX Zoom-Nikkor Autofocus Lens
See more products like this
Related Searches:

* • nikon d40
* • nikon d40 kit
* • d40
* • nikon
* • nikon cameras

$417 to $554

view 27 prices
Including: RitzCamera:$500
AbesOfMaine:$479
Dell Accesso:$460
Nikon D60 10.2 Digital SLR Camera

Nikon D60 10.2 Digital SLR Camera
Extraordinary 10.2-megapixel DX-format Nikon picture quality Includes AF-S DX NIKKOR 18-55mm f/3.5-5.6G Vibration Reduction lens 2.5-inch LCD screen; horizontal and vertical ...
See more products like this
Related Searches:

* • nikon d60
* • nikon
* • d60
* • nikon cameras
* • digital camera

$589 to $754

view 27 prices
Including: DigiCombos:$589
AbesOfMaine:$700
Dell Accesso:$670
Canon EOS 5D 12.8 Megapixel SLR Digital Camera Kit Body Only

Canon EOS 5D 12.8 Megapixel SLR Digital Camera Kit Body Only
Capture sharp and clear images with the EOS 5D Digital SLR Camera from Canon.
See more products like this
Related Searches:

* • canon 5d
* • canon eos 5d
* • eos 5d
* • 5d
* • canon 5d body only

$1,529 to $3,000

view 23 prices
Including: AbesOfMaine:$1,889
42nd St. Pho:$1,870
Dell Accesso:$2,500
Panasonic Lumix DMC-FZ18K 8.1MP Digital Camera with 18x Wide Angle MEGA Optical Image Stabilized Zoom (Black)

Panasonic Lumix DMC-FZ18K 8.1MP Digital Camera with 18x Wide Angle MEGA Optical Im...
The DMC-FZ18 Lumix camera from Panasonic enables you to take a large array of photos thanks to the 8.1 megapixels and its 18x optical zoom.
See more products like this
Related Searches:

* • fz18
* • panasonic lumix dmc fz 18
* • panasonic fz18
* • panasonic dmc fz18
* • digital camera

$279 to $350

view 16 prices
Including: beachcamera:$298
buydig.com:$298
Dell Accesso:$297
Canon PowerShot SX100IS 8.0 MP Digital Camera, Black

Canon PowerShot SX100IS 8.0 MP Digital Camera, Black
Get in on the action with a 10x zoom lens. PowerShot SX100 IS keeps your subject in focus with Face Detection and optical Image Stabilizer.
See more products like this
Related Searches:

* • canon sx100
* • digital camera
* • canon powershot sx100
* • cameras
* • canon 10 x optical zoom digital camera

$197 to $310

view 25 prices
Including: buydig.com:$209
ButterflyPho:$209
AbesOfMaine:$216
Nikon D80 10.2 Megapixel Digital Camera

Nikon D80 10.2 Megapixel Digital Camera
The Nikon D80 SLR Digital Camera features a 10.2 effective megapixel DX Format CCD image sensor, providing a high level of resolution and sharp detail, so users can have the ...
See more products like this
Related Searches:

* • nikon d80
* • nikon d80 18-135
* • nikon d80 kit
* • nikon d80 18-135mm
* • digital camera

$787 to $1,200

view 21 prices
Including: AbesOfMaine:$990
ButterflyPho:$988
Dell Accesso:$1,200
Nikon D300 12.3 MP Digital Camera With Nikon 18-200mm VR Lens

Nikon D300 12.3 MP Digital Camera With Nikon 18-200mm VR Lens
Nikon D300 Digital SLR Camera Outfit w/18-200mm f/3.5-5.6G ED-IF AFS DX VR(II) Lens -72mm-
See more products like this
Related Searches:

* • nikon d300
* • d300
* • nikon d300 18-200
* • nikon
* • slr digital camera

$1,997 to $2,550

view 18 prices
Including: 42nd St. Pho:$2,207
17StreetPhot:$2,329
DigiCombos:$2,200
Samsung L830 8.1 MP Digital Camera - Silver

Samsung L830 8.1 MP Digital Camera - Silver
Heart rendering moments of life pop up without any notice. Make sure you are prepared for the unexpected smiles life throws your way.
See more products like this
Related Searches:

* • digital camera
* • cameras
* • samsung l830
* • 8 mp digital camera
* • samsung 630

$153 to $170

view 2 prices
Including: Dell Accesso:$153
PC Connectio:$170
Canon EOS REBEL XSI KIT BLK-12.2MPIX EFS W/ LENS DELL (2756B003)

Canon EOS REBEL XSI KIT BLK-12.2MPIX EFS W/ LENS DELL (2756B003)
For stunning photography with point-and-shoot ease, look no further than Canon's EOS Rebel XSi. The EOS Rebel XSi brings staggering technological innovation to the masses.
See more products like this
Related Searches:

* • canon xsi
* • canon rebel xsi
* • rebel xsi
* • xsi
* • canon eos rebel xsi

$797 to $900

view 23 prices
Including: BPAV.com:$900
AbesOfMaine:$899
ButterflyPho:$838

Hide images
Sort by: Best Match | Price
Results per Page: 15 | 30 | 60

« previous 1234567891011+ next »

kalavathi

LOGIN / MY ACCOUNT / WISH LIST / SHOPPING BAG

■ Tops
Camis & Tanks
Tops
Graphic tees & Tanks
Sweaters & Knits
Tunics
Vests
Hoodies
Coats & Jackets
■ Bottoms
Pants
Skirts
Shorts
■ Dresses
■ Denim
■ Basics
Basic Tops
Basic Bottoms
■ Shoes
■ Accessories
Jewelery
Hats
Bags & Gifts

Summer is coming and bringing in a new wave of exciting new products. Lots of new camis, graphic tees and tanks, colorful skinny jeans, tunics, dresses, charmed necklaces, earrings, bangels and rhinestone trucker hats! We're sure you'll find some items you'll just fall in love with. <3

HACKER SAFE certified sites prevent over 99.9% of hacker crime.
Copyright© 2008 Pink Ice California Dream Company, Inc.
All rights reserved. ABOUT US / CONTACT US / PRIVACY & SECURITY / TERMS & CONDITIONS

kalavathi

? Closet Mistresses

? This is a joint account of me, eEsther?, aAlex?.
16 to 30 years old .
Singapore, West area
We ? Shopping xD
Items sold here is brand new, in good conditions & lowest price
Email Us : Click Here or sms to 96810229

? Terms and Conditions

? You may tag at our "TagiiesBox" if you are interested. But i prefer you to sms mii. You can send us a mail also. xD
? We will try to reply you as soon as possible, so, PLEASE BE PATIENCE!
? Please take note that for ALL PRE-ORDER goods, you have to wait for 1 to 3 weeks as I need time to get the stocks. :)
? All items are based on first come first serve basics.
? Prices are not negotiable unless it had stated there.
? No backing out after you have confirm to order. If you wann to cancel order, yes, you may, but will have to charge you S$6.
? Bidding will take place if there is two or more buyers, but, there is only one item avaiable.
? Swaps can be done if we are interested in your items, and it's BRAND NEW and additional S$3 charge.
? No dead buyers/MIA-ing (Missing in action-ING)
?All of our products are stated in Singapore dollars (SG$)
? No refund or exchange once items sold. PAYMENT HAVE TO BE MADE BEFORE I TAKE YOUR ORDERS. NO PAYMENT = NO ORDER.
? I will have the authority to cancel the spree if the capping did not reach my expectations and the EXACT amount will be return to you.
? Enjoy shopping with ShOpTituDe! Thank you xD

? Format

Mode of Payments
? Meet-ups
? Bank Transfers

Meet-ups
? Jurong Intercharge
? Bukit Batok
? Clementi
? Chua Chu Kang, Yew tee (Only on weekends)
?Please note that the above is charge FREE
? Additional of $4 of Transportion Fees will be charged for MEET-UPS at your convenience

POSB Bank Transfer
? Kindly make your payment within 2 working days after confirming your orders with us
? Inform us when payment is made and keep the recipt in case of somethings occurs.
? We will email or SMS you if the item upon receiving payment

Mail
? Normal postage $3
Not responsible if loss of mail
? Registered postage $4

Send orders in the following format
Name:
Address:
HP no:
Email:
Item code:
Colour if applicable:
Quantity of item:
Mode of payment & collection:
send all orders to: Easter_Dream@hotmail.com or Melodiie_Snow@yahoo.com.sg

? Links

? SGcafe
? BLOGskins
?
?
?
?
?

? Tagbox

any enquires? do tagged :D

? Music

? with love-hilary

? Credits

Designer: Agnes
Base Code: Tammy
Image: Enakei
Image Host: Photobucket
Others: Imeem , Cbox , Dorischu ,
Marcomedia Fireworks

? Wednesday, May 21, 2008

? Shop till you drop ! ?

Code: 180274 (Pre-order)
Price: S$18
Colour available: Grey, red, black, purple, blue
Size: Bust 30cm, length 69cm

? You're Shopping @

1:13 AM

?

? Shop till you drop ! ?

Code: 100878 (Pre-order)
Price: S$18
Colour available: grey, red, yellow, blue
Size: Bust 47cm, length 66cm (Ribbon adjustable)

? You're Shopping @

1:10 AM

?

? Shop till you drop ! ?

Code: 180303 (Pre-order)
Price: S$18
Colour available: Red, blue, pink, black
Size: Bust 34cm, length 70cm

? You're Shopping @

1:05 AM

?

? Shop till you drop ! ?

Code: 180270 (Pre-order)
Price: S$18
Colour available: White, pink, light blue, grey
Size: Bust 36cm, length 59cm

? You're Shopping @

1:02 AM

?

? Shop till you drop ! ?

Code: 180291 (Pre-order)
Price: S$18
Colour available: Purple, pink, red, grey, blue, bronze
Size: Bust 33cm, length 67cm

? You're Shopping @

12:57 AM

?

? Shop till you drop ! ?

Code: 140163 (Pre-order)
Price: S$18
Colour available: Dark blue, grey
Size: Bust 36cm, length 63cm

? You're Shopping @

12:53 AM

?

? Shop till you drop ! ?

Code: 140161 (Pre order)
Price: S$18
Colour available: Black, White
Size: Bust 25-42, length 65 cm

? You're Shopping @

12:48 AM

? Tuesday, May 20, 2008

? Shop till you drop ! ?

Code: 180311 (Pre-Order)
Price: S$15
Colours available: Red, Yellow, White, Black
Size: Free

? You're Shopping @

11:16 PM

?

? Shop till you drop ! ?

Hii all!
I am here to announced that WIWI spree and Orange Bear Spree will be open on 20 May 2008!
So DO buy as much as you can!

As my terms and conditions stated there S$4 will be charge for meet ups. I decided to give you guys a FREE meet ups if you buy more denn 3 pieces. 5 pieces and above will have a FREE gift!

But!
Not going to tell you now as it is a suprise gift. But i can guaranteed that the S.E.C.R.E.T gift will be worth more than S$8!!

This spree is closing on 8 Jun 08. All payments should be made on 7 Jun 08!
Thanks alot!

? You're Shopping @

10:22 PM

?

? Shop till you drop ! ?

Item #04 (IN-Stocks)
Price: S$4.90 = now at S$4 ea
Left with silver and pink. 1 each only.
Description: Really bright kind of liquid eyeliner. Apply on your eye and you can see your eyes sparkling in the dark.

? You're Shopping @

1:36 AM

?

? Shop till you drop ! ?

Item #03 (In-Stocks)
Price: S$8.00 = now at S$6.90
Left 1 only. Glue provided inside.

? You're Shopping @

1:33 AM

?

? Shop till you drop ! ?

Item #02 (IN-Stocks)
Price: S$7 = now at S$4.50 ea (Price slashed)
Left with blue and green. Each for both. Obtain from cosmetic spree 1.
Description: Apply some mascara on your lashes 1st. After that, drop a few drops of lash jewel on your lashes. Your eyes with seem bigger and sparkling. You can apply on your ears, nose... etc.

? You're Shopping @

1:23 AM

?

? Shop till you drop ! ?

Item #01 (IN-Stocks)
Price: S$26 = yours at S$22 (Price slashed!)
Left 1 from spree 1 only.
Nicely pack. Still in the plastic bag.

? You're Shopping @

12:43 AM

? Wednesday, March 19, 2008

? Shop till you drop ! ?

Thanks for viewing, ShOpTituDe-LovEs!
I warmly welcome you all!
Firstly, I will tell you about my working days and hours.
Is like this,
-I will update my blog everyday, to see if i have any taggiies.
-Checking my E-mail every 1 to 2 days.
-Products that sold here will be updated every 1 to 3 weeks.

Yupp. That all. So i hope that you will email to mii if you would like to order from mii.

Opps, some of my goods are IN-stocks, and some are PRE-orders.
((Will be written, no worriies))

Regards
ShOpTituDe-LovEs You have attitude, we have SHOPTITUDE

? You're Shopping @

1:30 AM

kalavathi

W3C Activities | Technical Reports | Site Index | New Visitors | About W3C | Join W3C
W3C Technical Reports and Publications

View by Editor | View by Title | View by Date | View by Activity | Configurable Views

W3C Publications:
Recommendations · Proposed Recommendations · Proposed Edited Recommendations · Candidate Recommendations · Working Drafts · Group Notes · About W3C Technical Reports · Technical Reports FAQ
Related:
Translations of W3C documents · The QA Matrix of W3C specifications · Technical Report Publication Rules · Manual of Style · Member Submissions · Team Submissions · W3J
Member only: Newsletter · NewsWire

Note: Some links previously part of this page have been moved to the page for Team Submissions.
Recently Published Recommendations

* 2 May 2008: Canonical XML Version 1.1
* ...more Recommendations

Recently Published Candidate Recommendations

* 16 May 2008: XQuery and XPath Full Text 1.0 - Candidate Recommendation Feedback Due 15 September 2008
* 30 April 2008: Web Content Accessibility Guidelines 2.0 - Candidate Recommendation Feedback Due 30 June 2008
* ...more Candidate Recommendations

Recently Published Working Drafts

* 16 May 2008: Cascading Style Sheets (CSS) Snapshot 2007 - Last Call Ends 9 June 2008
* 16 May 2008: State Chart XML (SCXML): State Machine Notation for Control Abstraction
* 16 May 2008: XQuery and XPath Full Text 1.0 Requirements
* 16 May 2008: XQuery and XPath Full Text 1.0 Use Cases
* 14 May 2008: Web Accessibility for Older Users: A Literature Review
* 6 May 2008: CURIE Syntax 1.0 - Last Call Ends 10 June 2008
* 1 May 2008: XProc: An XML Pipeline Language
* 30 April 2008: Understanding WCAG 2.0
* 30 April 2008: Techniques for WCAG 2.0
* ... more Working Drafts

Recommendations

A W3C Recommendation is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment of its Recommendations. Note: W3C Recommendations are similar to the standards published by other organizations.

Canonical XML Version 1.1
2 May 2008, Glenn Marcy, John Boyer - (Errata, Translations, Royalty-Free Commitments)
SPARQL Query Results XML Format
15 January 2008, Jeen Broekstra, Dave Beckett - (Errata, Translations, Royalty-Free Commitments)
SPARQL Protocol for RDF
15 January 2008, Lee Feigenbaum, Kendall Grant Clark, Elias Torres - (Errata, Translations, Royalty-Free Commitments)
SPARQL Query Language for RDF
15 January 2008, Andy Seaborne, Eric Prud'hommeaux - (Errata, Translations, Royalty-Free Commitments)
Gleaning Resource Descriptions from Dialects of Languages (GRDDL)
11 September 2007, Dan Connolly - (Errata, Translations, Royalty-Free Commitments)
GRDDL Test Cases
11 September 2007, Chimezie Ogbuji - (Errata, Translations, Royalty-Free Commitments)
Web Services Addressing 1.0 - Metadata
4 September 2007, Martin Gudgin, Ümit Yalçinalp, Tony Rogers, Marc Hadley - (Errata, Translations, Royalty-Free Commitments)
Web Services Policy 1.5 - Framework
4 September 2007, Asir S Vedamuthu, David Orchard, Frederick Hirsch, Maryann Hondo, Prasad Yendluri, Toufic Boubez, Ümit Yalçinalp - (Errata, Translations, Royalty-Free Commitments)
Web Services Policy 1.5 - Attachment
4 September 2007, Asir S Vedamuthu, Toufic Boubez, Frederick Hirsch, Maryann Hondo, David Orchard, Prasad Yendluri, Ümit Yalçinalp - (Errata, Translations, Royalty-Free Commitments)
Semantic Annotations for WSDL and XML Schema
28 August 2007, Joel Farrell, Holger Lausen - (Errata, Translations, Royalty-Free Commitments)
Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language
26 June 2007, Roberto Chinnici, Arthur Ryman, Jean-Jacques Moreau, Sanjiva Weerawarana - (Errata, Translations)
Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts
26 June 2007, David Orchard, Hugo Haas, Sanjiva Weerawarana, Jean-Jacques Moreau, Roberto Chinnici, Amelia A. Lewis - (Errata, Translations)
Web Services Description Language (WSDL) Version 2.0 Part 0: Primer
26 June 2007, David Booth, Canyang Kevin Liu - (Errata, Translations)
Voice Extensible Markup Language (VoiceXML) 2.1
19 June 2007, Matt Oshry, Ken Rehor, Michael Bodell, Paolo Baggia, RJ Auburn, David Burke, Daniel C. Burnett, Emily Candell, Jerry Carter, Scott McGlashan, Alex Lee, Brad Porter - (Errata, Translations, Royalty-Free Commitments)
Semantic Interpretation for Speech Recognition (SISR) Version 1.0
5 April 2007, David Burke, Luc Van Tichelen - (Errata, Translations, Royalty-Free Commitments)
Internationalization Tag Set (ITS) Version 1.0
3 April 2007, Felix Sasaki, Christian Lieske - (Errata, Translations, Royalty-Free Commitments)
WebCGM 2.0
30 January 2007, Benoit Bezaire, David Cruikshank, Lofton Henderson - (Errata, Translations, Royalty-Free Commitments)
XQuery 1.0 and XPath 2.0 Data Model (XDM)
23 January 2007, Ashok Malhotra, Jonathan Marsh, Norman Walsh, Mary Fernández, Marton Nagy - (Errata, Translations, Royalty-Free Commitments)
XQuery 1.0 and XPath 2.0 Functions and Operators
23 January 2007, Jim Melton, Norman Walsh, Ashok Malhotra - (Errata, Translations, Royalty-Free Commitments)
XML Path Language (XPath) 2.0
23 January 2007, Mary F. Fernández, Don Chamberlin, Jérôme Siméon, Anders Berglund, Scott Boag, Jonathan Robie, Michael Kay - (Errata, Translations, Royalty-Free Commitments)
XQuery 1.0: An XML Query Language
23 January 2007, Mary F. Fernández, Scott Boag, Daniela Florescu, Don Chamberlin, Jonathan Robie, Jérôme Siméon - (Errata, Translations, Royalty-Free Commitments)
XQuery 1.0 and XPath 2.0 Formal Semantics
23 January 2007, Peter Fankhauser, Philip Wadler, Ashok Malhotra, Denise Draper, Kristoffer Rose, Michael Rys, Mary Fernández, Jérôme Siméon - (Errata, Translations, Royalty-Free Commitments)
XML Syntax for XQuery 1.0 (XQueryX)
23 January 2007, Subramanian Muralidhar, Jim Melton - (Errata, Translations, Royalty-Free Commitments)
XSLT 2.0 and XQuery 1.0 Serialization
23 January 2007, Henry Zongaro, Michael Kay, Scott Boag, Norman Walsh, Joanne Tong - (Errata, Translations, Royalty-Free Commitments)
XSL Transformations (XSLT) Version 2.0
23 January 2007, Michael Kay - (Errata, Translations, Royalty-Free Commitments)
Extensible Stylesheet Language (XSL) Version 1.1
5 December 2006, Anders Berglund - (Errata, Translations, Royalty-Free Commitments)
XHTML-Print
20 September 2006, Jim Bigelow, Melinda Grant - (Errata, Translations)
Extensible Markup Language (XML) 1.1 (Second Edition)
16 August 2006, François Yergeau, John Cowan, C. M. Sperberg-McQueen, Eve Maler, Tim Bray, Jean Paoli - (Errata, Translations)
Web Services Addressing 1.0 - Core
9 May 2006, Martin Gudgin, Marc Hadley, Tony Rogers - (Errata, Translations, Royalty-Free Commitments)
Web Services Addressing 1.0 - SOAP Binding
9 May 2006, Martin Gudgin, Tony Rogers, Marc Hadley, Martin Gudgin, Marc Hadley, Tony Rogers - (Errata, Translations, Royalty-Free Commitments)
XForms 1.0 (Third Edition)
First published 14 March 2006, revised 29 October 2007, John M. Boyer - (Errata, Translations)
Synchronized Multimedia Integration Language (SMIL 2.1)
13 December 2005, Guido Grassel, Dick Bulterman, Nabil Layaïda, Jack Jansen, Daniel Zucker, Thierry Michel, Sjoerd Mullender, Antti Koivisto - (Translations)
xml:id Version 1.0
9 September 2005, Jonathan Marsh, Norman Walsh, Daniel Veillard - (Errata, Translations, Royalty-Free Commitments)
QA Framework: Specification Guidelines
17 August 2005, Karl Dubost, Lynne Rosenthal, Lofton Henderson, Dominique Hazaël-Massieux - (Errata, Translations, Royalty-Free Commitments)
XML Key Management Specification (XKMS 2.0)
28 June 2005, Shivaram H. Mysore, Phillip Hallam-Baker - (Errata, Translations)
XML Key Management Specification (XKMS 2.0) Bindings
28 June 2005, Shivaram H. Mysore, Phillip Hallam-Baker - (Errata, Translations)
Character Model for the World Wide Web 1.0: Fundamentals
15 February 2005, Martin J. Dürst, Richard Ishida, Misha Wolf, Tex Texin, François Yergeau - (Errata, Translations)
SOAP Message Transmission Optimization Mechanism
25 January 2005, Mark Nottingham, Martin Gudgin, Noah Mendelsohn, Hervé Ruellan - (Errata, Translations)
Resource Representation SOAP Header Block
25 January 2005, Yves Lafon, Anish Karmarkar, Martin Gudgin - (Errata, Translations)
XML-binary Optimized Packaging
25 January 2005, Hervé Ruellan, Mark Nottingham, Noah Mendelsohn, Martin Gudgin - (Errata, Translations)
XML Inclusions (XInclude) Version 1.0 (Second Edition)
First published 20 December 2004, revised 15 November 2006, Jonathan Marsh, David Orchard, Daniel Veillard - (Errata, Translations)
Architecture of the World Wide Web, Volume One
15 December 2004, Norman Walsh, Ian Jacobs - (Errata, Translations)
Speech Synthesis Markup Language (SSML) Version 1.0
7 September 2004, Daniel C. Burnett, Mark R. Walker, Andrew Hunt - (Errata, Translations)
Document Object Model (DOM) Level 3 Core Specification
7 April 2004, Jonathan Robie, Lauren Wood, Gavin Nicol, Steve Byrne, Arnaud Le Hors, Mike Champion, Philippe Le Hégaret - (Errata, Translations)
Document Object Model (DOM) Level 3 Load and Save Specification
7 April 2004, Johnny Stenback, Andy Heninger - (Errata, Translations)
Speech Recognition Grammar Specification Version 1.0
16 March 2004, Andrew Hunt, Scott McGlashan - (Errata, Translations)
Voice Extensible Markup Language (VoiceXML) Version 2.0
16 March 2004, Scott McGlashan, Andrew Hunt, Brad Porter, Daniel C. Burnett, Jim Ferrans, Jerry Carter, Steph Tryphonas, Bruce Lucas, Ken Rehor, Peter Danielsen - (Errata, Translations)
OWL Web Ontology Language Overview
10 February 2004, Deborah L. McGuinness, Frank van Harmelen - (Errata, Translations)
OWL Web Ontology Language Guide
10 February 2004, Michael K. Smith, Chris Welty, Deborah L. McGuinness - (Errata, Translations)
OWL Web Ontology Language Reference
10 February 2004, Guus Schreiber, Mike Dean - (Errata, Translations)
OWL Web Ontology Language Semantics and Abstract Syntax
10 February 2004, Patrick Hayes, Ian Horrocks, Peter F. Patel-Schneider - (Errata, Translations)
OWL Web Ontology Language Test Cases
10 February 2004, Jeremy J. Carroll, Jos De Roo - (Errata, Translations)
Resource Description Framework (RDF): Concepts and Abstract Syntax
10 February 2004, Graham Klyne, Jeremy J. Carroll - (Errata, Translations)
RDF Semantics
10 February 2004, Patrick Hayes - (Errata, Translations)
RDF Primer
10 February 2004, Frank Manola, Eric Miller - (Errata, Translations)
RDF Vocabulary Description Language 1.0: RDF Schema
10 February 2004, Dan Brickley, Ramanathan V. Guha - (Errata, Translations)
RDF/XML Syntax Specification (Revised)
10 February 2004, Dave Beckett - (Errata, Translations)
RDF Test Cases
10 February 2004, Jan Grant, Dave Beckett - (Errata, Translations)
OWL Web Ontology Language Use Cases and Requirements
10 February 2004, Jeff Heflin - (Errata, Translations)
Extensible Markup Language (XML) 1.0 (Fourth Edition)
First published 4 February 2004, revised 16 August 2006, Eve Maler, Jean Paoli, François Yergeau, C. M. Sperberg-McQueen, Tim Bray - (Errata, Translations)
Namespaces in XML 1.1 (Second Edition)
First published 4 February 2004, revised 16 August 2006, Andrew Layman, Richard Tobin, Dave Hollander, Tim Bray - (Errata, Translations)
Document Object Model (DOM) Level 3 Validation Specification
27 January 2004, Ben Chang, Rezaur Rahman, Joe Kesselman - (Errata, Translations)
Composite Capability/Preference Profiles (CC/PP): Structure and Vocabularies 1.0
15 January 2004, Chris Woodrow, Mark H. Butler, Franklin Reynolds, Graham Klyne, Luu Tran, Hidetaka Ohto, Johan Hjelm - (Errata, Translations)
XML Events
14 October 2003, Shane McCarron, T. V. Raman, Steven Pemberton - (Errata, Translations)
SOAP Version 1.2 Part 0: Primer (Second Edition)
First published 24 June 2003, revised 27 April 2007, Yves Lafon, Nilo Mitra - (Errata, Translations)
SOAP Version 1.2 Part 1: Messaging Framework (Second Edition)
First published 24 June 2003, revised 27 April 2007, Anish Karmarkar, Marc Hadley, Henrik Frystyk Nielsen, Martin Gudgin, Noah Mendelsohn, Jean-Jacques Moreau, Yves Lafon - (Errata, Translations)
SOAP Version 1.2 Part 2: Adjuncts (Second Edition)
First published 24 June 2003, revised 27 April 2007, Anish Karmarkar, Jean-Jacques Moreau, Henrik Frystyk Nielsen, Yves Lafon, Martin Gudgin, Marc Hadley, Noah Mendelsohn - (Errata, Translations)
SOAP Version 1.2 Specification Assertions and Test Collection (Second Edition)
First published 24 June 2003, revised 27 April 2007, Jeff Mischkinsky, Mark Jones, Oisin Hurley, Richard Martin, Lynne Thompson, Anish Karmarkar, Hugo Haas - (Errata, Translations)
XPointer element() Scheme
25 March 2003, Jonathan Marsh, Norman Walsh, Paul Grosso, Eve Maler - (Errata, Translations)
XPointer Framework
25 March 2003, Paul Grosso, Norman Walsh, Jonathan Marsh, Eve Maler - (Errata, Translations)
XPointer xmlns() Scheme
25 March 2003, Steven J. DeRose, Eve Maler, Ron Daniel Jr., Jonathan Marsh - (Errata, Translations)
Scalable Vector Graphics (SVG) 1.1 Specification
14 January 2003, Dean Jackson, Jon Ferraiolo, 藤沢淳 - (Errata, Translations)
Mobile SVG Profiles: SVG Tiny and SVG Basic
14 January 2003, Tolga Capin - (Errata, Translations)
Document Object Model (DOM) Level 2 HTML Specification
9 January 2003, Arnaud Le Hors, Philippe Le Hégaret, Johnny Stenback - (Errata, Translations)
User Agent Accessibility Guidelines 1.0
17 December 2002, Jon Gunderson, Eric Hansen, Ian Jacobs - (Errata, Translations)
XML Encryption Syntax and Processing
10 December 2002, Donald Eastlake, Joseph Reagle - (Errata, Translations)
Decryption Transform for XML Signature
10 December 2002, Takeshi Imamura, Hiroshi Maruyama, Merlin Hughes - (Errata, Translations)
XML-Signature XPath Filter 2.0
8 November 2002, Merlin Hughes, Joseph Reagle, John Boyer - (Errata, Translations)
Exclusive XML Canonicalization Version 1.0
18 July 2002, Joseph Reagle, Donald E. Eastlake 3rd, John Boyer - (Errata )
The Platform for Privacy Preferences 1.0 (P3P1.0) Specification
16 April 2002, Massimo Marchiori - (Errata )
XML-Signature Syntax and Processing
12 February 2002, Joseph Reagle, Donald Eastlake, David Solo - (Errata )
XML Information Set (Second Edition)
First published 24 October 2001, revised 4 February 2004, John Cowan, Richard Tobin - (Errata, Translations)
Extensible Stylesheet Language (XSL) Version 1.0
15 October 2001, Anders Berglund, Sharon Adler, Stephen Deach, R. Alexander Milowski, Eduardo Gutentag, Paul Grosso, Tony Graham, Scott Parnell, Jeff Caruso, Jeremy Richman, Steve Zilles - (Errata )
SMIL Animation
4 September 2001, Patrick Schmitz, Aaron Cohen - (Errata )
XML Linking Language (XLink) Version 1.0
27 June 2001, David Orchard, Steven DeRose, Eve Maler - (Errata )
Ruby Annotation
31 May 2001, Masayasu Ishikawa, Michel Suignard, Tex Texin, Marcin Sawicki, Martin Dürst - (Errata )
XHTML™ 1.1 - Module-based XHTML
31 May 2001, Murray Altheim, Shane McCarron - (Errata )
XML Schema Part 0: Primer Second Edition
First published 2 May 2001, revised 28 October 2004, David C. Fallside, Priscilla Walmsley - (Errata, Translations)
XML Schema Part 1: Structures Second Edition
First published 2 May 2001, revised 28 October 2004, Henry S. Thompson, Murray Maloney, David Beech, Noah Mendelsohn - (Errata, Translations)
XML Schema Part 2: Datatypes Second Edition
First published 2 May 2001, revised 28 October 2004, Paul V. Biron, Ashok Malhotra - (Errata, Translations)
Canonical XML Version 1.0
15 March 2001, John Boyer - (Errata )
Mathematical Markup Language (MathML) Version 2.0 (Second Edition)
First published 21 February 2001, revised 21 October 2003, Robert Miner, Patrick Ion, David Carlisle, Nico Poppelier - (

kala

Glossary

Editors
Arnaud Le Hors, IBM
Lauren Wood, SoftQuad Software Inc.
Robert S. Sutor, IBM (for DOM Level 1)

Several of the following term definitions have been borrowed or modified from similar definitions in other W3C or standards documents. See the links within the definitions for more information.

16-bit unit
The base unit of a DOMString. This indicates that indexing on a DOMString occurs in units of 16 bits. This must not be misunderstood to mean that a DOMString can store arbitrary 16-bit units. A DOMString is a character string encoded in UTF-16; this means that the restrictions of UTF-16 as well as the other relevant restrictions on character strings must be maintained. A single character, for example in the form of a numeric character reference, may correspond to one or two 16-bit units.
For more information, see [Unicode] and [ISO/IEC 10646].
ancestor
An ancestor node of any node A is any node above A in a tree model of a document, where "above" means "toward the root."
API
An API is an application programming interface, a set of functions or methods used to access some functionality.
child
A child is an immediate descendant node of a node.
client application
A [client] application is any software that uses the Document Object Model programming interfaces provided by the hosting implementation to accomplish useful work. Some examples of client applications are scripts within an HTML or XML document.
COM
COM is Microsoft's Component Object Model [COM], a technology for building applications from binary software components.
convenience
A convenience method is an operation on an object that could be accomplished by a program consisting of more basic operations on the object. Convenience methods are usually provided to make the API easier and simpler to use or to allow specific programs to create more optimized implementations for common operations. A similar definition holds for a convenience property.
data model
A data model is a collection of descriptions of data structures and their contained fields, together with the operations or functions that manipulate them.
descendant
A descendant node of any node A is any node below A in a tree model of a document, where "above" means "toward the root."
ECMAScript
The programming language defined by the ECMA-262 standard [ECMAScript]. As stated in the standard, the originating technology for ECMAScript was JavaScript [JavaScript]. Note that in the ECMAScript Language binding, the word "property" is used in the same sense as the IDL term "attribute."
element
Each document contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements by an empty-element tag. Each element has a type, identified by name, and may have a set of attributes. Each attribute has a name and a value. See Logical Structures in XML [XML].
information item
An information item is an abstract representation of some component of an XML document. See the [Infoset] for details.
hosting implementation
A [hosting] implementation is a software module that provides an implementation of the DOM interfaces so that a client application can use them. Some examples of hosting implementations are browsers, editors and document repositories.
HTML
The HyperText Markup Language (HTML) is a simple markup language used to create hypertext documents that are portable from one platform to another. HTML documents are SGML documents with generic semantics that are appropriate for representing information from a wide range of applications. [HTML4.0]
inheritance
In object-oriented programming, the ability to create new classes (or interfaces) that contain all the methods and properties of another class (or interface), plus additional methods and properties. If class (or interface) D inherits from class (or interface) B, then D is said to be derived from B. B is said to be a base class (or interface) for D. Some programming languages allow for multiple inheritance, that is, inheritance from more than one class or interface.
interface
An interface is a declaration of a set of methods with no information given about their implementation. In object systems that support interfaces and inheritance, interfaces can usually inherit from one another.
language binding
A programming language binding for an IDL specification is an implementation of the interfaces in the specification for the given language. For example, a Java language binding for the Document Object Model IDL specification would implement the concrete Java classes that provide the functionality exposed by the interfaces.
local name
A local name is the local part of a qualified name. This is called the local part in Namespaces in XML [Namespaces].
method
A method is an operation or function that is associated with an object and is allowed to manipulate the object's data.
model
A model is the actual data representation for the information at hand. Examples are the structural model and the style model representing the parse structure and the style information associated with a document. The model might be a tree, or a directed graph, or something else.
namespace prefix
A namespace prefix is a string that associates an element or attribute name with a namespace URI in XML. See namespace prefix in Namespaces in XML [Namespaces].
namespace URI
A namespace URI is a URI that identifies an XML namespace. Strictly speaking, this actually is a namespace URI reference. This is called the namespace name in Namespaces in XML [Namespaces].
object model
An object model is a collection of descriptions of classes or interfaces, together with their member data, member functions, and class-static operations.
parent
A parent is an immediate ancestor node of a node.
qualified name
A qualified name is the name of an element or attribute defined as the concatenation of a local name (as defined in this specification), optionally preceded by a namespace prefix and colon character. See Qualified Names in Namespaces in XML [Namespaces].
readonly node
A readonly node is a node that is immutable. This means its list of children, its content, and its attributes, when it is an element, cannot be changed in any way. However, a readonly node can possibly be moved, when it is not itself contained in a readonly node.
root node
The root node is the unique node that is not a child of any other node. All other nodes are children or other descendants of the root node.
sibling
Two nodes are siblings if and only if they have the same parent node.
string comparison
When string matching is required, it is to occur as though the comparison was between 2 sequences of code points from the Unicode 3.0 standard [Unicode].
token
An information item such as an XML Name which has been tokenized.
tokenized
The description given to various information items (for example, attribute values of various types, but not including the StringType CDATA) after having been processed by the XML processor. The process includes stripping leading and trailing white space, and replacing multiple space characters by one. See the definition of tokenized type.
well-formed document
A document is well-formed if it is tag valid and entities are limited to single elements (i.e., single sub-trees). See Well-Formed XML Documents in XML [XML].
XML
Extensible Markup Language (XML) is an extremely simple dialect of SGML. The goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML [XML] has been designed for ease of implementation and for interoperability with both SGML and HTML.
XML name
See XML name in the XML specification [XML].
XML namespace
An XML namespace is a collection of names, identified by a URI reference [RFC2396], which are used in XML documents as element types and attribute names. [Namespaces]

previous next contents inde

kala

previous next contents index

13 November, 2000
1. Document Object Model Core

Editors
Arnaud Le Hors, IBM
Gavin Nicol, Inso EPS (for DOM Level 1)
Lauren Wood, SoftQuad, Inc. (for DOM Level 1)
Mike Champion, ArborText (for DOM Level 1 from November 20, 1997)
Steve Byrne, JavaSoft (for DOM Level 1 until November 19, 1997)

Table of contents

* 1.1. Overview of the DOM Core Interfaces
o 1.1.1. The DOM Structure Model
o 1.1.2. Memory Management
o 1.1.3. Naming Conventions
o 1.1.4. Inheritance vs. Flattened Views of the API
o 1.1.5. The DOMString type
o 1.1.6. The DOMTimeStamp type
o 1.1.7. String comparisons in the DOM
o 1.1.8. XML Namespaces
* 1.2. Fundamental Interfaces
o DOMException, ExceptionCode, DOMImplementation, DocumentFragment, Document, Node, NodeList, NamedNodeMap, CharacterData, Attr, Element, Text, Comment
* 1.3. Extended Interfaces
o CDATASection, DocumentType, Notation, Entity, EntityReference, ProcessingInstruction

1.1. Overview of the DOM Core Interfaces

This section defines a set of objects and interfaces for accessing and manipulating document objects. The functionality specified in this section (the Core functionality) is sufficient to allow software developers and web script authors to access and manipulate parsed HTML and XML content inside conforming products. The DOM Core API also allows creation and population of a Document object using only DOM API calls; loading a Document and saving it persistently is left to the product that implements the DOM API.
1.1.1. The DOM Structure Model

The DOM presents documents as a hierarchy of Node objects that also implement other, more specialized interfaces. Some types of nodes may have child nodes of various types, and others are leaf nodes that cannot have anything below them in the document structure. For XML and HTML, the node types, and which node types they may have as children, are as follows:

* Document -- Element (maximum of one), ProcessingInstruction, Comment, DocumentType (maximum of one)
* DocumentFragment -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference
* DocumentType -- no children
* EntityReference -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference
* Element -- Element, Text, Comment, ProcessingInstruction, CDATASection, EntityReference
* Attr -- Text, EntityReference
* ProcessingInstruction -- no children
* Comment -- no children
* Text -- no children
* CDATASection -- no children
* Entity -- Element, ProcessingInstruction, Comment, Text, CDATASection, EntityReference
* Notation -- no children

The DOM also specifies a NodeList interface to handle ordered lists of Nodes, such as the children of a Node, or the elements returned by the getElementsByTagName method of the Element interface, and also a NamedNodeMap interface to handle unordered sets of nodes referenced by their name attribute, such as the attributes of an Element. NodeList and NamedNodeMap objects in the DOM are live; that is, changes to the underlying document structure are reflected in all relevant NodeList and NamedNodeMap objects. For example, if a DOM user gets a NodeList object containing the children of an Element, then subsequently adds more children to that element (or removes children, or modifies them), those changes are automatically reflected in the NodeList, without further action on the user's part. Likewise, changes to a Node in the tree are reflected in all references to that Node in NodeList and NamedNodeMap objects.

Finally, the interfaces Text, Comment, and CDATASection all inherit from the CharacterData interface.
1.1.2. Memory Management

Most of the APIs defined by this specification are interfaces rather than classes. That means that an implementation need only expose methods with the defined names and specified operation, not implement classes that correspond directly to the interfaces. This allows the DOM APIs to be implemented as a thin veneer on top of legacy applications with their own data structures, or on top of newer applications with different class hierarchies. This also means that ordinary constructors (in the Java or C++ sense) cannot be used to create DOM objects, since the underlying objects to be constructed may have little relationship to the DOM interfaces. The conventional solution to this in object-oriented design is to define factory methods that create instances of objects that implement the various interfaces. Objects implementing some interface "X" are created by a "createX()" method on the Document interface; this is because all DOM objects live in the context of a specific Document.

The DOM Level 2 API does not define a standard way to create DOMImplementation objects; DOM implementations must provide some proprietary way of bootstrapping these DOM interfaces, and then all other objects can be built from there.

The Core DOM APIs are designed to be compatible with a wide range of languages, including both general-user scripting languages and the more challenging languages used mostly by professional programmers. Thus, the DOM APIs need to operate across a variety of memory management philosophies, from language bindings that do not expose memory management to the user at all, through those (notably Java) that provide explicit constructors but provide an automatic garbage collection mechanism to automatically reclaim unused memory, to those (especially C/C++) that generally require the programmer to explicitly allocate object memory, track where it is used, and explicitly free it for re-use. To ensure a consistent API across these platforms, the DOM does not address memory management issues at all, but instead leaves these for the implementation. Neither of the explicit language bindings defined by the DOM API (for ECMAScript and Java) require any memory management methods, but DOM bindings for other languages (especially C or C++) may require such support. These extensions will be the responsibility of those adapting the DOM API to a specific language, not the DOM Working Group.
1.1.3. Naming Conventions

While it would be nice to have attribute and method names that are short, informative, internally consistent, and familiar to users of similar APIs, the names also should not clash with the names in legacy APIs supported by DOM implementations. Furthermore, both OMG IDL and ECMAScript have significant limitations in their ability to disambiguate names from different namespaces that make it difficult to avoid naming conflicts with short, familiar names. So, DOM names tend to be long and descriptive in order to be unique across all environments.

The Working Group has also attempted to be internally consistent in its use of various terms, even though these may not be common distinctions in other APIs. For example, the DOM API uses the method name "remove" when the method changes the structural model, and the method name "delete" when the method gets rid of something inside the structure model. The thing that is deleted is not returned. The thing that is removed may be returned, when it makes sense to return it.
1.1.4. Inheritance vs. Flattened Views of the API

The DOM Core APIs present two somewhat different sets of interfaces to an XML/HTML document: one presenting an "object oriented" approach with a hierarchy of inheritance, and a "simplified" view that allows all manipulation to be done via the Node interface without requiring casts (in Java and other C-like languages) or query interface calls in COM environments. These operations are fairly expensive in Java and COM, and the DOM may be used in performance-critical environments, so we allow significant functionality using just the Node interface. Because many other users will find the inheritance hierarchy easier to understand than the "everything is a Node" approach to the DOM, we also support the full higher-level interfaces for those who prefer a more object-oriented API.

In practice, this means that there is a certain amount of redundancy in the API. The Working Group considers the "inheritance" approach the primary view of the API, and the full set of functionality on Node to be "extra" functionality that users may employ, but that does not eliminate the need for methods on other interfaces that an object-oriented analysis would dictate. (Of course, when the O-O analysis yields an attribute or method that is identical to one on the Node interface, we don't specify a completely redundant one.) Thus, even though there is a generic nodeName attribute on the Node interface, there is still a tagName attribute on the Element interface; these two attributes must contain the same value, but the it is worthwhile to support both, given the different constituencies the DOM API must satisfy.
1.1.5. The DOMString type

To ensure interoperability, the DOM specifies the following:

*

Type Definition DOMString

A DOMString is a sequence of 16-bit units.

IDL Definition

valuetype DOMString sequence;

* Applications must encode DOMString using UTF-16 (defined in [Unicode] and Amendment 1 of [ISO/IEC 10646]).
The UTF-16 encoding was chosen because of its widespread industry practice. Note that for both HTML and XML, the document character set (and therefore the notation of numeric character references) is based on UCS [ISO-10646]. A single numeric character reference in a source document may therefore in some cases correspond to two 16-bit units in a DOMString (a high surrogate and a low surrogate).

Note: Even though the DOM defines the name of the string type to be DOMString, bindings may use different names. For example for Java, DOMString is bound to the String type because it also uses UTF-16 as its encoding.

Note: As of August 2000, the OMG IDL specification ([OMGIDL]) included a wstring type. However, that definition did not meet the interoperability criteria of the DOM API since it relied on negotiation to decide the width and encoding of a character.
1.1.6. The DOMTimeStamp type

To ensure interoperability, the DOM specifies the following:

*

Type Definition DOMTimeStamp

A DOMTimeStamp represents a number of milliseconds.

IDL Definition

typedef unsigned long long DOMTimeStamp;

*

Note: Even though the DOM uses the type DOMTimeStamp, bindings may use different types. For example for Java, DOMTimeStamp is bound to the long type. In ECMAScript, TimeStamp is bound to the Date type because the range of the integer type is too small.

1.1.7. String comparisons in the DOM

The DOM has many interfaces that imply string matching. HTML processors generally assume an uppercase (less often, lowercase) normalization of names for such things as elements, while XML is explicitly case sensitive. For the purposes of the DOM, string matching is performed purely by binary comparison of the 16-bit units of the DOMString. In addition, the DOM assumes that any case normalizations take place in the processor, before the DOM structures are built.

Note: Besides case folding, there are additional normalizations that can be applied to text. The W3C I18N Working Group is in the process of defining exactly which normalizations are necessary, and where they should be applied. The W3C I18N Working Group expects to require early normalization, which means that data read into the DOM is assumed to already be normalized. The DOM and applications built on top of it in this case only have to assure that text remains normalized when being changed. For further details, please see [Charmod].
1.1.8. XML Namespaces

The DOM Level 2 supports XML namespaces [Namespaces] by augmenting several interfaces of the DOM Level 1 Core to allow creating and manipulating elements and attributes associated to a namespace.

As far as the DOM is concerned, special attributes used for declaring XML namespaces are still exposed and can be manipulated just like any other attribute. However, nodes are permanently bound to namespace URIs as they get created. Consequently, moving a node within a document, using the DOM, in no case results in a change of its namespace prefix or namespace URI. Similarly, creating a node with a namespace prefix and namespace URI, or changing the namespace prefix of a node, does not result in any addition, removal, or modification of any special attributes for declaring the appropriate XML namespaces. Namespace validation is not enforced; the DOM application is responsible. In particular, since the mapping between prefixes and namespace URIs is not enforced, in general, the resulting document cannot be serialized naively. For example, applications may have to declare every namespace in use when serializing a document.

DOM Level 2 doesn't perform any URI normalization or canonicalization. The URIs given to the DOM are assumed to be valid (e.g., characters such as whitespaces are properly escaped), and no lexical checking is performed. Absolute URI references are treated as strings and compared literally. How relative namespace URI references are treated is undefined. To ensure interoperability only absolute namespace URI references (i.e., URI references beginning with a scheme name and a colon) should be used. Note that because the DOM does no lexical checking, the empty string will be treated as a real namespace URI in DOM Level 2 methods. Applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

Note: In the DOM, all namespace declaration attributes are by definition bound to the namespace URI: "http://www.w3.org/2000/xmlns/". These are the attributes whose namespace prefix or qualified name is "xmlns". Although, at the time of writing, this is not part of the XML Namespaces specification [Namespaces], it is planned to be incorporated in a future revision.

In a document with no namespaces, the child list of an EntityReference node is always the same as that of the corresponding Entity. This is not true in a document where an entity contains unbound namespace prefixes. In such a case, the descendants of the corresponding EntityReference nodes may be bound to different namespace URIs, depending on where the entity references are. Also, because, in the DOM, nodes always remain bound to the same namespace URI, moving such EntityReference nodes can lead to documents that cannot be serialized. This is also true when the DOM Level 1 method createEntityReference of the Document interface is used to create entity references that correspond to such entities, since the descendants of the returned EntityReference are unbound. The DOM Level 2 does not support any mechanism to resolve namespace prefixes. For all of these reasons, use of such entities and entity references should be avoided or used with extreme care. A future Level of the DOM may include some additional support for handling these.

The new methods, such as createElementNS and createAttributeNS of the Document interface, are meant to be used by namespace aware applications. Simple applications that do not use namespaces can use the DOM Level 1 methods, such as createElement and createAttribute. Elements and attributes created in this way do not have any namespace prefix, namespace URI, or local name.

Note: DOM Level 1 methods are namespace ignorant. Therefore, while it is safe to use these methods when not dealing with namespaces, using them and the new ones at the same time should be avoided. DOM Level 1 methods solely identify attribute nodes by their nodeName. On the contrary, the DOM Level 2 methods related to namespaces, identify attribute nodes by their namespaceURI and localName. Because of this fundamental difference, mixing both sets of methods can lead to unpredictable results. In particular, using setAttributeNS, an element may have two attributes (or more) that have the same nodeName, but different namespaceURIs. Calling getAttribute with that nodeName could then return any of those attributes. The result depends on the implementation. Similarly, using setAttributeNode, one can set two attributes (or more) that have different nodeNames but the same prefix and namespaceURI. In this case getAttributeNodeNS will return either attribute, in an implementation dependent manner. The only guarantee in such cases is that all methods that access a named item by its nodeName will access the same item, and all methods which access a node by its URI and local name will access the same node. For instance, setAttribute and setAttributeNS affect the node that getAttribute and getAttributeNS, respectively, return.
1.2. Fundamental Interfaces

The interfaces within this section are considered fundamental, and must be fully implemented by all conforming implementations of the DOM, including all HTML DOM implementations [DOM Level 2 HTML], unless otherwise specified.

A DOM application may use the hasFeature(feature, version) method of the DOMImplementation interface with parameter values "Core" and "2.0" (respectively) to determine whether or not this module is supported by the implementation. Any implementation that conforms to DOM Level 2 or a DOM Level 2 module must conform to the Core module. Please refer to additional information about conformance in this specification.

Exception DOMException

DOM operations only raise exceptions in "exceptional" circumstances, i.e., when an operation is impossible to perform (either for logical reasons, because data is lost, or because the implementation has become unstable). In general, DOM methods return specific error values in ordinary processing situations, such as out-of-bound errors when using NodeList.

Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if a null argument is passed.

Some languages and object systems do not support the concept of exceptions. For such systems, error conditions may be indicated using native error reporting mechanisms. For some bindings, for example, methods may return error codes similar to those listed in the corresponding method descriptions.

IDL Definition

exception DOMException {
unsigned short code;
};
// ExceptionCode
const unsigned short INDEX_SIZE_ERR = 1;
const unsigned short DOMSTRING_SIZE_ERR = 2;
const unsigned short HIERARCHY_REQUEST_ERR = 3;
const unsigned short WRONG_DOCUMENT_ERR = 4;
const unsigned short INVALID_CHARACTER_ERR = 5;
const unsigned short NO_DATA_ALLOWED_ERR = 6;
const unsigned short NO_MODIFICATION_ALLOWED_ERR = 7;
const unsigned short NOT_FOUND_ERR = 8;
const unsigned short NOT_SUPPORTED_ERR = 9;
const unsigned short INUSE_ATTRIBUTE_ERR = 10;
// Introduced in DOM Level 2:
const unsigned short INVALID_STATE_ERR = 11;
// Introduced in DOM Level 2:
const unsigned short SYNTAX_ERR = 12;
// Introduced in DOM Level 2:
const unsigned short INVALID_MODIFICATION_ERR = 13;
// Introduced in DOM Level 2:
const unsigned short NAMESPACE_ERR = 14;
// Introduced in DOM Level 2:
const unsigned short INVALID_ACCESS_ERR = 15;

Definition group ExceptionCode

An integer indicating the type of error generated.

Note: Other numeric codes are reserved for W3C for possible future use.

Defined Constants

DOMSTRING_SIZE_ERR
If the specified range of text does not fit into a DOMString
HIERARCHY_REQUEST_ERR
If any node is inserted somewhere it doesn't belong
INDEX_SIZE_ERR
If index or size is negative, or greater than the allowed value
INUSE_ATTRIBUTE_ERR
If an attempt is made to add an attribute that is already in use elsewhere
INVALID_ACCESS_ERR, introduced in DOM Level 2.
If a parameter or an operation is not supported by the underlying object.
INVALID_CHARACTER_ERR
If an invalid or illegal character is specified, such as in a name. See production 2 in the XML specification for the definition of a legal character, and production 5 for the definition of a legal name character.
INVALID_MODIFICATION_ERR, introduced in DOM Level 2.
If an attempt is made to modify the type of the underlying object.
INVALID_STATE_ERR, introduced in DOM Level 2.
If an attempt is made to use an object that is not, or is no longer, usable.
NAMESPACE_ERR, introduced in DOM Level 2.
If an attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
NOT_FOUND_ERR
If an attempt is made to reference a node in a context where it does not exist
NOT_SUPPORTED_ERR
If the implementation does not support the requested type of object or operation.
NO_DATA_ALLOWED_ERR
If data is specified for a node which does not support data
NO_MODIFICATION_ALLOWED_ERR
If an attempt is made to modify an object where modifications are not allowed
SYNTAX_ERR, introduced in DOM Level 2.
If an invalid or illegal string is specified.
WRONG_DOCUMENT_ERR
If a node is used in a different document than the one that created it (that doesn't support it)

Interface DOMImplementation

The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model.

IDL Definition

interface DOMImplementation {
boolean hasFeature(in DOMString feature,
in DOMString version);
// Introduced in DOM Level 2:
DocumentType createDocumentType(in DOMString qualifiedName,
in DOMString publicId,
in DOMString systemId)
raises(DOMException);
// Introduced in DOM Level 2:
Document createDocument(in DOMString namespaceURI,
in DOMString qualifiedName,
in DocumentType doctype)
raises(DOMException);
};

Methods

createDocument introduced in DOM Level 2
Creates an XML Document object of the specified type with its document element. HTML-only DOM implementations do not need to implement this method.
Parameters

namespaceURI of type DOMString
The namespace URI of the document element to create.
qualifiedName of type DOMString
The qualified name of the document element to be created.
doctype of type DocumentType
The type of document to be created or null.
When doctype is not null, its Node.ownerDocument attribute is set to the document being created.

Return Value

Document

A new Document object.
Exceptions

DOMException

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NAMESPACE_ERR: Raised if the qualifiedName is malformed, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" [Namespaces].

WRONG_DOCUMENT_ERR: Raised if doctype has already been used with a different document or was created from a different implementation.
createDocumentType introduced in DOM Level 2
Creates an empty DocumentType node. Entity declarations and notations are not made available. Entity reference expansions and default attribute additions do not occur. It is expected that a future version of the DOM will provide a way for populating a DocumentType.
HTML-only DOM implementations do not need to implement this method.
Parameters

qualifiedName of type DOMString
The qualified name of the document type to be created.
publicId of type DOMString
The external subset public identifier.
systemId of type DOMString
The external subset system identifier.

Return Value

DocumentType

A new DocumentType node with Node.ownerDocument set to null.
Exceptions

DOMException

INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character.

NAMESPACE_ERR: Raised if the qualifiedName is malformed.
hasFeature
Test if the DOM implementation implements a specific feature.
Parameters

feature of type DOMString
The name of the feature to test (case-insensitive). The values used by DOM features are defined throughout the DOM Level 2 specifications and listed in the Conformance section. The name must be an XML name. To avoid possible conflicts, as a convention, names referring to features defined outside the DOM specification should be made unique by reversing the name of the Internet domain name of the person (or the organization that the person belongs to) who defines the feature, component by component, and using this as a prefix. For instance, the W3C SVG Working Group defines the feature "org.w3c.dom.svg".
version of type DOMString
This is the version number of the feature to test. In Level 2, the string can be either "2.0" or "1.0". If the version is not specified, supporting any version of the feature causes the method to return true.

Return Value

boolean

true if the feature is implemented in the specified version, false otherwise.
No Exceptions

Interface DocumentFragment

DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object.

Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node.

The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document.

When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node. This makes the DocumentFragment very useful when the user wishes to create nodes that are

kalavathi

Wednesday, May 21, 2008

kalavathi

kalavathi

kalavathi

kalavathi

kalavathi

kalavathi

kalavathi

kalavathi

kala

kala

Blog Archive

About Me