SIOC Import to Weblog
WordPress has a nice admin menu entry called "Import":
If you have posts or comments in another system WordPress can import
them into your current blog. To get started, choose a system to import
from below:
Dotclear Import posts from a Dotclear Blog
LiveJournal Import posts from LiveJournal
Blogger Import posts and comments from a Blogger account
Movable Type Import posts and comments from your Movable Type
Textpattern Import posts from a Textpattern Blog
RSS Import posts from an RSS feed
It would be nice to have ability to import SIOC into a CMS (and
WordPress weblog as a particular case).
While it is not main focus of SIOC development it 'd be an interesting
thing to have.
And anything else that uses SIOC data.
SIOC is currently strong on the data generation side (note: we could
use more users & testers of SIOC export in Drupal though) and now we
should get it strong in the data consumption side as well.
Best,
Uldis
[ http://captsolo.net/info/ ]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
- Login to post comments
This resource is supported by Science Foundation Ireland under grant number SFI/02/CE1/I131 (Líon) and SFI/08/CE/I1380 (Líon 2) at the Digital Enterprise Research Institute, National University of Ireland, Galway.
Syndicate
SIOC Import to Weblog
On 23/11/06, Uldis Bojars wrote:
> SIOC is currently strong on the data generation side (note: we could
> use more users & testers of SIOC export in Drupal though) and now we
> should get it strong in the data consumption side as well.
That's a general pattern with semweb I think. Definitely same
situation with FOAF too. We need more tools that actually use this
stuff!
cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
SIOC Import to Weblog
On 11/24/06, Dan Brickley wrote: wrote:
> On 23/11/06, Uldis Bojars
>
> > SIOC is currently strong on the data generation side (note: we could
> > use more users & testers of SIOC export in Drupal though) and now we
> > should get it strong in the data consumption side as well.
>
> That's a general pattern with semweb I think. Definitely same
> situation with FOAF too. We need more tools that actually use this
> stuff!
Here's an experimental tool that imports sioc:Posts(s) in WordPress:
"WordPress SIOC Import: Re-Using Some RDF"
http://tinyurl.com/2ydq7h
Hope this demonstration shows web developers what cool opportunities
appear once you start to re-use SIOC and RDF in regular web
applications (and that you can do that at all) and start connecting
different systems. And you don't need to know much of RDF to do that.
P.S. Bringing up a thread which is almost half a year old, but this is
a thread well worth coming back to. :)
Uldis
[ http://captsolo.net/info/ ]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
SIOC Import to Weblog
On 24/11/06, Dan Brickley wrote: wrote:
>
> On 23/11/06, Uldis Bojars
>
> > SIOC is currently strong on the data generation side (note: we could
> > use more users & testers of SIOC export in Drupal though) and now we
> > should get it strong in the data consumption side as well.
>
> That's a general pattern with semweb I think. Definitely same
> situation with FOAF too. We need more tools that actually use this
> stuff!
I don't disagree, but I did recently see the impression (on somebody's
blog, which I didn't bookmark and have probably lost for eternity...)
that this RDF thing was intended to be about looking at stuff, clever
data browsing etc. Writeable, maybe, but not like... editable.
btw, did any of yous sling SIOC data into Longwell?
Cheers,
Danny.
--
http://dannyayers.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
SIOC Import to Weblog
On 23/11/06, Danny Ayers wrote: wrote: wrote:
>
> On 24/11/06, Dan Brickley
> >
> > On 23/11/06, Uldis Bojars
> >
> > > SIOC is currently strong on the data generation side (note: we could
> > > use more users & testers of SIOC export in Drupal though) and now we
> > > should get it strong in the data consumption side as well.
> >
> > That's a general pattern with semweb I think. Definitely same
> > situation with FOAF too. We need more tools that actually use this
> > stuff!
>
> I don't disagree, but I did recently see the impression (on somebody's
> blog, which I didn't bookmark and have probably lost for eternity...)
> that this RDF thing was intended to be about looking at stuff, clever
> data browsing etc. Writeable, maybe, but not like... editable.
Oh, sure - RDF could have a fine future even just as a publish-only
format, ... with things internally being stored using other
techniques. But there is no point in publishing things that aren't
read ie. used, right? Even if used is consume-only... or at least
consuming that might sometimes result in the availability of more RDF
elsewhere, ... but which isn't editing in the classical sense of
changing the canonical source file.
cheers,
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
SIOC Import to Weblog
On 24/11/06, Dan Brickley wrote:
> > I don't disagree, but I did recently see the impression (on somebody's
> > blog, which I didn't bookmark and have probably lost for eternity...)
> > that this RDF thing was intended to be about looking at stuff, clever
> > data browsing etc. Writeable, maybe, but not like... editable.
>
> Oh, sure - RDF could have a fine future even just as a publish-only
> format, ... with things internally being stored using other
> techniques. But there is no point in publishing things that aren't
> read ie. used, right? Even if used is consume-only... or at least
> consuming that might sometimes result in the availability of more RDF
> elsewhere, ... but which isn't editing in the classical sense of
> changing the canonical source file.
I'll keep this one going a moment longer - not particularly coherent
late night rambling, you may prefer to exit at this point...
Bill deHora recently had a go on what he saw as the screw-ups of RDF,
and while his main crit was on RDF/XML syntax (moot for me) he did
nicely identify another hole: right now there's now easy way of doing
what you can do with an SQL DB behind a HTML form. Direct
round-tripping.
With many a web app there's a bunch of text slots in front of the end
user; behind the scenes is a table (tuples aren't in the vocabulary).
Intuitive 1:1 mapping, change the name field, same happens behind the
scenes. Yesterday if you have Ajax. <?php $name ?> (I don't know php,
but I bet that's not far off the mark). SELECT foo.name WHERE bar.
Easy.
Broad hand-wave, we know better than that. The knowledge being
modelled isn't so simple.
Ok it would be straightforward to have a messy graph thing behind the
scenes and make assumptions between that and the UI - the (open) world
allows many foaf:names, but this system will ignore that reality and
live with setName()/getName(). The FOAF-a-matic writes once, then it
writes once again...
On paper it /is/ possible to capture the fullness of changes:
reification (maybe), n-ary chunks (possibly), named graphs (easy). But
dealing with the interaction between a front end and a triplestore -
gets tricky. How do you edit the stuff in a triplestore? (Are
statements as cool as URIs?)
So how do you edit bits of the Semantic Web? How do you make editing a
triplestore as easy as editing (through a PHP interface to) an SQL DB?
Cheers,
Danny.
--
http://dannyayers.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "SIOC-Dev" group.
To post to this group, send email to sioc-dev@googlegroups.com
To unsubscribe from this group, send email to sioc-dev-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sioc-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
SIOC Import to Weblog
Fully agree with Dan Brickley, I think it is not easy to do this, -> through a PHP interface, reification (maybe), n-ary chunks (possibly), named graphs , lot of things need to be modified, not easy!
software reviews