René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Enhancement: Use rdflib's JSON-LD parser for full context expansion","articleBody":"## Current Behavior\n\nThe `parseJsonLdToStore()` function uses a simple manual parser that only expands the `schema:` prefix:\n\n```typescript\nconst typeUri = node['@type'].replace('schema:', 'http://schema.org/')\n```\n\nThis means JSON-LD using other vocabularies (like W3C Verifiable Credentials) must use full URIs instead of relying on `@context` expansion.\n\n## Proposed Enhancement\n\nUse rdflib's built-in JSON-LD parser which handles full context expansion:\n\n```typescript\n$rdf.parse(jsonLdString, store, baseUri, 'application/ld+json')\n```\n\n## Benefits\n\n- Full JSON-LD context expansion\n- Support for any vocabulary without code changes\n- Proper handling of `@type` arrays\n- Standards-compliant parsing\n\n## Considerations\n\n- **Network latency**: Context URLs need to be fetched (could cache common ones)\n- **Offline support**: Would need bundled/cached contexts\n- **Async**: `$rdf.parse()` with remote contexts is async\n\n## Possible Approach\n\n1. Use `$rdf.parse()` for full JSON-LD support\n2. Bundle common contexts (schema.org, credentials/v1, etc.)\n3. Fall back to simple parser if context fetch fails\n\n## Related\n\n- Issue #1: @type array handling (subset of this problem)\n- W3C Verifiable Credentials demo requires full URIs as workaround","author":{"url":"https://github.com/melvincarvalho","@type":"Person","name":"melvincarvalho"},"datePublished":"2026-01-06T21:37:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2/solid-shim/issues/2"}