Hi everybody, give the latest discussion, I think we have lost a bit the focus we had for our first release. Therefore I'd like to start talk about it. Looking to the mailing list and issue tracker, I'll try to summarize the current status, and see what we can afford for 0.1*:
* I think we can continue with the plan an use the current groupId:artifactId, which should solve COMMONSRDF-2. * The big issue remains with blank nodes. For me it's fine to go out with an api defining a simple contract, then is up to each implementation to take care of special details. That means we shift COMMONSRDF-6 and COMMONSRDF-14 to version 0.2. * I guess immutability requires further discussion, so also shifting COMMONSRDF-7 to 0.2. * Current version of the simple implementation is enough for testing the api and showing some ideas to actual implementators. In addition I'm working to get the site up (see INFRA-9260 for details), but I'm confident to find a solution with the infra people in the next few days. The, I ask: is there any other thing that stop us for preparing release 0.1? Thanks. Best regards, (*) with 0.1 I generically refer to both commons-rdf-api-0.1-incubating and commons-rdf-simple-0.1.0-incubating artifacts -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 6602747925 e: [email protected] w: http://redlink.co
