8,037 Matching Annotations
  1. May 2022
    1. Machine Tags

      A new kind of tags — machine tags — are supported now. A machine tag, e.g. meta:language=python consists of a namespace (meta), a key (language) and a value (python). Everyone can created machine tags, but the meta: namespace is protected and tags in there will be created by the site itself.

      The codesite itself uses machine tags to make various properties of recipes accessible to the search:

      • meta:language

        The programming language of the recipe, e.g. python, perl or tcl.

      • meta:min_$lang_$majorver

        Those tags describe the minimum language version. If a recipe requires Python 2.5 it would have the tag meta:min_python_2=5.

      • meta:license

        The license that was selected by the author, e.g. psf, mit or gpl.

      • meta:loc

        This tag contains a number describing the lines of code in a recipes. It counts only the number of lines in the code block but not any lines in the discussion of in comments. This makes it possible to search for short recipes with less than ten lines or very large ones.

      • meta:score

        The current score of the recipe. This is the same number that is displayed besides the recipe title and can only be influenced by voting on recipes. That way you could even search for down-voted recipes

      • meta:requires

        Stores information about additional requirements of the recipes, e.g. required python modules. You can find recipes using python's collections module that way.

      All those tags cannot be changed directly because they are generated from a recipe's properties.

    1. We also support machine tags that follow the pattern NAMESPACE:KEY=VALUE. For example: geo:lat=43.555 camel:size=medium machine:tag=with space Machine tags are not revealed to the user on the track pages.

    1. Get all repos from the user https://api.github.com/users/:user/repos, then look for open_issues_count in the named repo.

      HI, when you get issues by page like issues?page=0&per_page=5 number property from first element will be count of issues.

    1. ```html

      <script type="application/ld+json"> { "@context": "https://schema.org", "@type": ["MathSolver", "LearningResource"], "name": "An awesome math solver", "url": "https://www.mathdomain.com/", "usageInfo": "https://www.mathdomain.com/privacy", "inLanguage": "en", "potentialAction": [{ "@type": "SolveMathAction", "target": "https://mathdomain.com/solve?q={math_expression_string}", "mathExpression-input": "required name=math_expression_string", "eduQuestionType": ["Polynomial Equation","Derivative"] }], "learningResourceType": "Math solver" }, { "@context": "https://schema.org", "@type": ["MathSolver", "LearningResource"], "name": "Un solucionador de matemáticas increíble", "url": "https://es.mathdomain.com/", "usageInfo": "https://es.mathdomain.com/privacy", "inLanguage": "es", "potentialAction": [{ "@type": "SolveMathAction", "target": "https://es.mathdomain.com/solve?q={math_expression_string}", "mathExpression-input": "required name=math_expression_string", "eduQuestionType": ["Polynomial Equation","Derivative"] }], "learningResourceType": "Math solver" } </script>

      ```

    1. <details open> <summary>
      Nanotate Annotations Samples
      </summary> ```json [ { "id":"d5JrdABbEeuatj9X3vvoXw", "authority":"__world__", "url":"https://protocolexchange.researchsquare.com/article/pex-1069/v1", "created":"2020-09-27T00:50:41.265044+00:00", "updated":"2020-09-27T00:50:41.265044+00:00", "title":[ "Sample preparation and imaging procedures for fast and multiplexed superresolution microscopy with DNA-PAINT-ERS" ], "refs":[ ], "isReply":false, "isPagenote":false, "user":"acct:miguel.ruano@hypothes.is", "displayName":null, "text":"", "prefix":"for 10 minutes. Wash with PBS3. ", "exact":"Add imaging buffer with desired ratios of Buffer C (500 mM), ethylene carbonate, and IS-CF660R at 1-2 nM final concentration. The exact concentration of IS may need to be adjusted depending on the target and based on the imaging kinetics.", "suffix":"", "start":15158, "end":15396, "tags":[ "step" ], "group":"__world__", "ontologies":[ ] }, { "id":"FrhgjABcEeu5B4dnXgvb_A", "authority":"__world__", "url":"https://protocolexchange.researchsquare.com/article/pex-1069/v1", "created":"2020-09-27T00:55:08.276888+00:00", "updated":"2020-10-05T14:15:00.764415+00:00", "title":[ "Sample preparation and imaging procedures for fast and multiplexed superresolution microscopy with DNA-PAINT-ERS" ], "refs":[ ], "isReply":false, "isPagenote":false, "user":"acct:miguel.ruano@hypothes.is", "displayName":null, "text":"my other text modificate", "prefix":"ed ratios of Buffer C (500 mM), ", "exact":"ethylene carbonate", "suffix":"", "start":15219, "end":15237, "tags":[ "reagent" ], "group":"__world__", "ontologies":[ "CHEBI" ], "settings":{ "bio_annotations":[ "" ] } }, { "id":"7Z1sugBbEeu9_wtvk1iAjw", "authority":"__world__", "url":"https://protocolexchange.researchsquare.com/article/pex-1069/v1", "created":"2020-09-27T00:53:59.317703+00:00", "updated":"2020-09-30T00:39:50.822216+00:00", "title":[ "Sample preparation and imaging procedures for fast and multiplexed superresolution microscopy with DNA-PAINT-ERS" ], "refs":[ ], "isReply":false, "isPagenote":false, "user":"acct:miguel.ruano@hypothes.is", "displayName":null, "text":"", "prefix":"10 minutes. Wash with PBS3. Add ", "exact":"imaging buffer", "suffix":"", "start":15162, "end":15176, "tags":[ "reagent" ], "group":"__world__", "ontologies":[ "CHEBI" ], "settings":{ "bio_annotations":[ "http://purl.obolibrary.org/obo/CHEBI_35225" ] } } ] </summary>
  2. datatracker.ietf.org datatracker.ietf.org
    1. 4. Link Relations for Web Services

      In order to allow Web services to represent the relation of individual resources to service documentation/description and metadata, this specification introduces and registers three new link relation types.

      4.1. The service-doc Link Relation Type

      The "service-doc" link relation type is used to represent the fact that a resource or a set of resources is documented at a specific URI. The target resource is expected to provide documentation that is primarily intended for human consumption.

      4.2. The service-desc Link Relation Type

      The "service-desc" link relation type is used to represent the fact that a resource or a set of resources is described at a specific URI. The target resource is expected to provide a service description that is primarily intended for machine consumption. In many cases, it is provided in a representation that is consumed by tools, code libraries, or similar components.

      4.3. The service-meta Link Relation Type

      The "service-meta" link relation type is used to link to available metadata for the service context of a resource. Service metadata is any kind of data that may be of interest to existing or potential service users, with documentation/description being only two possible facets of service metadata. The target resource is expected to provide a representation that is primarily intended for machine consumption. In many cases, it is provided in a representation that is consumed by tools, code libraries, or similar components.

      Since service metadata can have many different purposes and use many different representations, it may make sense for representations using the "service-meta" link relation to offer additional hints about the specific kind or format of metadata that is being linked.

      This definition of the "service-meta" link relation makes no specific assumptions about how these link hints will be represented, and the specific mechanism will depend on the context where the "service-meta" link relation is being used.

      One example is that a "service-desc" link may identify an OpenAPI description, which is supposed to be the machine-readable description of a Web API. A "service-meta" link may identify a resource that contains additional metadata about the Web API, such as labels that classify the API according to a labeling scheme and a privacy policy that makes statements about how the Web API manages personally identifiable information.

    1. The paper describes four ontologies for representing workflows in Research Objects, and includes examples and motivation scenarios.

      The ontologies developed make use of and extend existing well known ontologies, namely the Object Reuse and Exchange (ORE) vocabulary, the Annotation Ontology (AO) and the W3C PROV ontology (PROVO). We illustrate how the ontologies can be utilized using a real-world scenario, in which scientists created a Workflow Research Object for an investigation on the Huntington's disease. We also present the tools we developed for managing Workflow Research Objects.

      A sketch depicting the main steps that the bioinformatician followed for manipulating and analyzing datasets, and the workflows that were used in each step

  3. Apr 2022
    1. ```js document.createAnnotation()

      document.getAnnotations(nodes)

      document.removeAnnotation(annotation) ```

      ```js Annotation#addTarget(target)

      Annotation#addBody(body) ```