Extract frontend components in a separate library

[srosset81]

Once the data provider and auth provider will support "regular" Solid servers, the frontend components will be usable by any Solid developers.

I think it's the good time to split the backend services and frontend components from SemApps, which cause confusion, since it make people believe that the two need to be used together.

So I propose to keep "SemApps" as the name for backend services, to find a new name for frontend components and to move the frontend documentation to a new Starlight-based website.

What name shall we use ?

Ideas:

• Linked Data Framework (but already used here ... besides LDF is also the acronym for Linked Data Fragments)
• FI-LD (Framework for the Integration of Linked Data)
• ...

Ping @simonLouvet @fluidlog @VincentFarcy @GuillaumeAV (we are requesting funds from NLnet for this issue, amongst others)

Related issues

• https://github.com/assemblee-virtuelle/semapps/issues/1218

[srosset81]

Found out that the following domains are available for around 10€ a year:

• ldframe.work
• ldframework.org
• ldframework.io
• linkeddataframework.org (a bit long IMO)

ldf domain names are generally not available, or cost more than 150€ a year. The https://ldf.js.org domain is also taken by a project that is not updated since 2019.

[GuillaumeAV]

If you receive funds I want to be paid for my contribution on the brainstorming for the name !

SemApps could be used for the frontend component no? And we could have SemBack for the backend ?

We also had Linked data management system ..

Le mer. 22 mai 2024, 15:34, Sébastien Rosset @.***> a écrit :

Once the data provider and auth provider will support "regular" Solid servers https://github.com/assemblee-virtuelle/semapps/issues/1121, the frontend components will be usable by any Solid developers.

I think it's the good time to split the backend services and frontend components from SemApps, which cause confusion, since it make people believe that the two need to be used together.

So I propose to keep "SemApps" as the name for backend services, to find a new name for frontend components and to move the frontend documentation https://semapps.org/docs/frontend to a new Starlight https://starlight.astro.build/fr/-based website.

What name shall we use ?

Ideas:

• Linked Data Framework (but already used here https://docs.plm.automation.siemens.com/content/polarion/20/help/en_US/teamcenter_polarion_integration_installation_43/solution_components/configure_the_teamcenter_linked_data_framework_ldf_component/overview.html and here http://silkframework.org/)
• FI-LD (Framework for the Integration of Linked Data)
• ...

Ping @simonLouvet https://github.com/simonLouvet @fluidlog https://github.com/fluidlog @VincentFarcy https://github.com/VincentFarcy @GuillaumeAV https://github.com/GuillaumeAV (we are requesting funds from NLnet for this issue, amongst others)

— Reply to this email directly, view it on GitHub https://github.com/assemblee-virtuelle/semapps/issues/1256, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABO75HAM7OAWPKIJHBHC4HTZDSNE7AVCNFSM6AAAAABIDVKQ6OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTANJVHAYDCMA . You are receiving this because you were mentioned.Message ID: @.***>

[srosset81]

If you receive funds I want to be paid for my contribution on the brainstorming for the name !

Your contribution is priceless ! ;-)

SemApps could be used for the frontend component no?

I find the name SemApps to be confusing, as we don't know what "apps" we are talking about. Also "semantic" is less and less used, except in academic fields.

[simonLouvet]

key words

• Linked Data
• React Admin
• User Interface
• Framwork
• semantic

I try to put them together

• LIDIF : LInked Data Interface Framework