Re: HM.applications-Translations

[Mark Brownell <gizmotron@earthlink.net>]

----- Original Message ----- 
From: Sean B. Palmer 
> > [...] I mean an equivalent consideration for the Sierra
> > Madre in Mexico could also be a cultural fit for this
> > element value. So how do you get machines to draw
> > the connection?
> 
> You could have a profile for the document that explains the cultural
> connections of the author, and then augment the data within the instance
> according to that profile upon delivery to the user.
> 
> The way you'd do it using RDF annotations is probably to assign a context
> to the document, and then have an anonymous node with a lexical value
> representing the "Sierras".
> 

Hi Sean,

That's exactly what I've been thinking. Only I'm searching for simplicity.

>    [ :lexVal "Sierra" ] .
> 
> Then, when you take into account something like:-
> 
>    [ :authorOf this; :nationality :Mexican ] .
> 
> You can conclude that:-
> 
>    [ :lexVal "Sierra" ] :probablyMeansInThisContext
>      [ :lexVal "Sierra Madre" ] .
> 

All of this type of markup could be used to drive a SQL query of a database. What's 
interesting here is that these alternatives would not even exist in the database but would 
be transformed somehow at the time that the results were reported. It's like a layer that 
exists between the database and the user. Interesting choice. It also looks like it could work 
as an OOPs namespace, overloading class method type of a thing running in the big brain.

Is this a new framework for some specified computer language? It looks like you are creating 
a method for every known possibility of knowledge.

> Or whatever. You'd need a rulebase containing FOPL statements for it to
> work, but that's coming along.
> 
> Tip: think in terms of DLGs laid on top of structural XML.

Was that Digital Line Graphs? 

Best regards,
Mark