-Original Message-
From: denny.vrande...@wikimedia.de
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] Expiration date for data
We will have a time datatype, and every property is strongly typed. This
is also true for properties used as qualifiers.
Regarding the
Hi Lydia!
I don't think you're hearing the question. A reply y'all gave on the issue was
that any standard used by Wikidata needed to be 100% open-source -- no money
required as in free. Even though what is being charged by ISO to support its
business model is a PITTANCE in my humble opinion...
deed necessary. If
a distinction between nouns and adjectives is made, then one type + multiple
facets is necessary.
-Original Message-
From: John McClure [mailto:jmccl...@hypergrove.com]
Sent: Thursday, April 05, 2012 7:08 PM
To: Wikidata (E-mail)
Subject: [Wikidata-l] Namespace-b
Denny said:
I think the assumption everything has exactly one type is oversimplifying
The assumption that everything is of multiple types is over-complicating.
Usually you can tell from the first sentence in the Wikipedia page.
"Tuesday is a day of the week"
"Love is an emotion"
"(Roman) Catholic
Hi Denny -
Correct - URI opaqueness is required at the level of exchange but there's no
such requirement internal to an application. During exchange, sure you can
add a triple to assert that Density is the type of the object
France#Density:2012_pop_estimate_Bilan_2010. Outside of exchange, type can
Hi Denny -
Correct - URI opaqueness is required at the level of exchange but there's no
such requirement internal to an application. During exchange, sure you can
add a triple to assert that Density is the type of the object
France#Density:2012_pop_estimate_Bilan_2010. Outside of exchange, type can
Denny said:
you forgot to add something like
France#Density:2012_pop_estimate_Bilan_2010 property Density .
No I did not forget anything, given the Density 'namespace' in the subobject
name.
IOW your triple merely restates what is discernible from the subobject name.
Maybe you should tell me what
Denny said:
"if I understand topic maps correctly it should be trivial to write a
transformer that takes the export that Wikidata will offer and translates it
into topic maps, if you are so inclined. This way the topic maps community
can be served through that transformer easily, be it a web servic
Denny said:
But if you find a simpler, and more RDFish way to express the (below)
statement, please feel free to enlighten me. I would be indeed very
interested.
"The population density of France, as of an 2012 estimate, is 116 per square
kilometer, according to the "Bilan demographique 2010"."
A
Hi Denny -
Thanks for your reply and I am relieved. The design seems in the process of
walking towards looking quite alot like ISO Topic Maps, I must say, because
it designates no wall of separation between classes and topics. Today that
wall exists in SMW in the dichotomy of Category vs all-other-
Wiki namespaces are currently so underused people may not realize their
importance: they provide crucial semantic information. For instance,
consider the example given in Wikidata's data model article[1]
"Obama was US Senator from Illinois from January 3, 2005 to November 16,
2008"
which yielded
ain,
this note does *not* seek perfection, it is seeking to identify and to learn
from our experiences. My experience is that the Category namespace has been
functionally overloaded to the detriment of 'good' system design.
John McClure
___
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Sorry about a blank subject before...
Came across a good CalTech presentation called Relevance of Topic Maps
at http://www.cacr.caltech.edu/semast/files/mahabal.pdf
The presentation has the infamous Cregan datamodel on page 5. The question
is why not use this already-certified ISO datamodel being
iki Subject Indexes
Message-ID:
Content-Type: text/plain; charset="us-ascii"
On Mar 31, 2012, at 02:00 , John McClure wrote:
> Hello,
> Can/should wiki subject indexes be a functional requirement of the
wikidata
> project, or of some other? I think navigating a wiki today
hatever that is intended to be.
Thanks,
John
Date: Sat, 31 Mar 2012 11:22:43 +0200
From: Ivan Herman
To: "Discussion list for the Wikidata project."
Subject: Re: [Wikidata-l] Wiki Subject Indexes
Message-ID:
Content-Type: text/plain; charset="us-ascii"
On Mar 31, 2012, at 02
Hello,
Can/should wiki subject indexes be a functional requirement of the wikidata
project, or of some other? I think navigating a wiki today without a subject
index is difficult, to say the least. A subject index seems such a critical
component for information libraries! WP's portals are a nice s
iki.org]
>Sent: Wednesday, March 21, 2012 7:43 AM
>To: jmccl...@hypergrove.com
>Subject: Re: [Wikitech-l] Topic Maps
>
>
>On 21/03/12 13:06, John McClure wrote:
>> (1) official ISO versions are purchaseable while unofficial
>versions are
>> foss.
>
>Ok, that
17 matches
Mail list logo