NAVIGATION
CATEGORIES
REFERRENCE
LINKS
Missing xs:anyUri from fn:boolean typing rule.
0 answers - 348 bytes -
Comment #1 from simeon (AT) us (DOT) ibm.com 2006-09-19 15:25
Good catch. The typing rule should have xs:anyURI added to it, as follows:
statEnv |- Type <: (empty | NodeType+ | xs:boolean | xs:string |
xs:untypedAtomic | fs:numeric | xs:anyURI)
statEnv |- (FN-URI,"boolean")(Type) : xs:boolean
- Jerome
QUESTION ON "Standards"
- URI's for processes, stocks, file hashes, UPC's, etc..
- spam in this maillist?
- Call for Participation: OWLED06. OWL - Experiences and Directions
- Type checking fn:data(())
- Initial Writeup for ACPP Coronary Artery Bypass Guidelines Usecase
- specification of item-sequence-to-* functions unclear
- Problems with binary operators table in C.2
- xs:untypedAtomic promotable to *any* type?
- 3.7.1.1 Attributes: xml:id processing misleading
- Performance issues with OWL Reasoners => subclass vs instance-of
- URI's for processes, stocks, file hashes, UPC's, etc..
- Sizing
- Abstract section clarity
- Performance issues with OWL Reasoners => subclass vs instance-of
- ontology for units of measurement and/or physical quantities
- Performance issues with OWL Reasoners (Was Playing with sets in OWL...)
- A question on the vocabulary for 'persons'
- ZWJ&XML
- A question on the vocabulary for 'persons'
- Possible counters() limitation?