[Ngoid-dev] Re: Ngoid-dev digest, Vol 1 #6 - 2 msgs

[Chris M. <cm...@ob...>]

Have you guys ever heard of Lore?   It's an experimental XML database management system
from Stanford University... it let's you browse, search, and query XML databases (like
NGOID).. it allows you to take an XML stream from any source including URLs (it says)..

check it out... http://www-db.stanford.edu/lore

ngo...@li... wrote:

> Send Ngoid-dev mailing list submissions to
>         ngo...@li...
>
> To subscribe or unsubscribe via the web, visit
>         http://lists.sourceforge.net/mailman/listinfo/ngoid-dev
> or, via email, send a message with subject or body 'help' to
>         ngo...@li...
> You can reach the person managing the list at
>         ngo...@li...
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of Ngoid-dev digest..."
>
> Today's Topics:
>
>   1. Indexing Criteria for Job Posting Service on this directory (he...@i3...)
>   2. Re: Indexing Criteria for Job Posting Service on this directory (Ashvil)
>
> --__--__--
>
> Message: 1
> From: he...@i3...
> Date: Mon, 15 May 2000 22:19:15 -0700 (PDT)
> To: ngo...@so...
> Subject: [Ngoid-dev] Indexing Criteria for Job Posting Service on this directory
>
> Hello,
>
> As per my previous posting, I am working on defining a structure for a sample
> application for Job posting that can be build on top of NGOID directory. I
> have been doing some research and trying to identify minimum indexing
> criteria that should allow companies to identify job requirements and should
> be relatively easy enough for NGOID developers to build an initial sample app
> on top.
> Following is the representation of the minimum indexing criteria that I am
> proposing. I would really appreciate any help and feedback from the community.
>
> Indexing Criteria: These are the fields that the publishing entity (users)
> must provide information to in order for them to list jobs that can be
> indexed and search by the application providers. Indexing criteria is a group
> of fields that is part of info.xml
>
> Following is the simplistic view of indexing fields that I think we need to
> go ahead with in order to develop a job posting app that can be used by
> business entities.
>
> Idexing Categories for Job Posting application:
>
> I have tried to identify three different sets of indexing criterias. All
> three are fairly important. The challange here is to choose one or two
> simplistic criterias for the sample application. But, this choise should not
> restrict the future flexibility of searching. As indexing strategy would have
> an impact on search mechanism and flexibility.
> I think the indexing criteria must be a combination of
> 1) Job Category (Industry, Job Function, Sub Funbction etc.)
> 2) Geographical Location
> 3) Free Key words (Weighted key words that can be used in free form to
> provide ultimate flexibility in defining the job and search criteria)
>
> 1 and 2 are relatively easy to define and implement, but number 3 (keyword
> based) indexing scheme is the most critical and difficult to do.
> Please review the following structure and advise if I am on the right track.
> Please keep in mind, this excercise is a quick one in order to get some
> sample demo app out there to demonstrate directory's vision.
> We must then extend these definition and info.xml 'service' micro schemas to
> support robust applications.
>
> Info.Xml
>
> <Identification Information> (Optional or Mendatory.. please refer to
> info.xml)
> </Identification Information>
>
> #Indexing Information: Index #1
> <Category>
>         example (Advertising / Marketing, Information Technology, Computer
>         SOftware, Accounting etc.)
>        <Sub Category>
>               These can  be defined by domain experts. We should explode
>               atleast one domain for example (I would do IT domain)
>        </Sub Category>
> </Category>
>
> #Indexing Information: Index #2
> <Country>
>     <State/Province>
>          <Location>
>            example (US-California-Silicon Valley, Work From Home, Travel etc.)
>            Other data fields that must be on the service (micro schema)are
>          </Location>
>     </State/Province>
> </Country>
>
> #Indexing Information: Index #3
> <Keyword>
>     <Weightage>
>     </Weightage>
> </Keyword>
> <Keyword>
>     <Weightage>
>     </Weightage>
> </Keyword>
> <Keyword>
>     <Weightage>
>     </Weightage>
> </Keyword>
>
> # Other Qualifying fields (Not part of an index)
> <Job Level> (Entry Level, 2+ Years, 5 + Years, Mid Career, Executive)
> </ Job Level>
>
> <City>
> </City>
>
> <Job Title>
> </Job Title>
>
> <Posittion Type>
>             Fill TIme, Part Time, ContrACT etc.
> </Posittion Type>
>
> <More...> Need more input....
>
> Thank you,
> Hemant Asher
> NGOID Member
>
> --__--__--
>
> Message: 2
> Date: Tue, 16 May 2000 11:27:27 -0700 (PDT)
> To: ngo...@so...
> Subject: Re: [Ngoid-dev] Indexing Criteria for Job Posting Service on this directory
> From: Ashvil <as...@i3...>
>
> he...@i3... said:
> > I think the indexing criteria must be a combination of
> > 1) Job Category (Industry, Job Function, Sub Funbction etc.)
> > 2) Geographical Location
> > 3) Free Key words (Weighted key words that can be used in free
> form to
> > provide ultimate flexibility in defining the job and search
> criteria)
> >
> > 1 and 2 are relatively easy to define and implement, but number 3
> (keyword
> > based) indexing scheme is the most critical and difficult to do.
>
> There is an article written on inverted indexing
> http://hotwired.lycos.com/webmonkey/code/97/16/index2a.html
>
> The database used is Open Source. However, it looks like it had
> Perl interfaces and the sample of the article is in Perl. Since
> SourceForge supports PHP, we may need someone to port the Perl code
> over to PHP.
> http://www.sleepycat.com/
>
> I think if we use a combination of hierarchial indexes and inverted
> indexes along with issue of the context of the XML element, we
> should have a killer search/indexing capability.
>
> Regards,
> Ashvil
>
> --__--__--
>
> _______________________________________________
> Ngoid-dev mailing list
> Ngo...@li...
> http://lists.sourceforge.net/mailman/listinfo/ngoid-dev
>
> End of Ngoid-dev Digest