Bparsiajorgenson: Really smartening up, I think. I've been using it to debug loads of ontologies.
Bparsiajorgenson: We need somewhat better display of classification results, so you can tell what subclass relations were inferred. OTOH, you can export the class tree as an rdfs file.
Bparsiajorgenson: So, pretty easy to integrate with "dumb" rdf tools, usefully.
Bparsiajorgenson: We need somewhat better display of classification results, so you can tell what subclass relations were inferred. OTOH, you can export the class tree as an rdfs file.
Bparsiajorgenson: So, pretty easy to integrate with "dumb" rdf tools, usefully.
sbp: Scenario: you need to write a small piece of FOAF to test in some application. You want to write Person instead of foaf:Person (or worse <http://xmlns.com/foaf/0.1/Person>), and you don't want to have to say "literal" when you know that the range of your property is rdfs:Literal. Hence: schema-awareness
sbp: Email to rdfweb-dev, so FOAF oriented, but touches on many issues, including RDF-in-HTML
sbp: TODO/@@: check that particular objects belong to classes specified in their predicate's range, and perhaps allow the use of rdfs:label (and sub properties) to show the current subject in the prompt
sbp: Also, in www-archive, RDF Miniserializations: some history to the notes program, in random-note-format
sbp: Did I say "notes program"? Ahem. Slip of the tounge. Rather an interesting one, though...
Wack: nice! (schema aware editing is 'the only way to fly'; we're working on a wxPython editor and plan to implement schema awareness as well)
sbp: Email to rdfweb-dev, so FOAF oriented, but touches on many issues, including RDF-in-HTML
sbp: TODO/@@: check that particular objects belong to classes specified in their predicate's range, and perhaps allow the use of rdfs:label (and sub properties) to show the current subject in the prompt
sbp: Also, in www-archive, RDF Miniserializations: some history to the notes program, in random-note-format
sbp: Did I say "notes program"? Ahem. Slip of the tounge. Rather an interesting one, though...
Wack: nice! (schema aware editing is 'the only way to fly'; we're working on a wxPython editor and plan to implement schema awareness as well)
DanC: tutorial deadline is today.
dajobe: there are other OWL APIs, maybe they could assign a URI so we can uniquely identify this
dajobe: see WonderWeb
dajobe: won't build from source without junit
dajobe: announcement with broken URL, use the one here
dajobe: includes a non-streaming parser; stuffs all triples into memory to handle them
dajobe: docs note this is a problem
dajobe: and intended for OWL-DL/Lite only.
dajobe: so I'd say ignore this for RDF, use something complete
dajobe: rather dubious blank node support, indicated by methods like "public boolean isAnonymousNodeURI(java.lang.String uri)"
dajobe: what is this OWL/RDF syntax refered to here. That's ambiguous.
dajobe: later... they mean RDF/XML
dajobe: /me gives up
dajobe: I get 100s of unit test failures from building it here, can't tell why since it doesn't say
dajobe: here's a link to the ISWC paper but you are unlikely to be able to read it since a) site bloody awful b) corrupt pdfs
dajobe: and c) urls that have no real hope of living given the mechanism burnt into them
dajobe: I forgot d) access controlled by publisher
dajobe: there seems to be a typo in the paper "parsing RDF is non-trivial effort"; surely that means OWL
dajobe: <10k of python for a complete and streaming RDF/XML parser is not much
DanC: dealing with n-ary relations in a stream of RDF/XML is non-trivial
dajobe: there are no n-ary relations in RDF. The description was under "4.3 Parsing"/"Parsing RDF"
dajobe: see WonderWeb
dajobe: won't build from source without junit
dajobe: announcement with broken URL, use the one here
dajobe: includes a non-streaming parser; stuffs all triples into memory to handle them
dajobe: docs note this is a problem
dajobe: and intended for OWL-DL/Lite only.
dajobe: so I'd say ignore this for RDF, use something complete
dajobe: rather dubious blank node support, indicated by methods like "public boolean isAnonymousNodeURI(java.lang.String uri)"
dajobe: what is this OWL/RDF syntax refered to here. That's ambiguous.
dajobe: later... they mean RDF/XML
dajobe: /me gives up
dajobe: I get 100s of unit test failures from building it here, can't tell why since it doesn't say
dajobe: here's a link to the ISWC paper but you are unlikely to be able to read it since a) site bloody awful b) corrupt pdfs
dajobe: and c) urls that have no real hope of living given the mechanism burnt into them
dajobe: I forgot d) access controlled by publisher
dajobe: there seems to be a typo in the paper "parsing RDF is non-trivial effort"; surely that means OWL
dajobe: <10k of python for a complete and streaming RDF/XML parser is not much
DanC: dealing with n-ary relations in a stream of RDF/XML is non-trivial
dajobe: there are no n-ary relations in RDF. The description was under "4.3 Parsing"/"Parsing RDF"
danbri: See http://tap.stanford.edu/mcf/H/Herbert_A_Simon.mcf MCF source data.
danbri: I'm going to map the schema into FOAF...