-
**Describe the bug**
`linkml-convert` fails to convert to RDF for the following case:
`schema.yaml`:
```yaml
id: https://www.foo.com/tsakg
name: tsakg
prefixes:
linkml: https://w3id.org/lin…
-
@eecavanna No action needed from you at this time. I will reach out if needed.
-
Schema.org datatypes are not good:
- they go against standard XSD datatypes that are the foundation of both XML and RDF.
- they are tentative (don't specify a lexical representation), eg schema:Numb…
-
**Describe the bug**
Range of attributes can be defined by key word `range` or by key word `any_of`. The latter allows to define union of ranges, e.g. union of boolean and float. However current impl…
-
Currently the python generation has lots of magic in it that should be better documented
- It creates very inclusive types with complex Unions, see #464.
- It creates classes for types, which c…
-
We have many cases where people use APs differently w.r.t the broad datatype used, and the kind of filler
With OWL, it is perfectly valid to use the same AP but to have values range from
* lite…
-
### Describe the bug
See https://github.com/monarch-initiative/monarch-ingest/issues/468#issuecomment-1564660130
Biolink imports linkml types (see https://github.com/biolink/biolink-model/blob/m…
-
**Is your feature request related to a problem? Please describe.**
Not a problem, rather an "intelligent" feature.
The Person+Organization [tutorial](https://github.com/linkml/linkml/blob/main/exa…
-
Right now, when transforming from a CURIE to a URI-based representation (i.e. TSV to RDF), we have to hard-code the prefix map in the linkml schema - which is not realistic for a wide range of data se…
-
**Describe the bug**
Some targets do not accept `@` as-is, so terms such as `@id` or `@type` have to be escaped/transformed.
**To reproduce**
Steps to reproduce the behavior:
- Use a yaml conta…