15
edits
Talk:RDF:Interfaces: Difference between revisions
m
no edit summary
Peter Wilson (talk | contribs) mNo edit summary |
Peter Wilson (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
Peter Wilson: Some notes on current shortcomings: | Peter Wilson: Some notes on current shortcomings: | ||
1. Ensure all rdf nodes have a value property. Its a pita to have ValueUTF8, Value etc. | *1. Ensure all rdf nodes have a value property. Its a pita to have ValueUTF8, Value etc. | ||
2. rdfINumber JS compatible decimal number. (Possibly replace nsIRDFInt) | *2. rdfINumber JS compatible decimal number. (Possibly replace nsIRDFInt) | ||
3. rdfIBoolean JS compatible boolean. | *3. rdfIBoolean JS compatible boolean. | ||
4. rdfIService.findResource(string)->bool should actually exist. (see 5.) A better name would be hasResource (It doesn't actually find anything). | *4. rdfIService.findResource(string)->bool should actually exist. (see 5.) A better name would be hasResource (It doesn't actually find anything). | ||
5. Is there any way to implement a case insensitive version of getSources? | *5. Is there any way to implement a case insensitive version of getSources? | ||
6. Are rdf:type and xml:lang handled correctly, at all? | *6. Are rdf:type and xml:lang handled correctly, at all? | ||
7. getDataSource should throw an exception if the source does not exist. Currently an empty DS is returned. | *7. getDataSource should throw an exception if the source does not exist. Currently an empty DS is returned. | ||
8. OR, A way to check that a datasource exists without creating it as a by-product. | *8. OR, A way to check that a datasource exists without creating it as a by-product. | ||
9. JS Access to the blob type. Other API manage to handle byte objects. Together with 6. you would be able to | *9. JS Access to the blob type. Other API manage to handle byte objects. Together with 6. you would be able to impl*ement any xsd or user defined type - but better to use XPCOM interfaces fo each type. | ||
10. Access to facts via the pattern (Subject ?Predicate Object). Currently, you have to do ArcsOut and test for the Object. Call it getPredicates. (see 5.) | *10. Access to facts via the pattern (Subject ?Predicate Object). Currently, you have to do ArcsOut and test for the Object. Call it getPredicates. (see 5.) | ||
11. You already know about the rdf parser error handling. | *11. You already know about the rdf parser error handling. | ||
12. Call the new string literal rdfIString (Numbers are literals as well). Reserve the term literal as a generic term for non-resources. | *12. Call the new string literal rdfIString (Numbers are literals as well). Reserve the term literal as a generic term for non-resources. | ||