15
edits
Talk:RDF:Interfaces: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(comment on a bunch of comments.) |
Peter Wilson (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
*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). | ||
Useless. Whether any datasource has a particular resource doesn't have a single use case. (The RDF Service is globally unique, or, a singleton.) | Useless. Whether any datasource has a particular resource doesn't have a single use case. (The RDF Service is globally unique, or, a singleton.) | ||
PW The Help system uses synthesised Resource names (based on user input) to perform searches and index operations. The global creation of those resources could be avoided by an existance check. i.e RDF.hasResource(NC:index + "#" + userTerm) instead of RDF.GetResource and DS.HasAssertion. If there is no resource there is no point looking in the datastore for the definition. | |||
*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? | ||
Yes, by hand. | Yes, by hand. | ||
PW No there isn't. If I have a user entered string, matching it against a case variant of that string will take 2**N HasAssetion operations where N is the length of the string. | |||
*6. Are rdf:type and xml:lang handled correctly, at all? | *6. Are rdf:type and xml:lang handled correctly, at all? | ||
Not yet, but at least for rdf:type, there is a bug on file. I know about xml:lang. | Not yet, but at least for rdf:type, there is a bug on file. I know about xml:lang. | ||