docs(md): clarifies the isolation of margo sliced resources on device

[singhmj-1]

Description

Device capabilities documentation doesn't clarify that the resources are sliced and guaranteed on device solely for Margo usage and cannot be shared by other system entities.

Issues Addressed

#159

Change Type

Please select the relevant options:

• Fix (change that resolves an issue)
• New enhancement (change that adds specification content)
• Content edits (change that edits existing content)

Checklist

• I have read the CONTRIBUTING document.
• My changes adhere to the established patterns, and best practices.

[ajcraig]

@singhmj-1 lets ensure we have a similar note in following section of the device capabilities concepts section here.

Then I think we can close this issue out! Thanks

[singhmj-1]

@singhmj-1 lets ensure we have a similar note in following section of the device capabilities concepts section here.

Then I think we can close this issue out! Thanks

@ajcraig
That section already contains a reference to the document which we have modified in the PR.

P.S. : @ajcraig If this resolves your concern, then I believe that this can be merged.

[chrisgclayton]

@singhmj-1 lets ensure we have a similar note in following section of the device capabilities concepts section here.
Then I think we can close this issue out! Thanks

@ajcraig That section already contains a reference to the document which we have modified in the PR.

P.S. : @ajcraig If this resolves your concern, then I believe that this can be merged.

I believe that the concern, which I share, is that to ensure that device capabilities have a clause that say something similar to what was added for resources. For example "device capabilities should only report capabilities that are exposed and accessible for use in the Margo context". I could have a device that has a camera for security reasons but I do not want any Margo workloads to use it. This means the device as far as Margo is concerned does not have a camera.