Re: Semantic Web using Magritte

Quoting Jason Johnson <jason.johnson.081@...>:

> Are your descriptions going to still be relevant for PDF in the same
> way they are for a web page?  Magritte descriptions usually provide a
> GUI for entering or editing them, no?

Not sure if we're talking about the same things totally. My  
descriptions have little if anything to do with the GUI. I am looking  
at adding automagic form generation in a few places, but mainly the  
forms in my application are hand-crafted right now. We do use Magritte  
in conjunction with our forms (ex: memento validation), just not to  
generate the actual form UI.


> If the descriptions do fit (or if they don't you could make new ones)
> then I think the thing to do would be to add a renderer.  Right now
> there is one for Seaside and one for Morphic.  So you would need one
> for each format you need to output to.  Perhaps there is already a
> package that does something like Seaside's canvas for XML (maybe XANO
> or whatever it's called?).
>

I have explored this strategy before for output. The thing is I really  
need to produce the RDF/XML/FOAF/RSS/ATOM or whatever else is required  
given a particular use case on demand relevant to the context. Many  
situations, Seaside won't play much of a part if any, however Magritte  
and my back-end (eventually Gemstone) will. There are many channels  
already to the application, so I want to define how to provide data in  
each format once regardless of the channel.



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki