to fully "support" JSON-LD it would be required to support it in the main query interface - i.e. the GraphQL JSON response should be decorated with a JSON-LD context statement that binds the available URI identifiers to the graphql schema elements - after all the graphql schema is generated from the underlying SHACL models.
For interoperability such JSON-LD contexts should be modular of course - if a model imports SKOS then the JSON-LD context should import a SKOS context rather than dump it out. If this is too much work in the short term, I'd suggest that the injection of a context via a URI referencing another service which constructs the context for a given graphql schema - and if necessary leave it empty, but allow this to be customised by users to be more modular in future. This at least establishes an architecture which can be evolved to seamlessly allow more natively supplied detail in future, without too much effort in the short term. On Tuesday, 3 March 2020 09:29:44 UTC+11, R. U.S. wrote: > > Hi, I've been working with Topbraid for a while and now I need to support > JSON-LD files (importing/editing/exporting). What is the current support > for it? Can you point me to the documentation for this? > -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/bbe0d0c2-6326-4dda-a107-703a3cdef750%40googlegroups.com.
