Redland-ObjC Release Notes

1.0.2

Released on Tuesday, August 23rd, 2005.

• Statically linked against Redland 1.0.2, Raptor 1.4.7, Rasqal 0.9.10, Berkeley DB 4.3.27, and PCRE 4.5.
• Redland-ObjC now uses SenTestingKit (OCUnit) instead of UnitKit for all unit tests. SenTestingKit is included with Xcode 2.1.
• Added limit/setLimit: and offset/setOffset: methods to the RedlandQuery class.
• Due to an unsolved problem with HeaderDoc generation, there is currently no updated documentation available. The only API change from the previous version is the addition of the four methods mentioned above.

1.0.0

Released on Sunday, February 6th, 2005.

• Binary package is now compiled against Redland 1.0.0, Raptor 1.4.6, and Rasqal 0.9.6.
• API CHANGE: Added baseURI argument to all RedlandQuery initializers.
• Added -[RedlandModel containsContext:] method which checks for the existence of a context in the model.
• Added methods isBindings, isBoolean, isGraph, getBoolean, and resultStream to QueryResults class.
• Added new serializer name constants RedlandAbbreviatedRDFXMLSerializer and RedlandRSS10Serializer.

0.9.19p2

Released on Wednesday, November 3rd, 2004.

• Really added the librdf headers to the framework package.
• The binary framework package now includes patched librdf headers which point to the correct <Redland/…> locations if the macro LIBRDF_OBJC_FRAMEWORK is defined. If you include <Redland/Redland-ObjC.h> as recommended, it will automatically define the macro for you, and everything else should work out of the box.
• Added a text file with compile hints to the source package. See COMPILING.txt for details.
• The source project now has a shell script target for generating the framework documentation.

0.9.19p1

Released on Wednesday, November 3rd, 2004.

• Added the librdf headers to the framework package. (They should have been there before. I'm still not quite sure why they were left out in the first place.)
• To compile against the framework, you must manually set your include path to the Headers subdirectory of the Redland framework package. This is because the librdf headers contain lines like #import <raptor.h>, which result in a file not found error unless you happen to have the Redland headers somewhere in your default search path. I wish there was a more elegant solution to this problem…
• Fixed an assertion failure when calling [RedlandNode URIValue] on a non-resource node.

0.9.19

• License changed to LGPL 2.1/Apache 2.
• Binary package updated to use redland-0.9.19.
• There is now an API to set features for RedlandWorld, RedlandParser, RedlandSerializer, and RedlandModel.
• Most classes now have “real” initializer methods, not just class methods returning autoreleased objects.
• New RedlandSerializer methods serializedStringFromModel: and serializedDataFromModel: which use the new in-memory serializer API.
• The RSS parser in the statically linked binary package is currently disabled due to a compile problem.
• For additional changes, see the ChangeLog file inside the source package.

2004-09-19

• Fixed a bug that would cause the exception “+[RedlandWorld handleLogMessage:]: selector not recognized” whenever the Redland library generated a log message. Thanks go to Greg Schueler for pointing this out.

2004-09-18

• This is the first public release, so be gentle. Please report all bugs to me via e-mail. I am also subscribed to the Redland-dev mailing list.
• The Objective-C bindings are licensed under version 2.1 of the GNU Lesser General Public License.
• The API reference is auto-generated by HeaderDoc.
• Due to a naming conflict with the original Redland library header and the case insensitiveness of HFS+, you must include <Redland/Redland-ObjC.h> instead of <Redland/Redland.h> as you would normally do for a framework.
• By default, the framework is built with an INSTALL_PATH of @executable_path/../Frameworks. This means that it should be located inside the Frameworks folder of your application bundle. To accomplish this, add the Redland framework to your project, and then add a Copy Files Build Phase to your target. In the build phase inspector, set the destination to Frameworks, then drag the Redland framework into the newly created build phase. Xcode will now copy the framework into the application bundle during compile time. The framework contains the statically linked Redland libraries, so you can (hopefully) redistribute it without getting linker errors.
• The framework is prebound at address 0xDE000000. If this collides with other frameworks you are linking against, prebinding will be disabled. In this case you should download the source code and change the linker settings as appropriate.
• The Xcode source project expects Redland and related libraries to be located in /usr/local. If your libraries are located elsewhere, simply update the Other Linker Flags in the target's linker settings.
• The framework comes with a suite of test cases. If you want to run the test suite yourself, you will need the UnitKit framework.
• I am very interested in feedback. Feel free to send me your comments and ideas.