[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
KML is very extensible ... but why?
- From: "Costello, Roger L." <costello@mitre.org>
- To: "xml-dev@lists.xml.org" <xml-dev@lists.xml.org>
- Date: Fri, 20 Apr 2018 16:59:57 +0000
Hi Folks,
The format of KML 2.3 documents are specified with a W3C 1.1 XML Schema. XML Schema 1.1 has a powerful feature which KML
uses. At the top of the KML schema is this:
<defaultOpenContent mode="interleave">
<any namespace="##other" processContents="lax"/>
</defaultOpenContent>
Read as: "KML documents are open. That is, XML elements from any non-KML namespace can be inserted before and after every element in KML documents.
Those non-KML elements do not have to validate against any schema."
That makes KML very extensible.
But why?
If I add non-KML stuff in a KML instance, who’s going to understand my stuff? Google Earth? No. Google Maps? No. NASA WorldWind? No.
Only applications that have been custom-coded to understand my stuff will be able to do anything with it. Right? Doesn’t that destroy KML as a global
geographic annotation/visualization language since now you’ve got all these non-interoperable dialects floating around?
Thoughts?
/Roger
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
RSS 2.0 |
|
Atom 0.3 |
|
|
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|