Re: [PragmaticWeb] [topicmapmail] Business Applications

Sebastian

apologies for late reply, but was playing in other threads

i do agree that narrowing the focus does indeed help feasibility
of task at hand
however just a very quick <chime> for universality

I design general intelligence systems,
universality can be achieved by autodetection of schema properties

(like taking a dump of a schema and generating the code for the map)


any schema (detect structure of schema)  to
any other schema (configure to structure...)

however I design, not code so
if you or someone interested in exploring universality from the ground
up I think it can be done

cheers

PDM


On Thu, Aug 23, 2012 at 1:56 AM, Sebastian S. <[email protected]> wrote:
> [The PragmaticWeb Research List]
> Hi,
>
> I've been reading all of the comments and I'm taking note of all of them =
because they all seem very valuable to me. I'm verry thankful really.
>
> I agree in that there is some kind of solitaire fashion that one feels li=
ke when coming to this at first. And I also think that maybe I seem a littl=
e 'universal' in the needs/features I would like to implement and address t=
oo. And also that it would seem very unrealistic to come 'from the ground u=
p' with a tool that addresses everything.
>
> So, I'm trying to narrow a little the scope and try to reflect this into =
an updated document. It only adds a section named 'Application Model' in re=
spect to the first but if I'm making my point there, a general purpose tool=
 can be thought as a layer that is useful when someone tells it what to do =
(quite like a traditional RDBMS or framework or programming language). So, =
its it could be understood that there be models narrowing this 'universalit=
y' but without losing the benefits of a layer of semantics for future integ=
ration, merging and maybe interoperability of 'semantic application instanc=
es'.
>
> https://cognescent.googlecode.com/files/Brochure2.pdf
>
> I also would like to implement this in Java, so I'm describing the initia=
l layout of packages and their functionalities into the Google Code hosted =
project repository, in a document named 'packages.txt':
>
> https://code.google.com/p/cognescent/source/browse/trunk/Cognescent/src/p=
ackages.txt
>
> It is far from being more than a draft specification of components and th=
eir features. It reflects the partitioning of the proposed software model a=
nd where and what could be done. My actual coding time is not much and I'm =
doing this alone. Whenever updates become available they'll be published. I=
t would be also greatly appreciated if someone can help somehow in the crea=
tion of a development team for this project.
>
> Thanks in advance!
> Sebastian.
>
>
> On Sun, Aug 19, 2012 at 12:08 PM, Patrick Durusau <[email protected]> w=
rote:
>>
>> Quintin,
>>
>>
>> On 08/19/2012 07:10 AM, Quintin Siebers wrote:
>>
>> Hey,
>>
>> We've been working on such a system for a few years now, and our current=
 version is open to have a look at:
>>
>> http://en.mssm.nl/software/kamala-in-the-cloud/
>>
>>
>> Good point but Kamala requires (as any topic map application does) that =
you establish what subjects you want to talk about, their identifies, relat=
ionships, etc. Having said that, you can fill it with whatever content you =
like.
>>
>> My objection to Sebastian's needs/features is their universal nature.
>>
>> If I were writing a topic map for business expenses, it would be very un=
likely to include the rules for receipts written in cuneiform (the earliest=
 business document is a receipt for beer at an inn). Not that topic maps ca=
n't do that, but most clients are unlikely to be interested. For that matte=
r, of the thousands of natural languages in existence, most clients are goi=
ng to be interested in only one (1). Topic maps can do more but again, prob=
ably not a requirement.
>>
>> You can see where this is going.
>>
>> I think topic maps shine brightest meeting the semantic requirements of =
actual customers.
>>
>> That someone, somewhere, off the Net most likely, is not best served by =
my topic map is quite likely.
>>
>> But, I am not arrogant enough to presume to act in their best interest, =
never having asked what they want, much less their permission.
>>
>> Is the "digital divide" (http://en.wikipedia.org/wiki/Digital_divide) th=
e new "white man's burden? (http://en.wikipedia.org/wiki/White_Man%27s_Burd=
en)"
>>
>> Hope you are having a great weekend!
>>
>> Patrick
>>
>>
>>
>> Quintin Siebers
>>
>> --
>> [email protected]
>> (+31) (0)6 - 11 06 16 27
>>
>>
>> Morpheus Kennistechnologie BV
>> <URL: http://www.mssm.nl >
>> postbus 69
>> 3500 CD Utrecht
>> KVK 30 26 04 30
>>
>> On 19 aug. 2012, at 13:03, Alexander Johannesen <alexander.johannesen@gm=
ail.com> wrote:
>>
>> Hola,
>>
>> On Sun, Aug 19, 2012 at 8:52 PM, adasal <[email protected]> wrote:
>>
>> Is what you are proposing really possible from the ground up? I wonder i=
f
>> even getting an architecture is possible from the ground up, i.e. withou=
t
>> starting with real world compromises dictated by the job in hand.
>>
>>
>> Not sure if what's proposed is possible from the ground up, but I know
>> it's certainly possible to create an ontology-based complete system,
>> however I doubt "from the ground up" has been defined enough at this
>> point. I've worked on creating full-stack application and systems
>> delivery framework based on ontologies / Topic Maps, both in terms of
>> integration but also as a development tool, and as a way to infer
>> capabilities of services based on their entity / resource rather than
>> clumsy API's.
>>
>> I'm fairly confident that it's the way of the future, but as you
>> probably allude to as well, it's still a bit way off, mostly because
>> whomever comes up with it first or already doing it, are doing it in
>> solitary, much like the TM community watching the spectacle of RDF
>> from the side-lines.
>>
>>
>> Regards,
>>
>> Alex
>> --
>> Project Wrangler, SOA, Information Alchemist, UX, RESTafarian, Topic Map=
s
>> --- http://shelter.nu/blog/ --------------------------------------------=
--
>> ------------------ http://www.google.com/profiles/alexander.johannesen -=
--
>> _______________________________________________
>> topicmapmail mailing list
>> [email protected]
>> http://www.infoloom.com/mailman/listinfo/topicmapmail
>>
>>
>>
>>
>> _______________________________________________
>> topicmapmail mailing list
>> [email protected]
>> http://www.infoloom.com/mailman/listinfo/topicmapmail
>>
>>
>> --
>> Patrick Durusau
>> [email protected]
>> Former Chair, V1 - US TAG to JTC 1/SC 34
>> Convener, JTC 1/SC 34/WG 3 (Topic Maps)
>> Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
>> Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)
>>
>> Another Word For It (blog): http://tm.durusau.net
>> Homepage: http://www.durusau.net
>> Twitter: patrickDurusau
>
>
>
> _______________________________________________
> PragmaticWeb mailing list
> [email protected]
> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/pragmaticweb
>