Work in Progress

This is where i'll put information about the work in progress. This Website / repo, has only been started on the 4th of Jan 2023. I've used the tools created for the Webizen Docs site as a template.

Permissive Commons Technology (PCT) (#this)

This documentation environment has been built using Obsidian, GitHub, Gatsby and the [Obsidian Template for Gatsby](Obsibian Template for Gatsby). The DocumentationMethod document explains how its done.

The process of producing the documentation; will include output to address,

1. About Docs: General information about the Permissive Commons Project. a. Information about Ontologies. b. Information about related historical works c. information for non-technical people to understand what its about. d. Information about the use-cases related to the use of Ontologies e. Considerations about the desirable stewardship models for PCT-Ontologies.

2. Illustrating some of the percieved problems with existing HTTP based ontologies. a. considerations about how permissive commons may usefully address those issues.

3. Technical Docs: Design of Permissive Commons; and, a. The intended benefits of decentralised commons resources b. its intended role with other broader ecosystems. c. information about the requirements for ontologies more specifically.

4. Creating an Architectural Strategy for implementing Permissive Commons Ontologies. a. Functionality Objectives b. Comparison of Non-HTTP(s)Protocols for the purpose of PCT Ontologies. c. Evaluation of candidate approaches in relation to usecases.

5. The Application of PCT-Ontologies via Webizen Ecosystems.

6. Learning resources to help people learn about related technologies.

7. Working to update the content to address considerations about the many topics, etc.

NOTES:
a. This documentation environment does not easily provide RDF related functionality and the works on this site is not intended to provide name-space services. b. The PCT documentation was originally populated from the Webizen DevDocs repo that was started earlier; thereafter leading to my splitting the documentation out to two repos, which is already resulting in version control issues... In anycase, theres's links throughout these draft documents (very early stages still) that relate to the Webizen DevDocs more than is necessarily the case for the PermissiveCommonsTech related work specifically; although, the two fields of endevour are inextricably linked - Webizen doesn't work without some sort of PCT implementation.

ISSUES

1. Whilst i'm aware of many Semantic Web Luminaries, it is most often the case that their skills in this area far outstrip my own. Whilst i will work on a best efforts basis, i am entirely likely to make mistakes due to the software engineering related skillset not being core to what it is i do best.

2. Existing Ontologies often refer to URIs that no-longer exist. other ontologies are very old and now out dated. A respectful approach to resolving these sorts of issues is desirable.

3. Whilst the ChatGPT Content provides a helpful start to writing content about a topic, it does need to be updated and reviewed; as such, the new pages where this has been used needs to be reviewed (when i get there)... It has been found to provide garbage RDF relations when providing ontology related results; whilst also providing valuably useful support, for radically improving the productivity metrics for producing ontology works generally.

4. There's alot of work required to identify and thereafter create useful feature / functionality charts that relate to the functionality of various different types of Non-HTTP(s)Protocols relating to decentralisation of informatics. I suspect this will take sometime to do well.