Dan,
Why just integers? It would seem like it would be useful to be able to
add provenance (who, when, where...) information to any property - not
just integers. President:=Johnson - 1965 or hasChild :: Sarah - 2003
definedIn:=http://w3.org/sample/prelimVersion 2007-08-07
Harold Solbrig
RDF has two ways to handle this. I don't think SMW supports either in a direct
way.
1. Blank nodes. Instead of a property having a value of type integer, it has a
value
of a composite type that has an integer, date, etc. Since it is a "blank
node" you
don't need to create a unique URI f
Jeff Thompson wrote:
> RDF has two ways to handle this. I don't think SMW supports either in a
> direct way.
> 1. Blank nodes. Instead of a property having a value of type integer, it has
> a value
>of a composite type that has an integer, date, etc. Since it is a "blank
> node" you
>
Thanks, S, for finally detailing what n-ary relations will look like in SMW
1.0 - this was an issue of great curiosity to at least a few of us on the
mailing list.
That said (and I apologize if I'm now hijacking this thread) - are you sure
that this is the best way to implement them? The other way
S Page wrote:
> I just described SMW 1.0prealpha-3's support for N-ary properties in
> response to [Semediawiki-user] Typed links vs. OWL-relations [1], the
> same applies here.
>
> Property:Population_(on_date) would have [[Has type::Integer; Date]]
>
> The Berlin article would say [[Populatio
Yaron Koren wrote:
> Can you explain the reasoning that went into this [the composite type]
> decision?
Sorry, no. I'm more an early user of Semantic MediaWiki 1.0pre-alpha3
than a developer. I'm trying it out, filing bugs, and writing docs but
AFAIK the development was Deutschland und AIFB
