> Hello Everyone.
>
> Given that all of the listed implementations are in Java, are there any
> plans to evolve the requirement that "The API MUST NOT preclude the usage
> with more than one language binding" into something more relaxed (and
> perhaps more in the favour of Object Oriented
Hello Everyone.
A design point question: what is the reason for having ResourceSet in the
"base" package, when it is only used in the "modules" package?
A question which follows on from the first is: why are there two packages?
It looks as if there are two packages to make the "Core Levels"
Hello Everyone.
In the JavaDoc for "Collection", the method "getResourceCount()" is defined
to have a return type of "int".
The JavaDoc for the "getSize()" method of "ResourceSet" shows a return type
of "long"
This seems rather mysterious: a ResourceSet can theorectically hold more
Resources
Hello Everyone.
This question is more implementation oriented: should the "addResource()"
and "removeResource()" methods of "ResourceSet" operate persistently?
(That is, should removing a Resource from a ResourceSet remove it from the
underlying datastore too? Or just remove it from the
Hello Everyone.
The subject says it all: what is the progress of defining a schema for [the
result of] the "getMembersAsResource()" method of "ResourceSet" ?
Is there some "work in progress" level design document that I have
overlooked?
Thanks,
Trevor.
