Re: [SMW-devel] SMW Ontologies

2015-05-10 Thread John McClure 

Hi Valerio,
Sure, the extension includes an abstract class SMWOntology that can be 
inherited as you wish.
What you'll get are methods for storing (page/subobject) property values 
and also update.php -related processing...
And of course, you'll be able to examine the concrete classes when 
creating your own.
That said, I urge you nonetheless to consider identifying any 
relationships that exist between your own properties and properties 
established for public discourse -- that's what "smw:subProperty of" and 
a few other properties are used for.


Good question/thanks - john

On 5/8/2015 11:43 PM, Valerio wrote:

What if I'd create my own Ontology (i.e. NOT based on DC)?
BR/Valerio

On 8 May 2015 at 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




--
Valerio M. Pelliccioni


--
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

Re: [SMW-devel] SMW Ontologies

2015-05-10 Thread John McClure 

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  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  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_

Re: [SMW-devel] SMW Ontologies

2015-05-09 Thread Markus Krötzsch 
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
>


--
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

Re: [SMW-devel] SMW Ontologies

2015-01-15 Thread John McClure 

Thanks Martin for your thoughtful reply.
I agree completely that an IDE for SMW would be measurably useful to 
developers and editors (eschewing the term 'user' here, per standard MW 
definition that a user is someone with 'read' privledge on a wiki, not 
necessarily 'edit' privledge) for obvious reasons: faster, better, 
cheaper. But let's also note that by focusing our development efforts on 
SMW's core mission -- semantic queries, in large part -- then we 
strengthen the long-term business case for SMW itself.


SMW Ontologies /is/ an IDE (I will use these magic words in the 
future!). From Wikipedia, an "IDE normally consists of a (1) source code 
editor (2) build automation tools and (3) a debugger. Most modern IDEs 
have (4) intelligent code completion  Some IDEs contain a (5) 
compiler, interpreter, or both ... (6) a version control system and (7) 
various tools are integrated to simplify the construction of a Graphical 
User Interface. Many modern IDEs also have (8) a class browser, (9) an 
object browser, and (10) a class hierarchy diagram, for use in 
object-oriented software development." [footnote 1]


Let's compare this definition of an IDE to what I propose.

1. source code editor -- a 'smart textarea' is proposed to enter
   template calls for storing semantic triples
2. build tools -- not needed in interpreted environs like PHP,
   Javascript, Parsoid and template-script
3. debugger --templates and php code have a debug mode of output,
   storing validation errors on a page
4. intelligent code completion -- the smart textarea would have this
   for property values & facets selection
5. interpreter -- not an initial focus, though I envision a
   topic-map-syntax interpreter at a later time
6. version control -- achieved per namespace prefixes -- eg owl: vs
   owl2: -- a central idea of proposal
7. GUI builder tools -- data retrieval/formatting templates are parts
   of this proposal, plus infoboxes
8. class browser -- this is the OntologyBrowser I mentioned
9. object browser -- this is the OntologyBrowser I mentioned
10. class hierarchy -- this is the sum total of the numerous ontologies
   I indicated are to be installable

I want to see more than the dozen or so properties now (pitifully) 
built-in to SMW; I insist on a full dictionary.
I want to make life alot easier for people crafting (semantic) 
applications using SEMANTIC MediaWiki.


Hopefully my comparison clarifies that I also want to see an IDE come of 
this.


thanks/john

[footnote 1] source: 
http://en.wikipedia.org/wiki/Integrated_development_environment - i've 
added enumerators to the quote



On 1/15/2015 1:30 AM, Schneider, Martin wrote:

For now, I only want to say that all my use cases are ontology-related, so it 
would be good to have better support there.

But I cannot say if the points from your message, John, are those which are of 
importance.
I don't even see how this would ease building ontologies in SMW.

But then I'm rather new to this topic (both semantic knowledge engineering and 
SMW).

What I am missing most is something like an IDE for SMW, like Eclipse for Java.

I'll stay tuned to this topic.

Cheers, Martin


--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel