Hello Markus, it's very nice to hear from you.
Sure - that URI you mention is the same value I happen to assign to the
Property:dc:title page's smw:uri property. But no, this uri doesnt need
to be output during RDF export since the value of the smw:uri property
provided for the Dublin Core's Ontology page is (or perhaps should be!)
assigned to the xmlns:dc attribute on the export's <rdf:RDF> element.
The individual elements' URIs are provided on their Property: pages not
much for purpose of dereferencing by anyone as it is for documentation
purposes; indeed I replicate any triples from that source, such as the
property's datatype, that would be the purpose of such dereferencing.
Now, should you feel the dc:title's URI should be transmitted using a
different property than smw:uri, please don't hesitate to mention it as
other candidate properties do exist.
Oh with regard to RDFa, I note that W3 deprecates the use of xmlns: as a
vocabulary pointer mechanism in favor of a newish "prefix" attribute
that's to be used on the <html> element, thereby still allowing the use
of "dc:title" as the value of rdfa's property attribute on html
elements, so no need I can see to ever reference a uri like
http://purl.org/dc/elements/1.1/title/.
best regrds/john
On 5/9/2015 1:31 AM, Markus Krötzsch wrote:
Hi John,
Sounds interesting, but I don't think I fully understand the
functionality yet. In particular, how is the data that is thus
recorded related to the DC vocabulary? For example, dc:title is a
property with the URI http://purl.org/dc/elements/1.1/title. Is this
URI then used in the RDF export of SMW? Or do your parser functions
include some RDFa/microdata to refer to the DC URI?
Regards,
Markus
On 08.05.2015 22:22, John McClure wrote:
Hi,
Over the next month or so I am releasing a number of ontologies each as
an SMW extension. All installed ontologies will be listed on the
Special:Version page in a new section named "Semantic Ontologies".
For instance one of the ontologies is named "Dublin Core" (whose
namespace prefix is "dc") - its extension contains just one parser
function (named "dc") that is used to validate and then set the value(s)
on a page for any of the properties defined by that ontology. (Please
see http://dublincore.org/ for official documentation regarding this
ontology.)
So if you want to set the property "dc:title" for a page, then simply
call {{dc:title|/here is the formal title of a page/}}. For multilingual
wikis, one says {{dc:title|@en=/english formal title/|@de=/german
title/|...}}; the parser function in this latter case creates a
subobject named "dc:title" with properties named appropriately eg @en
and @de.
You may want to create your own property that is a "dc:title" but which
is to have a different name, here's all you do:
1) insert [[ smw:subProperty Of::dc:title]] on (say) your
"Property:Report name" page
2) call {{dc:title|{{{1|}}}|...|set property=Report name}} on a page or
within your "class" template
Validation errors are stored in special property "smw:error" that can be
reported using {{#ask:}}. A property value is not stored if a validation
error is raised.
A base ontology named "smw" is the first to be released, implemented as
described above; it contains properties and classes builtin to, or
implied by, the MediaWiki and Semantic MediaWiki software -- these
properties and classes form the lowest level ontology upon which ALL
other classes and properties are then defined (that is, via
class/subclass and property/subproperty relations).
I am working on an update.php -based mechanism for loading Property and
Category pages into one's wiki referenced by these ontology parser
functions. It also loads a page named "Ontology: /name/" into the
Concept namespace of the wiki so that users may conveniently access
information about the ontology.
Thanks in advance for your feedback.
--
thanks/john
skype:hypergrove
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
--
thanks/john
skype:hypergrove
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
