[rdfweb-dev] RE: IMP schema thoughts

Jeremy Gray jeremy at jeremygray.ca
Tue Mar 16 20:58:21 UTC 2004

Re: "Nope, not text based." hehe. Well, so much for that approach, assuming
for the moment that the format isn't publically documented. :(

Re: the GIMP & oft-requested macro-type features - that's unfortunate.

Re: translation/convertor - if the formats were publically available, it
should be a relatively trivial exercise (ignoring fundamental capability
differences, of course) to translate between each application-specific
format and a neutral RDF-based one. I even know of an RDF-based data
integration vendor whose product could be used to implement and readily
expand such a translation facility :D, though the product might be a bit
heavy-handed for the purpose. Could be used by a server-based tool, however,
that allowed people to post and share such scripts, automatically
translating between the various application-specific formats.


-----Original Message-----
From: rdfweb-dev-bounces at vapours.rdfweb.org
[mailto:rdfweb-dev-bounces at vapours.rdfweb.org] On Behalf Of bryce benton
Sent: Tuesday, March 16, 2004 5:08 AM
To: rdfweb-dev at vapours.rdfweb.org
Subject: [rdfweb-dev] RE: IMP schema thoughts

Jeremy Gray wrote:
> If you haven't already, it would also be a good idea to look at 
> Photoshop's Action scripts, its History mechanism, and things like 
> that.

I very briefly looked into Photoshop's Action scripts. This simply 
involved opening an .atn file in a text editor and observing, "Nope, not 
text based."

Aside: In my recent surfing around, I've discovered that a macro 
recording feature akin to Photoshop's (very simple to use) Action 
recording feature is something that has been repeatedly requested of the 
GIMP for several years. Not being a GIMP developer, I don't see what's 
the big deal: "Hey GIMP, everything that I do, just make a note of it."

It seems to me that there are certainly overlaps between the GIMP, 
Photoshop and other IMP's. For any function, you need to know the name 
of the function and some parameters. Even if one program might expect or 
allow more or less parameters, at least *some* of the parameters would 
surely be the same for congruent functions.

One thing that comes to mind is ADODB, which abstracts various SQL 
languages into a common language. MySQL may want a query written one 
way, but MSSQL may like it another way. No problem: just change the 
ADODB database parameter.

Actually, the GIMP is already abstracted. It's already possible to call 
the features from several languages (Perl, Python, Ruby, et al).

Making these calls work on different IMP's could be as complex as 
invoking some sort of translation/converter script or simply doing the 
steps manually.


p.s. Hey, I just found this potentially helpful tool[1]: it converts the 
pdb into HTML documentation files. This could be tweaked to create a 
schema, no?

[1] http://hans.breuer.org/gimp/pdb/pdb2doc.py

rdfweb-dev mailing list
rdfweb-dev at vapours.rdfweb.org
wiki: http://rdfweb.org/topic/FoafProject

More information about the foaf-dev mailing list