PackagePackagetypeA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

urp-vocab

A CDS vocabulary for User-Rendered Patterns, with @urp.display annotations describing views, card templates, layouts and sections on an entity, consumed by the author's own matching renderer.

A third way to annotate a model for rendering, beside Fiori annotations: the vocabulary is the author's own rather than SAP's, so what consumes it has to be the matching renderer.

Facts

Latestv0.1.2ReleasedLicenceMIT

Where it sits

Lives in
Provides
Fiori annotationsCAPFiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.
Flavors
Node.jsJavafrom its runtime
Requires
@sap/cds≥ 6.0.0@sap/cdsartifactThe peer range, as published.

Who is behind it

kamlendra

Before choosing this

Conditions

PracticalFunctional boundary

The declared repository is github.com/your-username/urp-vocab, an unedited placeholder. Three releases, September 2025.

What it declares

Every artifact

Type
Package
Origin
Independently maintained
Runtime
build time

As a package

Declared for
>=6.0.0
Where it runs
does not say
Distributed through
does not say

Tasks this contributes to1Beta

Carry a vocabulary SAP does not ship into the OData metadataAnnotations written with terms of somebody's own reach the service's OData metadata, with the reference to their vocabulary document beside them, instead of being dropped in translation.Node.jsAssessed, not knownpublished vocabulary
What it does

A vocabulary of its author's own, used from CDS as using urp from 'urp-vocab' and applied as @urp.display and five further terms. Whether its terms reach the OData metadata is not established: its readme names the terms and the widget types but says nothing about registering the vocabulary with the compiler, nothing about cds.cdsc.odataVocabularies, and nothing about what reads the terms. Its declared repository, github.com/your-username/urp-vocab, is an unedited placeholder, so the package's own files are the only record there is.

Remaining work

Read the published package's files before treating it as an answer here. On what is written down, it is a vocabulary definition and not a translation path.

All options on the Fiori annotations page →

Connections1

urp-vocab connectionsurp-vocabPROVIDES→ provides1provides authoredFiori annotations

Install

npm add urp-vocab

Derived from the package name. No recipe recorded; the README has the configuration.

History

Latest

v0.1.2

  1. v0.1.1

  2. v0.1.0

On npm
0downloads per week, npm
Weekly downloads for urp-vocab26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 0.27 Apr – 3 May: 14 May – 10 May: 911 May – 17 May: 518 May – 24 May: 325 May – 31 May: 31 Jun – 7 Jun: 48 Jun – 14 Jun: 315 Jun – 21 Jun: 622 Jun – 28 Jun: 329 Jun – 5 Jul: 66 Jul – 12 Jul: 813 Jul – 19 Jul: 020 Jul – 26 Jul: 527 Jul – 2 Aug: 13 Aug – 9 Aug: 310 Aug – 16 Aug: 617 Aug – 23 Aug: 124 Aug – 30 Aug: 631 Aug – 6 Sept: 67 Sept – 13 Sept: 514 Sept – 20 Sept: 421 Sept – 27 Sept: 528 Sept – 4 Oct: 45 Oct – 11 Oct: 012 Oct – 18 Oct: 119 Oct – 25 Oct: 0
Fiori annotations
  1. rap-extFloorplans rendered from CDS UI annotations as abap2UI5 appsfrom ABAP
  2. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  3. @mpah/enum-value-helpCAP plugin generating value help for enum fields from an annotationfrom CAP
  4. @sap/cds-fioriFiori draft handling and UI-facing behaviour for CAP servicesfrom CAP
  5. @sap/cdsCAP Node.js runtimefrom CAP
  6. @sap/generator-fioriEntry point for generating a Fiori application from a templatefrom CAP
  7. @sap-ux/cds-annotation-parserParser for annotations in CDS sourcefrom CAP
  8. @sap/ux-cds-compiler-facadeWrapper around the CDS compiler for annotation handlingfrom CAP
  9. @sap-ux/cds-odata-annotation-converterConverter from CDS annotations to their OData formfrom CAP
  10. @sap/ux-cds-odata-language-server-extensionOData annotation features for the @sap/vscode-cds extensionfrom CAP
  11. @sap-ux/fiori-annotation-apiProgrammatic API for reading and writing project annotationsfrom CAP
  12. @sap-ux/odata-vocabulariesOASIS and SAP OData vocabularies with a VocabularyServicefrom UI5
  13. cap-js-geoloc-pluginAnnotation-driven geocoding, address correction and routing for CAPfrom CAP
  14. cap-user-infoUser details and quickview links for createdBy and modifiedByfrom CAP

Details

Sources2
npm registrydiscovered here, keywords:cdschecked
npm registry, urp-vocabversion, releases, installschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesbuild-time
declared for>=6.0.0
latestv0.1.2
first release
releases and cadence3, ~0d median
discovered vianpm registry · keywords:cds
first seen in the atlas
ecosystem and domaincap, ui-and-frontend-bridge
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:kamlendra-urp-vocab
JSON
/artifacts/kamlendra-urp-vocab.json
MCP
Connecting an agent