7
1
Fork
You've already forked interop
0

Initial dump of possible areas we need to work on #1

Merged
txels merged 2 commits from rough-initial-plan into main 2026年03月29日 16:55:59 +02:00
Owner
Copy link
No description provided.
@ -0,0 +9,4 @@
- Content:
- Artists, releases, songs...
- Prior art: RSS, Canimus, Subsonic API, Mirlo API(?), internal Fairplayer scanner serialisation format...
Author
Owner
Copy link

Note: Navidrome supports the subsonic API, not sure if they also include other APIs beyond the scope of subsonic that may be relevant to us.

Note: Navidrome supports the subsonic API, not sure if they also include other APIs beyond the scope of subsonic that may be relevant to us.
Owner
Copy link

Navidrome has a Native API for the UI but for third party integrations they point to Subsonic.

https://www.subsonic.org/pages/api.jsp

As far as I've been able to research, I think that Subsonic is not open source. Navidrome adds new features to Sbsonic through the OpenSubsonicAPI which is an open extension of Subsonic

https://opensubsonic.netlify.app/

Navidrome has a Native API for the UI but for third party integrations they point to Subsonic. https://www.subsonic.org/pages/api.jsp As far as I've been able to research, I think that Subsonic is not open source. Navidrome adds new features to Sbsonic through the OpenSubsonicAPI which is an open extension of Subsonic https://opensubsonic.netlify.app/
Owner
Copy link

Another existent for interchange of content data is the ERN DDEX standard:

https://ern.ddex.net/electronic-release-notification-message-suite-part-1-definitions-of-messages/

Another existent for interchange of content data is the ERN DDEX standard: https://ern.ddex.net/electronic-release-notification-message-suite-part-1-definitions-of-messages/
MaciAc left a comment
Copy link

For us to use DDEX and any other party to interact with all of the parties need a ddex licesne identifier (DPID)

https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers/

For us to use DDEX and any other party to interact with all of the parties need a ddex licesne identifier (DPID) https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers/
@ -0,0 +22,4 @@
- "Reconciliation" across entities (consumer vs producer, player/catalog, player/player, different tools...)
- Auditability (immutable logs etc)
- Prior art: web3 / blockchains
- Identity:
Owner
Copy link

Also in the DDEX standard, there is the the PIE, Party Identification Enrichment, which aims to enhance the identifiers for artists such as legal name vs stage name, abbreviations etc

https://pie.ddex.net/party-identification-and-enrichment/

For release and other stuff enrichment there is the MEAD standard, media enrichment and description

https://mead.ddex.net/media-enrichment-and-description/

Also in the DDEX standard, there is the the PIE, Party Identification Enrichment, which aims to enhance the identifiers for artists such as legal name vs stage name, abbreviations etc https://pie.ddex.net/party-identification-and-enrichment/ For release and other stuff enrichment there is the MEAD standard, media enrichment and description https://mead.ddex.net/media-enrichment-and-description/
Sign in to join this conversation.
No reviewers
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fairplayer/interop!1
Reference in a new issue
fairplayer/interop
No description provided.
Delete branch "rough-initial-plan"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?