Re: Using TM to help define the future of XML

Anthony,

On Fri, 2010-12-03 at 23:34 +0000, Antony Pitts wrote:
> Jan (and Patrick),
>  
> Well, this may not be what you mean, but we’ve developed a simple
> slideshow tutorial which matches your criteria of an odd-sounding
> title, pictures, and some jokes...  
> http://www.musicdna.info/TMMN/ 
>  

Well, perhaps not exactly. ;-)

On the other hand, it was a real hoot! 

I had seen it before but it has been a really long day today so perhaps
I appreciated it more today. 

> It’s mainly for our own use as a scribble method for ontology
> development; we’re now working on simple shorthand representations of
> whole-part relationships for ATMMN (Advanced Topic Maps Martian
> Notation).
>  

I like that, "...scribble method for ontology development....", nah,
that's too easy a line. ;-)

Don't keep us waiting too long! 

Although I don't think you have many competitors when it comes to
graphic presentations. 

Hope you are having a great weekend!

Patrick

PS: I assume you are working on Martian topic map lego blocks that
prompt the user for properties, etc.? That crawl around on the screen
and self assemble/merge as appropriate? 

Or a topic map video game where you have to supply properties that will
make representatives of concealed subjects merge. That could be wicked
funny. You just get clues as to the identity of the subjects. Could even
have them merge without their identity being revealed. That has
potential. 




> Antony
>  
>  
>  
> From: Jan Schreiber 
> Sent: Friday, December 03, 2010 11:46 AM
> To: TopicMapMail Mail 
> Subject: Re: [topicmapmail] Using TM to help define the future of XML
>  
> Sender ALLOWED 
> [ Remove ]  [ Block ]
>    details 
>                                       Vanquish Anti-Spam Control Panel
> 
>  
> Patrick,
> 
> > More seriously, do you mean we need one or more tutorials with odd
> > sounding titles?
> 
> Well, I like it when tutorials include nice pictures and some jokes.
> This makes them more attractive as good night litterature than
> academic papers. It's hard to find easy-accessible litterature for TM
> beginners.
> 
> > Or just more tutorials in general?
> 
> > I suspect part of the problem is that unlike the Haskell tutorial,
> there
> > isn't a command line interface (or other) that gives you immediate
> > feedback. 
> 
> Well, that's where my secret secret plan is. But I need CTM import for
> tmjs first. Details will be posted on this list. ;-)
> 
> > That is if a tutorial started off talking about topics and you
> > enter/copy the code for a topic, yawn, now what?
> 
> Isn't that the way many programming tutorials start? Enter some data,
> start querying the data. This is how you store information, and that
> is how you retrieve information.
> The Ruby on Rails community did an excellent job. Everybody started
> writting blog engines with Rails. They were pretty useless, but it was
> an easy accessible way to the technology. Everybody knows what a blog
> is, and you only needed some lines of code to create a blog by
> yourself. Wow!
> 
> > See the problem? 
> > 
> > The *bang* in topic maps takes a bit longer to become evident. 
> 
> That's for sure. But you have to get started somehow. I prefer
> practical introductions.
> 
> > My thinking being that the create ontology/types/topics -> write
> file ->
> > load file -> navigate -> merge with other files -> still text
> interface
> > approach interests a small minority of users but just isn't
> appealing to
> > the game boy/netflix users. If it doesn't jump, fizzle or pop, they
> lose
> > interest pretty quickly. 
> 
> Agree.
> 
> > PS: Can you say what would be of interest to the nodejs community?
> > Thinking that tutorials that touch on items of interest to
> particular
> > communities are likely to be more successful than others. The
> Haskell
> > tutorial for example touches on concerns meaningful to programmers
> but
> > not rose gardeners. Topic maps tutorials for either of those groups
> > would be somewhat different. Yes?
> 
> Yes. As a developer I was thinking about tutorials for developers.
> Management and rose gardeners can be convinced later (maybe by other
> developers).
> 
> As for the nodejs community, it turned out that they are not
> interested in databases as much as other communities (e.g. Ruby on
> Rails). Usage of NoSQL storage is pretty widespread. But still, nobody
> knows where the development of all those NoSQL databases will end.
> Would you invest money into such storage solutions? If you use TMs as
> a layer between your application and a NoSQL database, migrating to
> other NoSQL databases will be quite easy. Write a new backend. Export
> XTM from the old backend. Import XTM. Done. You get the benefits
> (flexibility, scalability, etc.) of NoSQL but your information is
> always accessible using an ISO standard.
> 
> Also, it turns out that node programmers like functional programming.
> A case for path languages?
> And: node is still new and hot. Much more easy to get attention for
> anything, at least I think so.
> 
> - Jan
> _______________________________________________
> topicmapmail mailing list
> [email protected]
> http://www.infoloom.com/mailman/listinfo/topicmapmail
> 
> _______________________________________________
> topicmapmail mailing list
> [email protected]
> http://www.infoloom.com/mailman/listinfo/topicmapmail
_______________________________________________
topicmapmail mailing list
[email protected]
http://www.infoloom.com/mailman/listinfo/topicmapmail