I don't think we support that, and I would generally discourage such things
from an ontology point of view. The problem is not just that UIs will find it
hard to provide meaningful widgets - in your example we couldn't even display a
date picker. The other problem is that any query on that data will have to walk
through both cases, making it useless for SPARQL etc. Databases will also find
it hard to optimize the literals if they can't find a suitable default ordering
on them (to optimize FILTER and ORDER BY).
Why don't you define two properties with individual ranges? To work with such
data you could then use constructs such as
<span>{= COALESCE(spl:object(?subject, :published_in_date),
spl:object(?subject, :published_in_duration) }</span>
You could also turn the COALESCE above into a SPIN function so that it will get
either the first or the second property, which ever is available.
Thanks
Holger
On Jan 5, 2012, at 6:17 AM, PaulZH wrote:
> How can I limit a property e.g. :published_in to or a xsd:date or a
> xsd:duration and that the corresponding field in the form accepts
> both?
>
> --
> You received this message because you are subscribed to the Google
> Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
> TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/topbraid-users?hl=en
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
