Sarven Capadisli
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# W3C Solid Community Group: Weekly * Date: 2023-03-15T14:00:00Z * Call: https://meet.jit.si/solid-cg * Chat: https://gitter.im/solid/specification * Repository: https://github.com/solid/specification * Status: Draft ## Present * [Sarven Capadisli](https://csarven.ca/#i) * elf Pavlik * April Daly * Alain Bourgeois * Jeff Z. * Hadrian Zbarcea * michal/mrkvon * --- ## Announcements ### Meeting Guidelines * [W3C Solid Community Group Calendar](https://www.w3.org/groups/cg/solid/calendar). * [W3C Solid Community Group Meeting Guidelines](https://github.com/solid/specification/blob/main/meetings/README.md). * No audio or video recording, or automated transcripts without consent. Meetings are transcribed and made public. If consent is withheld by anyone, recording/retention must not occur. * Join queue to talk. * Topics can be proposed at the bottom of the agenda to be discussed as time allows. Make it known if a topic is urgent or cannot be postponed. ### Participation and Code of Conduct * [Join the W3C Solid Community Group](https://www.w3.org/community/solid/join), [W3C Account Request](http://www.w3.org/accounts/request), [W3C Community Contributor License Agreement]( ) * [Solid Code of Conduct](https://github.com/solid/process/blob/main/code-of-conduct.md), [Positive Work Environment at W3C: Code of Ethics and Professional Conduct](https://www.w3.org/Consortium/cepc/) * Operating principle for effective participation is to allow access across disabilities, across country borders, and across time. Feedback on tooling and meeting timing is welcome. * If this is your first time, welcome! please introduce yourself. ### Scribes * April Daly ### Introductions * name: text --- ## Topics ### CG Participation URL: https://www.w3.org/community/solid/participants * HZ: is there a concept of non-binding vote for non-(yet-)members? * SC: This is a community group, hence the process is not as strict as a working group. Please refer to the contributing guidelines. Regarding voting, if there are strongly opposing views we can take a vote to help the group move towards reconciliation. Voting is less of a concern relative to operating under the community guidelines. ### Implementation Feedback * SC: We'll allocate some time for implementation feedback or interest to implement. Links to products/projects and demos welcome. * SC: Any updates to share regarding implementations? Quick demonstrations are welcome! * AB: NSS shall implement the latest notification/webhoook protocol https://github.com/nodeSolidServer/node-solid-server/issues/1722. Request for help/assistance. Notifications have changed in the spec (i.e., web sockets), so must be implemented in NSS. Need assistance to help move this forward. * SC: Is there a Issue logged for tracking this? if not it would helpful to do a call with implementors. We have an issue "Call for implementations": https://github.com/solid/notifications/issues/141 * SC: we also have other looking at other aspects of the implementation. NSS will can fill more than one role: subscription server, notification server, etc. * SC: It would be great to update the table in the call for implementations. * AB: I will do that after the meeting. * SC: Great example - we have an intention and c all for help (e.g., we should create an issue) * eP: Can someone provide 1 min gist of reasoning for putting efforts in both CSS and NSS ? * JZ: CSS is not yet capable of delivering what NSS does? * eP: ok, thank you, is there a list of missing features available? * JZ: there issues in Solid Auth and related issues in other doc. More time is need to prepare to provide a more detailed answer. * SC: for the sake of accuracy - what features are in scope? (e.g., documentation, features list) * AB: there is a solidcommunity.net issue (https://github.com/solid/solidcommunity.net/issues/62)). There is no way to login with the user name but only with an email. * JF: that is not an issue of CSS but one of taking a large number of users (e.g., 50k) and migrating/creating in CSS. CSS server likely not capable to undertake this task. ### Shapes repository URL: https://github.com/solid/specification/issues/506 * SC: There is some support for the proposal at the issue. If no objections, we can follow-up and close issue. * SC: Simple follow-up - we created a shapes repository and any shape that is described in a spec or work-item can be added to this repository. We want to avoid adding every implementation shape (it would be chaos!). * AB: where is this located? * SC: It will be located in the Solid Org - a repo called shapes. * AB: WHat about shapes that are under development. If they are not available under the shapes pain, it will be difficult (e.g., Solid Chat). * SC: Someone will make a PR to add a shape. Questions: Is there a spec that is requiring the shape or is this driven by an application. Encourage the creation of a spec that uses the shape. * AB: How can we share shapes that are being developed but are not in specs. * SC: Our focus is on shapes that "touch" or are mentioned in specs. The process may change. * eP: I strongly prefer that we separate efforts on core shapes (domain agnostic) and infinite number of domain specific shapes. * MK: Understand the need to focus on shapes that are "standardized", however it would be very helpful to have a way to share shapes being developed. How can we shares these easily between contributors? * SC: We have to be careful to manage what would likely be an infinite number of shapes versus the shapes that are aligned with specs. We could create an issue that calls for a repo or other process to assist develops with sharing/collaborating shape development. Propose consult with Jackson on how to open up the (shape) repo to support this emerging need. * eP: for later we also should connect it with app directory to know which app implements which shape (and shape tree): https://shaperepo.com/ * eP: Michiel de Jong might do a project to help with domain specific shapes (and shape trees). I strongly prefer that we separate efforts on core shapes (domain agnostic) and infinite number of domain specific shapes for later we also should connect it with app directory to know which app implements which shape (and shape tree). * SC: Are we aligned on the purpose of the repo? Any objections/comments. There was call to have a repo on shapes. If that is not satisfactory, we can revisit this topic. * SC: No objections to creation of the shapes repo! ACTION: SC to create `solid/shapes` repo. ### AuthN and AuthZ Server side clients (apps) URL: https://github.com/solid/specification/issues/504 * SC: This is a follow-up/checkin on this issue as previous meetings have discussed this topic. I believe eP created this issue, can eP provide an status update? Jackson won't be able to work on it till later this week. * eP: The issue includes 3 specific design choices which so far received 0 feedback. * eP: the issue is currently inactive. * SC: Suggest we come back to the issue. If anyone in this meeting has processed the issue and has comments, please share your experience/comments. * SC: Since we do't have feedback, we';ll come back to this issue in the future. There is a lot of material to digest. When eP feels better, maybe he can provide a primer on the issue to help people understand where to start. * eP: It links back to another relevant issue about CLI clients: https://github.com/solid/data-interoperability-panel/issues/178 * SC: Specify kind of actors and class of interactions: https://github.com/solid/specification/issues/36 (c. 2019) * SC: there has been wok on this topic over the past few years, but eP is helping to move this issue further. Question: will we look at server-to-server interoperability. Most conversations have been on client-server, but server-to-server interaction is increasingly important (as expected). ### Auxiliary Resources with own Access Controls URL: https://github.com/solid/specification/issues/501 * SC: About time we have a closer look at this for a future milestone? * SC: This is a deep topic, probably can't get into too deeply today given the time remaining in this meeting. This topic touches upon access controls for profiles and resources (primary, auxiliary). Clarification is needed regarding what (specific) access is allowed, which depends on the type of resource * JZ: I recall you can have a ACL on a describedby resource. Is this still part of the discussion? * SC: This is a great example of this issue. So far that pattern has been in an implementation (e.g., NSS) but not spec'd. Along with ACLs having own ACLs. The WAC spec for example does not constrain which resources can have an ACL - so any resource can. We need to clarify in the Solid Protocol as there are cases in which separating the controls on the primary resource and the associated resource. See issue for some examples. * eP: I think we can't avoid paying attention to UX patters that might be required. If we expect end user to manage access policies we need to provide them with something that an average (non-geek) person can manage in responsible way. * AD: How complex is this going to be for users - with what Solid provides. Solid has many topics, .. so end user using some component, so is the complexity going to be too much for them or some abstraction that simplifies it for them. Especially using different applications that may not be uniform then it'd be difficult. * SC: WAC authorization model is designed to simplify (e.g., meant to be basic read/write/control). Users may also think in more of a workflow perspective, for example review of item. * eP: I'm happy to share some of the approach we took in the SAI spec. We could have short agenda point next week. SAI: https://solid.github.io/data-interoperability-panel/specification/ * eP: One's notes can go in some notes resource rather in the auxiliary resource. * MK: now, with acp having landed into spec, we also need to address potential incompatibilities between the two... (for next time...) ### Resource state changes and differences * SC: We can revisit the state of below issues (topics) and look at next steps. #### Standardizing state changes in resources (history, undo, sync) URL: https://github.com/solid/specification/issues/161 #### Evaluate existing RDF delta/diff formats URL: https://github.com/solid/notifications/issues/157 * SC: Move work to solid/specification? --- ### Topic URL: * Proposed by

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare with
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully