aboutsummaryrefslogtreecommitdiffstats
path: root/include
AgeCommit message (Collapse)AuthorFilesLines
2023-12-02Use ZixAllocator directlyDavid Robillard15-184/+56
2023-12-02Use ZixStringView directlyDavid Robillard7-125/+44
2023-12-02Use SerdNodes instead of manual memory management in testsDavid Robillard1-0/+10
2023-12-02Add "contextual" output optionDavid Robillard1-0/+9
This is mainly for developer or power-user cases, where one wants to look at some data for investigation or debugging. In such cases, it's common for the set of prefixes to be implicitly known (because they are baked in to the application, for example), so printing them just produces a large amount of redundant noise. That said, it can also be useful programmatically, because it allows several snippets to be written independently and ultimately concatenated (with a header to define the prefixes) without redundancy.
2023-12-02Add SERD_READ_ORDERED to preserve blank node ordering in modelsDavid Robillard1-0/+10
2023-12-02Add model and serd-sort utilityDavid Robillard6-0/+515
With all the new functionality, the complexity of the serd-pipe command-line interface is starting to push the limits of available flags. So, instead of grafting on further options to control a model, this commit adds a new tool, serd-sort, which acts somewhat like a stripped-down serd-pipe that stores statements in a model in memory. This keeps the complexity (including the user-facing complexity) of any one tool down, since other more focused tools can be used for streaming tasks in a pipeline. In other words, abandon Swissarmyknifeism, take a page from the Unix philosophy, and try to expose the model functionality to the command-line in a dedicated focused tool. The model implementation is tested by using this tool to run a subset of the usual test suites, and a special suite to test statement sorting.
2023-12-02Add statement filter sink and serd-filter toolDavid Robillard3-0/+62
2023-12-02Add "longhand" mode to write rdf:type predicates normallyDavid Robillard1-0/+7
2023-12-02Add serd_node_from_syntax() and serd_node_to_syntax()David Robillard2-0/+85
2023-12-02Cache commonly used nodes in the worldDavid Robillard1-0/+11
2023-12-02Add SerdNodes for storing a cache of interned nodesDavid Robillard3-1/+100
2023-12-02Make blank node prefixing automaticDavid Robillard2-23/+0
Though potentially useful, I don't think the complexity cost of the old interface (both to the implementation and to the user) is worth it. A special tool to transform blank node labels (for example with regular expressions) would be a better approach to this if it's ever needed in the future.
2023-12-02Split SERD_READ_VERBATIM into two more precise flagsDavid Robillard1-10/+19
Although the "verbatim" idea is nice and simple, more fine-grained control is necessary since these features (relative URI preservation and blank node label clash avoidance) are useful in different situations.
2023-12-02Add a reader flag to disable generated blank label avoidanceDavid Robillard1-0/+15
2023-12-02[WIP] Add support for converting literals to canonical formDavid Robillard2-0/+48
2023-12-02[WIP] Generalize node construction APIDavid Robillard4-150/+419
2023-12-02Add support for custom allocatorsDavid Robillard9-38/+182
This makes it explicit in the API where memory is allocated, and allows the user to provide a custom allocator to avoid the use of the default system allocator for whatever reason.
2023-12-02[WIP] Simplify reader and writer flagsDavid Robillard2-9/+81
[WIP] Testing?
2023-12-02[WIP] Remove SERD_CURIE node datatype entirelyDavid Robillard2-26/+29
2023-12-02[WIP] Expand URIs in readerDavid Robillard1-0/+2
This expands relative and prefixed URIs in the reader on the stack, rather than passing them to the caller to be dealt with. This pushes these context-full forms to the edge of the system as much as possible to minimise the headaches they can cause. Towards having stricter guarantees about nodes and eliminating the CURIE node type altogether.
2023-12-02[WIP] Move SerdEnv mutation from writer to readerDavid Robillard2-1/+3
Writing having side-effects seems questionable in general, and this prepares things for expanding URIs in the reader.
2023-12-02[WIP] Preserve long or short quoting from input documentsDavid Robillard2-27/+22
2023-12-02[WIP] Add extensible logging APIDavid Robillard4-58/+210
2023-12-02[WIP] Preserve anonymous graph syntax in TriGDavid Robillard1-6/+7
[WIP] Untested
2023-12-02[WIP] Add support for reading and writing variablesDavid Robillard2-4/+23
[WIP] Command line option, move later? This adds a reader flag and serdi option for extending a syntax with support for SPARQL-like variables, for storing things like patterns or simple queries.
2023-12-02Remove datatype arguments from integer and base64 constructorsDavid Robillard1-6/+2
2023-12-02Simplify output stream APIDavid Robillard5-31/+108
2023-12-02Simplify input stream APIDavid Robillard4-24/+136
2023-12-02Rename SerdErrorFunc to SerdLogFuncDavid Robillard2-6/+6
2023-12-02Make serd_writer_set_root_uri() take a string viewDavid Robillard1-3/+2
This is generally more convenient, and the node was just being copied anyway.
2023-12-02Make SerdBuffer an output streamDavid Robillard1-14/+19
2023-12-02Factor out and expose serd_write_file_uri()David Robillard11-11/+27
2023-12-02Separate Turtle and TriG reading codeDavid Robillard1-1/+1
2023-12-02Use Zix attributes directlyDavid Robillard19-274/+288
2023-12-02Add serd_env_copy() and serd_env_equals()David Robillard1-0/+10
2023-12-02Simplify SerdEnv APIDavid Robillard1-15/+13
2023-12-02Make serd_uri_string_length() precise and add it to public APIDavid Robillard1-1/+14
2023-12-02Replace serd_reader_set_strict() with SerdReaderFlagsDavid Robillard1-10/+9
2023-12-02Add empty syntax type for suppressing outputDavid Robillard1-6/+9
2023-12-02Use a simple type-safe stack in writerDavid Robillard1-0/+1
2023-12-02Add a set of limits to the worldDavid Robillard2-2/+30
The idea here is to remove the burden of passing things around like stack sizes (where most users don't care and will be happy with a reasonably large default) and keeping the call sites to things like serd_reader_new() clean. The cost is a bit more state, so it's both more powerful and more potentially flaky, since changing the limits has action at a distance that isn't clear from the call site. I think it's worth it for the cleaner API in the common case, and the much better forward compatibility.
2023-12-02Replace SERD_WRITE_STRICT flag with SERD_WRITE_LAXDavid Robillard1-1/+1
The unset value for flags should represent the best default, which in this case is strict parsing. Lax parsing is the riskier opt-in option.
2023-12-02Add support for writing terse output with minimal newlinesDavid Robillard2-0/+3
2023-12-02Simplify statement flagsDavid Robillard1-8/+6
2023-12-02Replace multiple stream callbacks with SerdEventDavid Robillard6-37/+113
This makes plumbing easier since everything goes through the same "stream" and only one callback is required to handling everything. It's also more easily extensible in case more event types need to be added in the future.
2023-12-02Simplify writer style options and write UTF-8 by defaultDavid Robillard1-6/+5
2023-12-02Add SerdStatementDavid Robillard2-6/+93
2023-12-02Add SerdCaretDavid Robillard4-9/+88
2023-12-02Add SerdField to public APIDavid Robillard1-0/+8
A statement field enum was previously only used by the writer internally, but will be used in the public API (without a sentinel value) in following commits.
2023-12-02Add serd_world_get_blank()David Robillard1-0/+10