Comments (7)
Thanks, @Pfeil, we will check it out next week and give you feedback.
from ro-crate-java.
@Pfeil Thanks for your work, everything seems to be working fine.
from ro-crate-java.
Thank you for this issue. I'd like to include this feature soon. As this kind of would be a breaking change to 1.1, we need to take some considerations, though.
Some implementation notes:
The best will probably be for the reader to recognize the version and then deserialize a different context object for the new version.I was obviously confused at this moment. The context is not affected. The descriptor object is stored in a simple json object, which allows for quite some flexibility.- For the writer there should not be much of a difference. But we should consider offering the possibility to upgrade to newer versions on export. Not sure if this can be done always fully automatically and if it should be the default, though.
- The examples on the linked 1.2 draft seem inconsistent with the 1.2 File descriptor, where it states the ro-crate spec should be referenced (although the should may be the reason), meaning in this case ther should be at least two entries. I suggest to make it the default that the ro-crate specification is referenced in any case (as it is now). This means that, if someone really does not want to include the RO-Crate specification as in the examples, it will take at least one additional line of code. But I'll need to read through that in detail, maybe I missed something.
from ro-crate-java.
Thanks for taking this into consideration!
I don't know about the status of version 1.2, but as this is a draft, there could be inconsistencies. My interpretation would be that conformsTo
maybe an array, but has to include at least one object referencing https://w3id.org/ro/crate/...
, or it maybe a single object in which case it is the one that is referencing https://w3id.org/ro/crate/...
.
from ro-crate-java.
I shortly looked into it today. My plan is to have a branch soon which you may test (I'll see if we can publish beta releases to include/test them easier in projects). I hope to provide a first solution until next week.
First solution means to fix this specific issue, meaning I will also look into other changes of this draft after that. (note to myself: RO-Crate Specification 1.2 milestone on github)
from ro-crate-java.
Thanks, @Pfeil, for the update!
from ro-crate-java.
I am sorry for the large delay. I released two versions today. One being a simple update of the dependencies, nothing new here. The other should contain all basic functionality to work with the "new" conformsTo array: v1.1.0-rc.1
The readme now points out a few tests where the read- write and modification process is being tested/demonstrated. The concept has not changed a lot. There is a new builder which allows functionality from draft-specifications. You can use it to create or modify crates. It will update the version by itself if you use one of the functionalities.
If something does not work out for you, please return to this issue or open a new one. Otherwise, I plan to release the real 1.1.0 in a few weeks, depending on feedback coming in. Thanks a lot!
from ro-crate-java.
Related Issues (20)
- Support new ROR schema HOT 1
- Transmitting an RoCrate instance over a network HOT 5
- Guidance implementation for creating Profile Crates and using them for validation
- Re-evaluate group and package names. HOT 6
- Missing support for provenance elements HOT 1
- Improve documentation on mandatory build dependecy 'ro-crate-html-js'
- Officially support Java 21 LTS HOT 1
- Handle possible loops in data graph (2.0.0-rc4 only)
- Give in-crate reason about why draft features are being used in a crate
- Default constructor creates invalid crate HOT 7
- Adding urls/pairs to the context without RoCrateBuilder HOT 6
- Removing urls/key-value pairs from the context is not supported HOT 4
- Removing properties from entities is too complicated HOT 2
- Check the valid use of lists in our data structures HOT 4
- Adding an entity with the same @id as RootDataEntity/JsonDescriptor should not be allowed
- It is possible to create unreferenced data entites, resulting in invalid crates HOT 2
- ZipReader unpacks in ./temp
- Publish the library on a maven/gradle compatible repository. HOT 2
- Missing points in documentation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ro-crate-java.