[Rets-dev] Why XML?

[Jeff Brush]

So your simpler solution is to use XML Schema to implement the metadata.
I was hoping for a little more detail.

You are an MLS.
How do I determine which standard payloads do you have available?
Which fields/elements do you allow searches on?
Do I scan the NAR hosted, RETS standard schema annotations for element
descriptions of my local data?
If a lightweight RETS IDX payload is defined next year how hard is it to
add to your server? How do I query on it?
Is delimited/compact format allowed?


> -----Original Message-----
> From: Matt Lavallee [mailto:matt at mattL.com] 
> Sent: Friday, August 03, 2007 1:18 PM
> To: 'Jeff Brush'; rets-dev at rets.org
> Subject: RE: [Rets-dev] Why XML?
> 
> On Friday, August 03, 2007 at 10:34 AM, Jeff Brush wrote:
> 
> > > As I said previously, I
> > > can understand consideration in non-standard uses, but I 
> think this 
> > > can be achieved in a simpler manner than multiple metadata tiers.
> > 
> > Could you elaborate on a simpler solution and let the community 
> > comment?
> 
> Sure, allow me to quote the W3C:
> 
> 	XML Schemas express shared vocabularies and allow
> 	machines to carry out rules made by people. They
> 	provide a means for defining the structure, content
> 	and semantics of XML documents in more detail.
> 
> As I joked in my meta-meta comment, we're using Schema (a 
> data description
> language) to outline our own data description language.
> 
> Why is Schema somehow good enough for the standard payloads 
> (which are rich and include annotations), but not good enough 
> for the secret local data that doesn't conform to any current payload?
> 
> -Matt
> 
> 
>