Comments (2)
On a second thought, a more generic solution which would most likely resolve the problem would be support for custom (de)serializers for fields/classes much like Jackson's @JsonDeserialize
and JsonSerialize
. That way, you would be able to easily override the default (de)serialization behavior.
I'll create an issue for it, but it may take a while to implement...
from jb4jsonld.
That's a good question. I'm not very familiar with activity streams, but given the said properties, I think it depends whether type information is available in the JSON-LD input. If it is (like Example 110 and 111 for the URL property definition), JB4JSON-LD should be able to determine correct actual Java type even if the target field type is Object
.
If type information is not available in the input, it is basically impossible to determine the actual target type and the library will attempt to use plain Object
.
Another problem could be determining whether to use OWLDataProperty
or OWLObjectProperty
if the value is either plain string (xsd:anyURI
) or a Link object, but in that case, it should help to use OWLAnnotationProperty
, which accepts both literal values and objects. However, that may not be suitable if OWL reasoning on storage level comes into play. But that would depend on your specific case.
from jb4jsonld.
Related Issues (20)
- AssertionErrors from valid JSON-LD input HOT 4
- Allow IRI aliasing handling. HOT 2
- Relaxing check about single cardinality constraints in json deserialization DefaultInstanceBuilder) HOT 2
- handle polymorfism in property ranges during deserialization HOT 7
- Support for custom serializers/deserializers HOT 3
- NoClassDefFoundError: cz/cvut/kbss/jopa/model/MultilingualString on version 0.8.2 HOT 4
- Unable to serialize individuals in unmapped properties HOT 1
- Classpath scanning does not work for Spring Boot-based JARs HOT 2
- issues when deserializing subclasses HOT 1
- deserializing subclass defined in external maven artifact HOT 2
- MultilingualString values without language tag are not supported HOT 1
- Support JSON-LD 1.1
- Per-attribute format configuration
- Allow property overriding
- Support embedded contexts HOT 1
- Support external contexts
- Support mapping enum constants to individuals HOT 1
- Serialization with embedded context attempts to add the context to incorrect node
- Support serializing individuals as string with context info HOT 1
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 jb4jsonld.