Comments on: KML in Google Maps and the challenge of standards http://blog.oroup.com/2006/12/27/kml-in-google-maps-and-the-challenge-of-standards/ Technology | Politics | Culture Wed, 19 Nov 2008 14:53:17 +0000 http://wordpress.org/?v=2.5.1 By: rkumar http://blog.oroup.com/2006/12/27/kml-in-google-maps-and-the-challenge-of-standards/#comment-16 rkumar Sat, 10 Feb 2007 09:19:18 +0000 http://blog.oroup.com/2006/12/27/kml-in-google-maps-and-the-challenge-of-standards/#comment-16 I disagree regarding xAL. There are data quality products that have implemented the complete specifications of xAL. 10 mb is not the size of one standard namely, xAL. OASIS CIQ has 5 standards, xAL for international address representation, xNL to represent party names, xNAL is a combination of name and address, xCIL to represent party centric information and xCRL to represent party relationships. 10 MG consists of schemas, several examples and many different documents. Complaining about a standard without understanding in detail is not fair. Because xAL is industry and application neutral, it provides the flexibility to end users to have a clear idea of how they want to implement and this is why the statement, "xAL can be used to define addresses in simple terms or in complex terms. It is up to the user to decide how they want to implement xAL." was introduced and should not be taken out of context. If Google Earth decided to implement xAL, then it is clear that xAL provides the fleibility to represent addresses of earth compared to other standards. Cheers I disagree regarding xAL. There are data quality products that have implemented the complete specifications of xAL. 10 mb is not the size of one standard namely, xAL. OASIS CIQ has 5 standards, xAL for international address representation, xNL to represent party names, xNAL is a combination of name and address, xCIL to represent party centric information and xCRL to represent party relationships. 10 MG consists of schemas, several examples and many different documents. Complaining about a standard without understanding in detail is not fair. Because xAL is industry and application neutral, it provides the flexibility to end users to have a clear idea of how they want to implement and this is why the statement, “xAL can be used to define addresses in simple terms or in complex terms. It is up to the user to decide how they want to implement xAL.” was introduced and should not be taken out of context.

If Google Earth decided to implement xAL, then it is clear that xAL provides the fleibility to represent addresses of earth compared to other standards.

Cheers

]]>