Please enable JavaScript.

Coggle requires JavaScript to display documents.

Yocto project has layers, what are those layers, YP builds packages then…

- - - - Quilt: patching tool
      - QA: is to make sure convection is followed and that no leftover files that haven't been packed or that wrong things haven't been packed
        
        Image/SDK builder from package feeds
- - - - BitBake
        
        Python
        
        Reads Metadata; Determines Dependencies; Schedules tasks
        
        Metadata Definition
        
        Structured collection of data which tells Bitbake what to build, organized in layers
        
        Four different kinds:
        
        .bb:
        Usually describes build instructions for a SINGLE package
        
        1 more item...
        
        special *.bb:
        Often used to group packages together for a FS image
        
        *.bbclass:
        Inheritancen mechanism for common functionality
        
        *.conf:
        Drives the overall behavior of the build process.
        
        Other 2 files but not Metadata
        
        2 more items...
        
        files needs to start with: recipes-
        
        Task scheduler and executor
        
        $ bitbake myrecipe ; is used to build the specified build and it's the HIGHEST version that's built
        
        If you want a specific version
        
        $ bitbake myrecipe-1.0
        
        Or revision
        
        $ bitbake myrecipe-1.0-r0
        
        To choose which task to run:
        $bitbake -c clean myrecipe
        OR
        $bitbake -c cleanall myrecipe
        
        To list all tasks: $bitbake -clisttaks myrecipe
        
        Operators
        
        ?= (dafault Value)
        
        = (Late Assignment)
        
        ?? = (late default)
        
        := (Immediate Assignment)
        
        =. (prepend)
        
        += (append with space)
        
        .= (append)
        
        =+ (prepend with space)
- - - - Aries Framework: Aries provides a set of protocols for secure communication and interactions between different parties in a decentralized identity ecosystem.
      - Hyperledger Indy (or other blockchain platforms): Indy is often used as the underlying blockchain technology for decentralized identity systems.
    - - Start by installing and configuring ACA-py on your edge gateway device. ACA-py can run on various platforms, including cloud servers, edge devices, and IoT devices.
    - - Using ACA-py, you can create and manage decentralized identities. This involves generating and managing keys and DID (Decentralized Identifier) documents.
    - - ACA-py allows you to issue and verify verifiable credentials. These credentials can represent various attributes, such as personal information, academic degrees, or professional certifications.
    - - ACA-py typically interacts with a blockchain, such as Hyperledger Indy, to anchor DID documents and transactions for verifiable credentials. Blockchain provides the immutability and trust needed for decentralized identity systems.
    - - The personal digital twin edge gateway serves as a point of control and data access for the individual. It can integrate with ACA-py to securely manage and share identity and credential information.
    - - Use ACA-py to implement consent management and data privacy features. Individuals should have control over who accesses their data and under what conditions.
    - - ACA-py ensures secure and private communication between the edge gateway and other parties in the ecosystem, including relying parties and other digital twins.
    - - Depending on the scale of your system, consider the scalability and performance aspects of ACA-py to handle a large number of identity interactions.
    - - Implement monitoring and management tools to keep track of the performance and security of your system. ACA-py provides APIs and tools for this purpose.
    - - Depending on your specific use case, you may need to customize ACA-py or extend it with additional features to meet your requirements.
    - - Ensure that your implementation complies with relevant standards and regulations, such as GDPR for data privacy.
- - - - AnonCreds
      - JWT
      - JWP
      - LDP-VC
    - - If the holder is the subject, they must provide proof that they are the subject
    - - Signed by issuer
      - Velue issues to holder
    - - Value presented to verifier
      - Derived from verifiable credential