[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: maps

• To: "Kohsuke Kawaguchi" <kk@k...>
• Subject: RE: maps
• From: "Dare Obasanjo" <dareo@m...>
• Date: Tue, 6 Aug 2002 08:42:10 -0700
• Cc: "J. David Eisenberg" <catcode@c...>,"Simon St.Laurent" <simonstl@s...>,<xml-dev@l...>
• Thread-index: AcI9Xej94GtUpUjqSqGRLHmF3WVFJQAAUgDk
• Thread-topic: maps

So basically I can write code for how to validate a datatype which plugs into the validator depending on whether the validator is designed in such a modular manner and knows where to look for my code? 
 
So for some cases, it isn't as bad as having to hack the validator yourself but it's still doesn't interoperate very well. 

	-----Original Message----- 
	From: Kohsuke Kawaguchi [mailto:kk@k...] 
	Sent: Tue 8/6/2002 8:28 AM 
	To: Dare Obasanjo 
	Cc: J. David Eisenberg; Simon St.Laurent; xml-dev@l... 
	Subject: Re: maps
	
	


	> How does RELAX NG provide a mechanism for specifying operations on these
	> datatypes? It would be easy enough to specify the lexical form of
	> longitudes and latitudes then place them in a publically accessible XSD
	> file but it would be useless since there would be no language for
	> specifying value space relationships in the schema.
	
	Each datatype can define a set of "parameters." So a datatype can define
	range facets by itself, then it can just reject anything that falls out
	of that range. Everything is up to datatypes.
	
	
	> For instance how would one specify what the semantics of maxInclusive,
	> minExclusive, maxExclusive, minInclusive, etc should be?
	
	See attached zip file for an example. This "hex" datatype validates
	hexadecimal digits, and it comes with the "max" and "min" facets which
	allow you to restrict a range.
	
	
	regards,
	----------------------
	Kohsuke Kawaguchi
	E-Mail: kk@k...
	

• Follow-Ups:
  • Re: RE: maps
    • From: John Cowan <jcowan@r...>

• Prev by Date: XML stylesheet web service
• Next by Date: DOM L3 views.idl question
• Previous by thread: Re: Re: maps
• Next by thread: Re: RE: maps
• Index(es):
  • Date
  • Thread