Namespaces XML data has to be exchanged between organizations Same tag name may have different meaning in different organizations, causing confusion on exchanged documents Specifying a unique string as an element name avoids confusion Better solution:use unique-name:element-name Avoid using long unique names all over document by using XML Namespaces <university xmIns:yale="http://www.yale.edu"> <yale:course> <yale:course id>CS-101 </yale:course id> <yale:title>Intro.to Computer Science</yale:title> <yale:dept_name>Comp.Sci.</yale:dept_name> <yale:credits>4 </yale:credits> </yale:course> </university> Database System Concepts-6th Edition 23.14 @Silberschatz,Korth and SudarshanDatabase System Concepts - 6 23.14 ©Silberschatz, Korth and Sudarshan th Edition Namespaces XML data has to be exchanged between organizations Same tag name may have different meaning in different organizations, causing confusion on exchanged documents Specifying a unique string as an element name avoids confusion Better solution: use unique-name:element-name Avoid using long unique names all over document by using XML Namespaces <university xmlns:yale=“http://www.yale.edu”> … <yale:course> <yale:course_id> CS-101 </yale:course_id> <yale:title> Intro. to Computer Science</yale:title> <yale:dept_name> Comp. Sci. </yale:dept_name> <yale:credits> 4 </yale:credits> </yale:course> … </university>