Inital project setup

.gitignore

@@ -0,0 +1,55 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules
+jspm_packages
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# ignore dist
+dist/
+
+# ignore compiled tests and scratch compiles
+test/**/*.js
+src/**/*.js
+
+# ignore private packages
+packages/*
+!packages/components
+!packages/generator
+
+# JetBrains IDEs
+.idea/
+
+# tsc build info
+tsconfig.tsbuildinfo

CODE_OF_CONDUCT.md

@@ -0,0 +1,47 @@
+# Community Code of Conduct
+
+**Version 1.2
+August 19, 2020**
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as community members, contributors, committers, and project leaders pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+-   Using welcoming and inclusive language
+-   Being respectful of differing viewpoints and experiences
+-   Gracefully accepting constructive criticism
+-   Focusing on what is best for the community
+-   Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances
+-   Trolling, insulting/derogatory comments, and personal or political attacks
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+With the support of the Eclipse Foundation staff (the “Staff”), project committers and leaders are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project committers and leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the Eclipse Foundation project or its community in public spaces. Examples of representing a project or community include posting via an official social media account, or acting as a project representative at an online or offline event. Representation of a project may be further defined and clarified by project committers, leaders, or the EMO.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Staff at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The Staff is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project committers or leaders who do not follow the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the Staff.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenan](https://www.contributor-covenant.org/), version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

LICENSE.md

@@ -0,0 +1,12 @@
+Copyright (c) 2025 Contributors to the Eclipse Foundation
+
+See the NOTICE file(s) distributed with this work for additional
+information regarding copyright ownership.
+
+This program and the accompanying materials are made available under the
+terms of the Eclipse Public License v. 2.0 which is available at
+http://www.eclipse.org/legal/epl-2.0, or the W3C Software Notice and
+Document License (2015-05-13) which is available at
+https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document.
+
+SPDX-License-Identifier: EPL-2.0 OR W3C-20150513

NOTICE.md

@@ -0,0 +1,43 @@
+# Notices for Eclipse Thingweb
+
+This content is produced and maintained by the Eclipse Thingweb project.
+
+-   Project home: https://projects.eclipse.org/projects/iot.thingweb
+
+## Trademarks
+
+Eclipse Thingweb is a trademark of the Eclipse Foundation.
+
+## Copyright
+
+All content is the property of the respective authors or their employers. For
+more information regarding authorship of content, please consult the listed
+source code repository logs.
+
+Note: The {year} in the copyright statements is the year in which the content
+was created (e.g. “2004”). A range of years is not used.
+
+## Declared Project Licenses
+
+This program and the accompanying materials are made available under the terms
+of the Eclipse Public License v. 2.0 which is available at
+http://www.eclipse.org/legal/epl-2.0, or the W3C Software Notice and Document
+License (2015-05-13) which is available at
+https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document.
+
+SPDX-License-Identifier: EPL-2.0 OR W3C-20150513
+
+## Source Code
+
+The project maintains the following source code repositories:
+
+## Third-party Content
+
+## Cryptography
+
+Content may contain encryption software. The country in which you are currently
+may have restrictions on the import, possession, and use, and/or re-export to
+another country, of encryption software. BEFORE using any encryption software,
+please check the country's laws, regulations and policies concerning the import,
+possession, or use, and re-export of encryption software, to see if this is
+permitted.

README.md

@@ -1,2 +1,10 @@
-# ui-wot
-Independent UI components library to build interfaces for IoT applications
+<h1>
+  <picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/eclipse-thingweb/thingweb/master/brand/logos/ui-wot_for_dark_bg.svg">
+  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/eclipse-thingweb/thingweb/master/brand/logos/ui-wot.svg">
+  <img title="ThingWeb ui-wot" alt="Thingweb ui-wot logo" src="https://raw.githubusercontent.com/eclipse-thingweb/thingweb/master/brand/logos/ui-wot.svg" width="300">
+</picture>
+</h1>
+
+> UI for your IoT applications and devices
+

SECURITY.md

@@ -0,0 +1,20 @@
+<!--- https://www.eclipse.org/security/ --->
+
+_ISO 27005 defines vulnerability as:
+"A weakness of an asset or group of assets that can be exploited by one or more threats."_
+
+## Eclipse Foundation Security Team
+
+The Eclipse Foundation Security Team provides help and advice to Eclipse projects on security issues and is the first point of contact for handling security vulnerabilities. Members of the Security Team are selected from committers on Eclipse Projects, members of the [Eclipse Architecture Council](https://www.eclipse.org/projects/handbook/#roles-ac), and Eclipse Foundation staff.
+
+## Reporting a Security Vulnerability
+
+Vulnerabilities can be reported either via email to [[email protected]](mailto:[email protected]) or directly with a project via the Eclipse Foundation’s [issue tracker](https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/new?issuable_template=new_vulnerability).
+
+The general [security team email address](mailto:[email protected]) can also be used to report vulnerabilities. Members of the Eclipse Foundation Security Team will receive messages sent to this address. This address should be used only for reporting undisclosed vulnerabilities; regular issue reports and questions unrelated to vulnerabilities in Eclipse Foundation project software will be ignored. Note that this email address is not encrypted.
+
+## Disclosure
+
+Disclosure is initially limited to the reporter, the project team and the Eclipse Foundation Security Team, but is expanded to include other individuals, and the general public. The timing and manner of disclosure is governed by the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy.php).
+
+Publicly disclosed issues are listed on the [Known Eclipse Security Vulnerabilities](https://www.eclipse.org/security/known.php) page.

package.json

@@ -0,0 +1,26 @@
+{
+  "name": "@thingweb/ui-wot",
+  "private": true,
+  "version": "0.1.0",
+  "description": "A set of projects to build user interfaces for IoT applications using Web of Things (WoT) standards.",
+  "scripts": {},
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/eclipse-thingweb/ui-wot.git"
+  },
+  "keywords": [
+    "ui-components",
+    "iot",
+    "dashboard"
+  ],
+  "author": "Eclipse Thingweb <[email protected]> (https://thingweb.io/)",
+  "license": "EPL-2.0 OR W3C-20150513",
+  "bugs": {
+    "url": "https://github.com/eclipse-thingweb/ui-wot/issues"
+  },
+  "homepage": "https://github.com/eclipse-thingweb/ui-wot#readme",
+  "workspaces": [
+    "packages/components",
+    "packages/generator"
+  ]
+}

packages/components/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "@thingweb/ui-wot-components",
+  "version": "0.1.0",
+  "description": "Independent UI components library to build interfaces for IoT applications",
+  "main": "index.js",
+  "scripts": {},
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/eclipse-thingweb/ui-wot.git"
+  },
+  "keywords": [
+    "ui-components",
+    "iot",
+    "dashboard"
+  ],
+  "author": "Eclipse Thingweb <[email protected]> (https://thingweb.io/)",
+  "license": "EPL-2.0 OR W3C-20150513",
+  "bugs": {
+    "url": "https://github.com/eclipse-thingweb/ui-wot/issues"
+  },
+  "homepage": "https://github.com/eclipse-thingweb/ui-wot/packages/components#readme"
+}

packages/generator/package.json

@@ -0,0 +1,19 @@
+{
+  "name": "@thingweb/ui-wot-generator",
+  "version": "0.1.0",
+  "description": "A library capable of create ui components from a W3C Thing Description",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/eclipse-thingweb/ui-wot.git"
+  },
+  "devDependencies": {},
+  "scripts": {},
+  "keywords": [
+    "ui",
+    "generator",
+    "dashboard"
+  ],
+  "author": "Eclipse Thingweb <[email protected]> (https://thingweb.io/)",
+  "license": "EPL-2.0 OR W3C-20150513",
+  "homepage": "https://github.com/eclipse-thingweb/ui-wot/packages/generator#readme"
+}