15
edits
Talk:RDF:Interfaces: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
Peter Wilson (talk | contribs) mNo edit summary |
Peter Wilson (talk | contribs) mNo edit summary |
||
| Line 8: | Line 8: | ||
*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 implement any xsd or user defined type - but better to use XPCOM interfaces for 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. | ||