gtsueng

Results 32 comments of gtsueng

Bioschemas has Specifications (classes) which are Profiles (and have additional property-related constraints) and Types (which do not). Hence to resolve to the appropriate specification on the Bioschemas website, you would...

Since all the projects I work on also use the DDE, I usually resolve any classes or properties for those projects using the DDE.

**Does the specification imply that the new type bioschema:SemanticTextAnnotation (STA in the follow) is being introduced too? Else, How can one distinguish a STA from any other schema:CreativeWork? Via dct:conformsTo?**...

Hi @marco-brandizi-- On the matter of `mainEntity`, I will defer to @ljgarcia, as she was involved in the development of the SemanticTextAnnotation profile. While the bioschemas:SemanticTextAnnotation has not been defined...

Since presentations are automatically ingested from presentations.csv, but publications are not, the publications may appear out of order from the presentations. It may be better to separate out publications and...

For profiles based on Schema.org types like ComputationalTool (based on schema:SoftwareApplication) -- this would mean adding a new property to a profile that is not available in the type, correct?...

The JSON file above displays fine in the DDE, but getting it to propagate to the website is another story (see https://github.com/BioSchemas/specifications/discussions/643)

@ljgarcia I can add them using the schema.org property 'disambiguatingDescription' in the jsonschema validation for profiles. Should I increase the version number for this fix? @albangaignard may need to update...

@ljgarcia The $validation portion of the JSON file (where the disambiguatingDescription is to be added) follows JSON schema formatting. Although we can add descriptors like `schema:disambiguatingDescription` here for our purposes,...

This makes sense to me. The pending property [suggestedAge](https://schema.org/suggestedAge) illustrates that QuantitativeValues is already being used as an expected value for age-related properties, so it's a reasonable suggestion. Something like:...