Bruce; See http://xmlns.com/foaf/spec/#term_birthday, which states that the value of foaf:birthday needs to be in a specific lexical form. The model we have formalizes this a bit more to set the range to be xsd:date.
So the Composer UI is looking for an xsd:date string. The parser will take any literal because that's how RDF works. Composer adds some type checking to align manual input to meet the model's definitions. You can always circumvent this through a SPARQL CONSTRUCT query or editing the source. Composer's UI is the only part that has code to check the type for validity. BTW, it was pointed out to me that I missed a sentence in an earlier response. When stating that you can unlock TopBraid/Common/foaf.owl, I had meant to state that you need to unlock it before deleting it. The point was to state that you can delete the version in Composer, which has been modified to be more OWLish than the standard. If you delete it, then it will be retrieved from the Web on each new session. -- Scott On Oct 24, 5:52 pm, Bruce Whealton <[email protected]> wrote: > Hello, > I have imported an rdf file that had various vocabularies > included. Some of them have properties that take dates as their data > type. For some reason, my birthday using foaf:birthday, which was > already in the rdf file is accepted. When I click on another > foaf:Person and try to enter their birthday, I get Unkown resource and > it doesn't accept the information. There isn't any resource defined > that represents my birthday. In other words, it should be a literal > value. However, it doesn't want to accept literal date values. > Bruce -- 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
