Michael Stahl wrote:
Stephan Bergmann wrote:
Some more input:
[snip]
- Not sure if the modifying methods of XRDFNamedGraph are necessary
(or if they are only added to allow implementing XRDFRepository
together with an "alien" XRDFNamedGraph implementation; in which case
some private protocol between an XRDFRepository and the XRDFNamedGraph
objects it creates might be better)---but I am absolutely not a domain
expert with RDF.
if by "modifying methods" you mean addStatement, removeStatement, then
yes, those are the only methods that actually allow to change repository
contents :)
And it is intended that client code calls these modifying methods?
(This is still not clear to me from what you write. I had initially
asked, because if the methods are not really needed for client use, it
might be better to make XRDFNamedGraph objects immutable.)
note that XRDFRepository and XNamedGraph implementations will be tightly
coupled and not interchangeable.
basically, XNamedGraph can be implemented as just the graph name and a
pointer to the underlying repository implementation.
note further that (hopefully) there is no method in either interface
which takes an object of the type as parameter :)
- I vaguely remember I had some reason to consider UNOIDL constants,
esp. "complex" ones like strings or (not even implemented) structs, as
not useful, but unfortunately cannot remember the reason any longer...
stdin(905) : Missing type or illegal syntax following CONST keyword:
parse error
umm, strings are also not allowed as constants? argh...
Yep, looks like only a very restricted handful are allowed,
idlc/source/parser.y:1.17 l. 1552 ff.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
