Investigate Semantic connector Module

[DiegoPino]

https://www.drupal.org/project/semantic_connector Related to #823 and in general with the planned use of taxonomies.

I have been investigating some pieces of this already but was not fully convinced about some parts. But for CLAW, some components or just code ideas could be useful for SPARQL/Graph integration and https://www.drupal.org/project/skos_importer which moved into https://www.drupal.org/project/pp_taxonomy_manager seems also like a good candidate.

[akuckartz]

Did you find out how that module can function without PoolParty ?

[DiegoPino]

@akuckartz. Short: not out of the box. Do you have a use case/need/idea you would like to discuss?

Long answer: Can't promise anything yet because i have too many unfulfilled promises and a huge ongoing project here (Metro/NYC) that is using my energy but also this code. What I'm doing is working on an internal RDF UX module, the one I will give back to islandora community, (unfulfilled task) that borrows some ideas of the mentioned module (some code) but uses a different approach for the source/authorities/terms. RDF UX has been a long development and i have got stalled many times because of changing pieces and a moving floor, normal of course in an evolving project as this one All started with the JSON-LD serializer and that need has shown me that there are a lot of holes in Drupal's semantic layer. So my focus has shifted in the last 2-3 months to build a much "chunkier" piece of software part of a larger semantic/repository environment (Drupal 8 of course) project.

In this new scenario, Ontologies are being handled as entities (custom ones) and a full RDF core module replacement has started developing mostly because I had the need. I feel Drupal community cares little about Semantics, there are large issues like "subfield" mapping (complex, compound fields can only be mapped as a single, processed field/value) properties missing and most of the RDF related things are hooks, hardcoded to a certain group of entities, missing the whole purpose of having an extendable entity layer here. RDF module currently really does not act as a service and has little room for improvement. Stuff like consistent canonical URIs based on UUID is still complex to implement (and most of Drupal argument/routing system still depends on numeric, incremental route parameters) so my road to having this locally fixed is still long and then I will be able to contribute it back to Islandora if the project feels it is useful.

Hope this makes sense.