JSON-LD may be the best way to build database data models and metadata tables, whether it be blockchain oriented, relational or a document store like MongoDB. With the rise of Decentralized Identifiers - DIDs even more so.
Have known of schema.org for a couple years, but the value of JSON-LD didn't become apparent until later. Although schema.org has a vast and rich library of schematics there are some business use cases that schema clarification could be very beneficial for certain industries.
For example, the waste industry. Land use for waste fields in metropolitan areas is increasingly becoming more scarce. This forces increases in costs to transport. This is a very important clarification/specification could affect residential, municipal, education, military and business.
JSON-LD has the potential to increase the processing accuracy of Artificial Intelligence or Machine Learning too, but for that potential to be realized there has to be meta-data that is pertinent to the process that computation performs. As of now, there is a little clarity or specification for tagging or tracking waste streams.
My opinion is that it would be beneficial to track the waste production/processing at the manufacturing point and be able to perform a total life cycle analysis of
Product makes material or additionalProperty available to the schema. Material would more than likely be reserved for the materials used in manufacturing the product being as granular, granular using the isAccessoryOrSparePartFor to build the complete Product type, or as complete in it's description as possible.
Being that the packaging is the 1st thing to be disposed of, having this property available could significantly improve the tracking of the waste stream and enable a more accurate reporting capability. If every week x corporation receives x-amount of product packaged in x-material and has a zero-waste program in place to be environmentally conscious it increases the efficiency of cataloging what goes back into it's recycling program.
It is best to keep the object flat or to embed different parameters?
For discussion. There has to be a practical way to track things through each component of the supply chain. Manufacturer -> Wholesale -> Retailer -> Customer -> Recycle -> Manufacturer
Total Life-cycle assessment
Just noticed another example in Products that has an itemListElement property that could be used for: 1) Shipping in bulk and 2) Aggregating all the pieces used in manufacturing to make a whole product.
An example for a single Toy Car and aggregating all the pieces you'd have an object like:
For brevity partials are used in the later examples, but included the product manufacturing pieces and the packaging. Maybe an identifier for packaging would be beneficial? Some type of standardization would be ideal.
JSON-LD may be the best way to build database data models and metadata tables, whether it be blockchain oriented, relational or a document store like MongoDB. With the rise of Decentralized Identifiers - DIDs even more so.
Have known of schema.org for a couple years, but the value of JSON-LD didn't become apparent until later. Although schema.org has a vast and rich library of schematics there are some business use cases that schema clarification could be very beneficial for certain industries.
For example, the waste industry. Land use for waste fields in metropolitan areas is increasingly becoming more scarce. This forces increases in costs to transport. This is a very important clarification/specification could affect residential, municipal, education, military and business.
JSON-LD has the potential to increase the processing accuracy of Artificial Intelligence or Machine Learning too, but for that potential to be realized there has to be meta-data that is pertinent to the process that computation performs. As of now, there is a little clarity or specification for tagging or tracking waste streams.
My opinion is that it would be beneficial to track the waste production/processing at the manufacturing point and be able to perform a total life cycle analysis of
For Example: Product Schema
Product makes
material
oradditionalProperty
available to the schema. Material would more than likely be reserved for the materials used in manufacturing the product being as granular, granular using theisAccessoryOrSparePartFor
to build the completeProduct
type, or as complete in it's description as possible.Being that the packaging is the 1st thing to be disposed of, having this property available could significantly improve the tracking of the waste stream and enable a more accurate reporting capability. If every week x corporation receives x-amount of product packaged in x-material and has a zero-waste program in place to be environmentally conscious it increases the efficiency of cataloging what goes back into it's recycling program.
It is best to keep the object flat or to embed different parameters?
An example would be:
For discussion. There has to be a practical way to track things through each component of the supply chain. Manufacturer -> Wholesale -> Retailer -> Customer -> Recycle -> Manufacturer Total Life-cycle assessment
Just noticed another example in Products that has an
itemListElement
property that could be used for: 1) Shipping in bulk and 2) Aggregating all the pieces used in manufacturing to make a whole product.An example for a single Toy Car and aggregating all the pieces you'd have an object like:
An example for shipping those individual pieces in a bulk shipment
For brevity partials are used in the later examples, but included the product manufacturing pieces and the packaging. Maybe an identifier for packaging would be beneficial? Some type of standardization would be ideal.
repo started to build on concepts presented here