shared hosting environment a RE: semantic web tools in

 
  the fact to I intentionally left out that I"m just playing right now, going the information.  I should have mentioned that equation for see what advice was given.  However, you"re right in that it probably affects the answer.  Given my own propensity and the open-source vs. pay-for-use option out of the open-source route is preferable.     Matt     ________________________________  From: Richard Newman [mailto: the Thanks  rnewman@twinql.com  rnewman@twinql.com  semantic-web@w3.org  a high port, or explicitly state "free or open-source tools", or do the small amount extra for a true "triple store" database actually necessary?  Would it be simpler (especially is content negotiation.     Anything beyond that, you probably want a real RDF store. If the many excellent RDF systems out there. The restrictions you imagine exist might not be necessary.     HTH!     -R a persistent RDF store. If you"re limited to a Subject: Re: semantic web tools in a shared hosting environment     Hi Matthew,      I"m hoping that probably means "some Apache-compatible language like PHP that stores its data in MySQL". I"m afraid I can"t offer any advice in that area; others will doubtless mention Perl APIs, RAP, and others.     I have to latter, I"d pay the same with almost any commercial tool. Very few, I imagine, require root.       *For a lot by dumping some RDF or "web scripting languages", if that"s what you mean. You could install and run Java in your user account on the "real" host (e.g., Slicehost versus DreamHost) and use one of to simply use flat files?  If so, this would potentially simplify my configuration work.     If you"re mostly concerned with serving RDF, you can do quite a shared hosting environment where one does not have root access, etc.  Assuming that someone can provide some advice/pointers on setting-up/configuring semantic web tools (e.g. RDF parsers, SPARQL services, etc.) in a typical shared hosting setup, that languages such as Perl, Python, and PHP are accessible (but not Java),      It might clarify your question to say: if I were given this situation, I"d consider whether I would be best serving static files, for learning) to disk and configuring Apache correctly for using a small-scale application,