Added new product families for LOD and LOAC - #12
Conversation
|
Converted to draft to prevent accidental merge before descriptions, labels, and images are finalized. |
| schema:name "LOD Connectivity Product Family" ; | ||
| skos:prefLabel "LOD Connectivity Product Family" ; | ||
| skos:altLabel "Virtuoso Data Access Driver for the World Wide Web" ; | ||
| schema:description """The OpenLink Virtuoso Linked Open Data connectors proved client access to Web-hosted data in a similar way to SQL RDBMS hosted data"""; |
There was a problem hiding this comment.
| schema:description """The OpenLink Virtuoso Linked Open Data connectors proved client access to Web-hosted data in a similar way to SQL RDBMS hosted data"""; | |
| schema:description """The OpenLink Virtuoso Linked Open Data connectors provide client access to Web-hosted data in a similar way to SQL RDBMS hosted data"""; | |
| schema:name "Linked Open Agentic Commerce (LOAC) Product Family" ; | ||
| skos:prefLabel "Linked Open Agentic Commerce Product Family" ; | ||
| skos:altLabel "LOAC - applying Linked Data principles directly to commerce systems." ; | ||
| schema:description """LOAC is a model for representing commerce as a linked data-based entity-relationship graph constructed using hyperlinks as the primary mechanism of identity and traversal, making every layer of commerce both discoverable and computable."""; |
There was a problem hiding this comment.
| schema:description """LOAC is a model for representing commerce as a linked data-based entity-relationship graph constructed using hyperlinks as the primary mechanism of identity and traversal, making every layer of commerce both discoverable and computable."""; | |
| schema:description """LOAC is a model for representing commerce as a linked-data-based entity-relationship graph constructed using hyperlinks as the primary mechanism of identity and traversal, making every layer of commerce both discoverable and computable."""; |
|
When making the last suggestion, I saw an extra newline. This suggests to me that this document — meaning this whole repository — has been bitten by the GitHub CRLF "normalization" bug. (tl;dr: When someone makes a commit to a repository that GitHub notices has a mix of CR/LF/CRLF EOL characters, GitHub will "normalize" that repo to have only CRLF EOLs. There is no user confirmation nor other interaction; GitHub knows best.) On that basis — All our repositories (cc: @kidehen @pkleef @smalinin @imitko @JacquiHand @timhaynesopenlink @HughWilliams @danielhmills @mirkospasic @mitache whoever-I-forgot?) should get root-level
Anyone who works with a local In addition, after the |
Prevent GitHub CRLF normalization bug per OpenLinkSoftware/general-turtle-doc-collection#12. - Add root .gitattributes enforcing LF and excluding vendored/binary files - Add root .editorconfig for consistent editor line endings - Normalize 7 existing CRLF files (TTL/CLAUDE) to LF (pure EOL change, 0 content diff) - Preserve node_modules and binary files verbatim
Per OpenLinkSoftware/general-turtle-doc-collection#12: - Add root .gitattributes enforcing LF and excluding vendored/binary files - Add root .editorconfig for consistent editor line endings - Add gitignore exceptions so root .gitattributes/.editorconfig are tracked - EOL sweep deferred (working tree has unrelated in-flight changes)
Per OpenLinkSoftware/general-turtle-doc-collection#12: - Add root .gitattributes enforcing LF and excluding vendored/binary files - Add root .editorconfig for consistent editor line endings - Add gitignore exceptions so root .gitattributes/.editorconfig are tracked - EOL sweep deferred (working tree has unrelated in-flight changes)
2 participants
These descriptions are not complete. The wording of the descriptions and labels needs reviewing and the images are placeholders