[Rets-dev] RETS2 Vote tomorrow

[Steve Clarke]

I still would like further clarification on:

 

R0043 -  all fields in vocabulary MUST be searchable.

 

 

The current spec candidate does not consider the possibility that a
field may be displayable but not searchable.  A query that includes
selected output may still need to refer to such fields (in the select
clause), even though they are technically not searchable.  However, on
page 616, the RC4 spec does state (about a vocabulary):

 

The Fields element contains searchable Fields that may be used to
construct a query.

 

I would interpret "Fields that may be used to construct a query" as
fields that can be used in either the "select" portion or the "where"
portion of a search request.   In my mind, that makes R0043 a little
misleading.  I would recommend we restate:

 

R0043 -  all fields in vocabulary MUST be Fields that are available to
construct a query.

 

If we do decide to take a stricter definition of what the term
"searchable" means in R0043, then does that mean that non-searchable
(display only) fields MAY NOT be used in the select portion of a query?
Or does it mean that the fields in the select portion of a search
request are not required to be in the vocabulary at all?

 

Smc

 

-----Original Message-----
From: rets-dev-bounces at rets.org [mailto:rets-dev-bounces at rets.org] On
Behalf Of Paul Stusiak
Sent: Tuesday, May 16, 2006 10:04 AM
To: rets-dev at rets.org
Subject: [Rets-dev] RETS2 Vote tomorrow

 

An email vote will be held tomorrow, open to all rets-dev subscribers as
of

April 13th, 2006 and attendees of the April 12 - 14 meeting in
Washington, DC

for those who attended but are not subscribed to the RETS-DEV mail list

 

The question to be voted on is "A vote to remove the Release Candidate

designation from the RETS 2 Service document, wsdl and RETS 2 Service
schema and

make these documents the final version of the RETS 2 specification."

 

The current release of the document is FC4 and represents changes from
the FC2

document of the meeting. Changes have been of the nature of
clarifications in

the majority, based on feedback from the community after the April 13th
meeting.

A couple of additional requirements have been added as well as a couple
of

extension points.  Change bars are on the document. I have a few more
minor

changes that have come in during the last day that should be
clarifications

only. I will try to get these done during today.

 

The current document, FC4 is on www.ftc2.com.

 

The voting process is straight-forward:

 

In favor of the motion:

 

Send mail to RETS2yes at rets.org (mailto:RETS2yes at rets.org)

 

Against the motion:

 

Send mail to RETS2no at rets.org (mailto:RETS2no at rets.org)

 

Voting will be open from 12AM EDT Wednesday, May 17th, 2006 to 11:59 PM
PDT

Wednesday, May 17th, 2006.

 

I'll tally up the votes sometime on Thursday and publish the results to
the

rets-dev list.

 

A supermajority yes vote means that the most current document will be
the final

document. Changes to the document will follow the change process.

 

Less than a supermajority yes vote will mean that the RETS 2 standard
will

remain at the current document release candidate status until the August
meeting

when we will take this vote again.

 

Please let me know if you have any questions.

 

Paul

-----------

Paul Stusiak,

President,

Falcon Technologies Corp.

_______________________________________________

Rets-dev mailing list

Rets-dev at rets.org

http://lists.rets.org/mailman/listinfo/rets-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20060516/10631462/attachment.html