OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

humanmarkup-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: HM.applications-Translations


> Mark Brownell wrote:
> > How about a selection option by the user to do a culturally equivalent
> > procedure in the search instructions. 
> 
> Am I oversimplifying if I would suggest +".se" to be such an
> instruction? .se itself is of course not a cultural instruction, but
> rather a filter that I know will make the search more interesting to me.
> .se for me just mean that the probability that it will be something from
> my culture is much greater than if I put .com in there. It's just a bad
> example, and as such I can put whatever I want into it. Seriously, do I
> understand this discussion correct if I understand it as sending a
> cultural profile to the search engine it would give me the results based
> on this? It would mean that I can search on turkish things using a
> turkish cultural profile.
> 
> Cheers,
> /Niclas

I'm always tinkering with the machine or at least trying to think of ways to do things. 
So I would first think of a simplification mechanism for the user of that search engine 
as a first solution. So I see options that the user can use to trigger SQL instruction 
that are then sent to the online database. The user never sees the complexity of the 
SQL yet through a more human readable interface adds cultural conditionality to the 
search engine's function. Now I'm thinking of data located in databases on a server 
somewhere, that when queried, has the ability to return information in the form that 
the machine request it in.  So this search engine can have several input capabilities 
that predefine the results that it will return. I hoping for a stack of MTML formatted 
RDF Dublin Core styled portal objects that I can run in the sub-browser and run 
relational text gathering queries for final results. I'm trying to build a system that 
works partly on the server and partly on the computer that the user is using. My goal 
here is to achieve speed and archiving at the same time. 

Mark



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC