Re: Encoding an incomplete date as xsd:dateTime

On 11 Feb 2014, at 01:53, Niklas Lindström wrote: > I would say that the vcard ontology formally needs to be fixed to allow for > more variation. It actually seems to have been amended somewhat in 2010 [4], > to at least not require the exact second (or fraction thereof) of the birth. The la

SEKE 2014 Call For Papers (Deadline 1 March)

(Apologies for multiple postings) SEKE 2014 Call For Papers The 26th International Conference on Software Engineering and Knowledge Engineering www.ksi.edu/seke/seke14.html (Alternate website: www.cs.pitt.edu/~chang/seke/seke14.html) Hyatt Regency, Vancouver, Canada July 1 - July 3, 2014 Call

Re: Encoding an incomplete date as xsd:dateTime

It may be worth reminding ourselves (?) that in RDF you can use “all of the above”. That is, if you want to make your RDF as consumable as possible, you may well represent the same stuff using more than one ontology. This is true of lots of things, such as peoples’ names or different bibliograph

Re: Encoding an incomplete date as xsd:dateTime

Hi Heiko, Unless you want to use another ontology (e.g. BIO [1][2] or schema.org[3]), I'd probably go ahead and break that contract, although it is not technically safe (AFAIK, it's a violation of OWL semantics). It depends on the expected consumption of your data. I would say that the vcard onto

Open Position for Graduate Fellowship in Semantic Web Technologies at CNR-STLAB

TITLE: Open Position for Graduate Fellowship in Semantic Web Technologies at CNR-STLAB Important notice: send by February 19th to st...@cnr.it your CV, a motivational statement, and the contact of at least one referee (or a recommendation letter). The official procedure for being admitted to t

Re: Encoding an incomplete date as xsd:dateTime

Hi Heiko, On 10 Feb 2014, at 15:55, Heiko Paulheim wrote: > Hi Jerven, > > this looks like a pragmatic solution. But I wonder if it may lead to any > conflicts, e.g., the vcard ontology defines the bday property with > xsd:dateTime as its range explicitly. Is it "safe" to simply use an xsd:gY

Re: Encoding an incomplete date as xsd:dateTime

Hi Heiko, The Timex3 standard for temporal expressions [1], as widely used for linguistic analysis, suggests 'XX' if the date or month is unknown. I'm not aware if people are using that to encode temporal expressions in Linked datasets, but it would definitely be a better solution than using

Re: Encoding an incomplete date as xsd:dateTime

Heiko, Another solution (that may be overkill for your needs) is to use the Time ontology[1] rhw [1] http://www.w3.org/TR/owl-time/ On 2014-02-10, at 10:37 AM, Heiko Paulheim wrote: > Hi all, > > xsd:dateTime and xsd:date are used frequently for encoding dates in RDF, > e.g., for birthdays in

ESWC 2014 Second Call for Challenge: Concept-Level Sentiment Analysis

** apologies for cross-posting ** Second Call for Challenge: Concept-Level Sentiment Analysis Challenge Website: http://challenges.2014.eswc-conferences.org/SemSA Call Web page: http://2014.eswc-conferences.org/important-dates/call-SemSA 11th Extended Semantic Web Conference (ESWC) 2014

Re: Encoding an incomplete date as xsd:dateTime

Hi Jerven, this looks like a pragmatic solution. But I wonder if it may lead to any conflicts, e.g., the vcard ontology defines the bday property with xsd:dateTime as its range explicitly. Is it "safe" to simply use an xsd:gYear value as its object? Best, Heiko Am 10.02.2014 15:43, schrie

Re: Encoding an incomplete date as xsd:dateTime

Hi Heiko, http://www.w3.org/TR/xmlschema-2/#gYear and http://www.w3.org/TR/xmlschema-2/#gYeargYearMonth are the datatypes that you should use. Regards, Jerven On 10 Feb 2014, at 15:37, Heiko Paulheim wrote: > Hi all, > > xsd:dateTime and xsd:date are used frequently for encoding dates in RD

Encoding an incomplete date as xsd:dateTime

Hi all, xsd:dateTime and xsd:date are used frequently for encoding dates in RDF, e.g., for birthdays in the vcard ontology [1]. Is there any best practice to encode incomplete date information, e.g., if only the birth *year* of a person is known? As far as I can see, the XSD spec enforces th

CFP: 1st Cuban Workshop on Semantic Web (Deadline is approaching)

We apologize for cross-postings. Please circulate this CFP among your colleagues and students. REMINDER CALL FOR PAPERS 1st Cuban Workshop on Semantic Web (TCWS 2014) Ha

ESWC 2014 Second Call for Challenge: Semantic Publishing

** apologies for cross-posting ** Second Call for Challenge: Semantic Publishing Challenge Website: http://challenges.2014.eswc-conferences.org/SemPub Call Web page: http://2014.eswc-conferences.org/important-dates/call-SemPub ** NEWS: ** an open in-use task has been added! 11th

ESWC 2014 Second Call for Challenge: Linked Open Data-enabled Recommender Systems

** apologies for cross-posting ** Second Call for Challenge: Linked Open Data-enabled Recommender Systems Challenge Website: http://challenges.2014.eswc-conferences.org/RecSys Call Web page: http://2014.eswc-conferences.org/important-dates/call-RecSys 11th Extended Semantic Web Confer

LiUD 2014: Linking User Data - Workshop at UMAP 2014

LiUD 2014 Workshop - Linking User Data Held at UMAP 2014 - 22nd Conf. User Modeling, Adapation and Personalization 7-11 July 2014 - Aalborg, Denmark Submission deadline: 1 April 2014 http://liud.linkededucation.org/ LINKING USER DATA The use of external, open resources is becoming increasingly