1 / 13

Update Workgroup

Update Workgroup. December 8 th , 2004 Scottsdale, AZ. Agenda. Implementation report Discussion Update for RETS 2.0 Discussion Update metadata schema. Implementation Report - 1. Currently team is working on an open Update Transaction implementation

castor-rivas
Download Presentation

Update Workgroup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Update Workgroup December 8th, 2004 Scottsdale, AZ

  2. Agenda • Implementation report • Discussion • Update for RETS 2.0 • Discussion • Update metadata schema

  3. Implementation Report - 1 • Currently team is working on an open Update Transaction implementation • Open refers to the requirement that the transaction works with any RETS compliant update client

  4. Implementation Report - 2 • During the design of this transaction, several issues arose that were resolved by extending the existing transaction • The extensions were grouped into three areas

  5. Implementation Report – 3 • Area 1: • Select for Update (Search Transaction) • Target records are “checked out” of the system • Area 2: • Layout Hinting (Metadata, GetMetadata) • Layout of clients is hinted through column grouping

  6. Implementation Report - 4 • Area 3: • Rules Engine (Metadata, GetMetadata) • Existing Rules implementation and additional rule creation

  7. Implementation Report – 5 • Select for Update • What is the reasoning behind this choice? • Prevent multiple updates on same record • Why does it belong in the specification? • Communicates this need to users • Resolves server checking of overwrites.

  8. Implementation Report - 6 • Layout Hinting • Column groups provide dynamic clients the ability to use the grouping information to layout displays • Optional for the client to use • Provides logical grouping of columns • Example is Address – tell the client which columns belong together

  9. Implementation Report - 7 • Layout Hinting (continued -2-) • Can be used by dynamic clients for search based systems as well • Specification currently does not provide any mechanism to make such suggestions

  10. Implementation Report - 8 • Rules Engine • Implementation of the rules currently defined in the metadata • Existing situation is wide open to interpretation. • Missing BNF grammar in current specification • Used as a working example the BNF submitted by MarketLinx • Required minor modifications to BNF to work with certain parser generators

  11. Implementation Report - 9 • Rules Engine (continued -2-) • MarketLinx BNF has extensions that did not appear to be needed. • Also had extensions that could have obvious application – example is functions

  12. Implementation Report - 10 • Rules Engine (continued -3-) • Missing certain additional extensions – example is concatenation • Not clear if string literals should be quoted. Would be good to do.

  13. Agenda • Implementation report • Discussion • Update for RETS 2.0 • Discussion • Update metadata schema

More Related