See also: IRC log
ok, seemed to just need the zakim invite to open things up
<uli> jeremy
<bijan> alanr
<uli> do we have an agenda?
Agenda at http://www.w3.org/2007/OWL/wiki/DataType.Telecon.2007.11.19/Agenda
mike: introduces agenda, rqmts for in-line, external data types
<bijan> http://protege.stanford.edu/plugins/owl/xsp.html
alanr: innteresting to hear what the motivation is for in-line datatypes. what would go wrong with just external?
bijan: people don't like having
definitions in external file, experience from Protege 3.x
... avoid overhead for always naming types
alanr: is there an argument that necessitates a separate syntax for RDF/OWL?
bijan: the argument is that its
not clear tools could find XML Schema syntax in-line
... some argue its more familiar for people from RDF
background
ack
jjc: unnamed datatypes are
advantageous, use-case for in-line user defined datatypes
... issue with serialization of XMLLiterals in RDF/XML,
particularly qnames in attributes
acks next
acks uli
uli: issue with XML schema types is closely related to using other types in OWL
<bijan> http://www.w3.org/TR/xml-c14n#NoNSPrefixRewriting
<bijan> I can almost define rationals in xml schema
<bijan> Definiteately in XML schema + an additional constraint
acks alan
<uli> bijan, ...i see - but will they look like the "true" xml schema types?
<bijan> yep
acks bijan
<Zakim> bijan, you wanted to reply to uli
alan: concern over defiing, e.g. owl:rational
bijan: owl extensibility requires
URIs. owl:rational could be defined, doesn't seem to be a big
deal
... clarifying Uli, Alan, are you saying reusing XML Schema
syntax might put burden on future datatypes
uli: concern was that other datatypes look like native types
bijan: yes, I believe that they
would
... we could use a relax ng type syntax as an inline syntax
acks jjc
jjc: take it that XML Schema
types are a given, largely b/c OWL 1.0 supported XML Schema
types
... query about how the value space mapping for rational could
work
discussion of representation of rational as pair of integers
discussion of XSCD, what they offer, are needed
jjc: the rqmt for us, is less than all of XSCD. we could take less of a solution if it provided re-usable URIs
a query has been sent to the XML Schema WG chair on the status of XSCD
alanr: can we say that if URI is
present you can reference external
... suggest we move forward with that proposal, on Wed
telecon
<uli> bye
<scribe> scribenick: mikesmith
<scribe> scribenick: MikeSmith
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: mikesmith Found ScribeNick: MikeSmith Inferring Scribes: mikesmith WARNING: No "Topic:" lines found. Default Present: MikeSmith, +44.789.107.aaaa, Carsten, bijan, Alan_Ruttenberg, uli, jjc Present: MikeSmith +44.789.107.aaaa Carsten bijan Alan_Ruttenberg uli jjc WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 19 Nov 2007 Guessing minutes URL: http://www.w3.org/2007/11/19-owl-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]