Whether a single namespace is best always depends on one's rqts but technically feasibility seems to depend on whether the properties of the duplicately-named pages are to have different values than the 'external term' page. You know you can always display 'customized' content for those pages. Anyway, remember that special property equivalent URI only works for apps that process owl:sameAs. (I don't know why the special property can't be called .owl:sameAs or, even better, .rdf:about).
Another perhaps better approach is to have a single protected page whose subobjects are the 'external terms' in question. Its feasibility depends on how subobjects are handled bvy RDF Export. You may need to do some patching.
To your original question -- is this the right way to export smw pages to the semantic web -- my answer is yes, for pages. Are you having trouble with your current approach?
On 29.04.2013 11:18, Marcelo Chiaradía wrote:
Marcelo.Cheers,What do you think?Regarding the exporting RDF feature, I think it could automatically export the external terms, if I use the property "equivalent URI" in every page that represents an imported term. (http://semantic-mediawiki.org/wiki/Help:Special_property_Equivalent_URI) . Again, I dont know for sure if this is meant to be used like this.Hi John, thanks a lot for your answer.The reason I thought to put the "external" terms in another namespace, is that I dont want them to be "normal" pages. Moreover, I could have some "real" pages in my wiki with the same name that the imported terms, and conceptually, they wouldnt mean the same thing, so I need to define them in a separate namespace. (maybe this is not a good practice, I dont know for sure. Maybe someone with more experience could give a thought)
2013/4/28 Marcelo Chiaradía <email@example.com>
Any tip about this would be much appreciated.Marcelo
2013/4/25 Marcelo Chiaradía <firstname.lastname@example.org>
Moreover, I dont want the imported terms will be considered as pages into my wiki. They represent just external terms. So I defined a new "External_term" namespace for them.Importing known vocabularies will allow me to acomplish this in a more massive way I think, cause I will be able to connect some of my pages to external resources through the imported vocabularies.I need it because I want my pages to be exported into the semantic web, thorugh the "Export RDF" feature.Hello everyone,Im trying to import some external vocabulary into my wiki (for examples, thesauri terms, dublin core properties, etc).So for each term imported I defined an "External_term" page for it. And for every property imported, I just tag my property page with the "equivalent" tag.I want to know if Im taking the right approach to expose my pages into the semantic web.Thanks in advance,Marcelo.
------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________ Semediawiki-devel mailing list Semediawikiemail@example.com https://lists.sourceforge.net/lists/listinfo/semediawiki-devel