> -----Original Message----- > From: Joshua Watt <[email protected]> > Sent: Thursday, May 9, 2024 10:22 AM > > On Wed, May 8, 2024, 7:13 PM [email protected] > <mailto:[email protected]> <[email protected] > <mailto:[email protected]> > wrote: > > Hi Joshua-san and tech team, > > Let me ask you a few questions about the Json-LD sample. > > 1. about "type" key > For example, "type": "Person" at line.5 could be considered a Person > class object in a Core profile, but by definition there is no "type" key. > How should I think about this, and could you describe it somewhere > in the specification document? > > "type" is an alias for the json-ld "@type" field. It's not defined in the spec > because it's specific to json-ld and thus it was decided not to put it in the > model. There probably needs to be some json-ld serialization annex written > to describe that > > > 2. about "@id": "_:creationinfo"/1 > > The value of "@id" must be IRI. But from the spdx-3.0-schema.json > at https://github.com/spdx/spdx-3-serialization-prototype- > playground/blob/main/jsonld/spdx-3.0-schema.json#L4025-L4027 > <INVALID URI REMOVED > serialization-prototype-playground/blob/main/jsonld/spdx-3.0- > schema.json*L4025- > L4027__;Iw!!JmoZiZGBv3RvKRSx!9Mr_mPJtMSk4H49WSnitZmq7Y_GxR5ymR > m0MkAdOjlJv7LQWF3gj7zxVodBV3hxf48MKfpvTNWf4wbla9DAN$> , > "_:creationinfo" is thought to be defined as a BlankNode, not IRI. > > Blank nodes (implicit or otherwise are allowed for objects that do not derive > from Element (e.g. that do not have an spdxid). This was done because those > do not typically need to be referenced outside a document (if they even > need to be referenced by name at all) and it would be a pain to users to have > to write them when they are not necessary. > > And the key "@id" is also undefined in the SPDX specification. > > This is the same reason as "type" > > > Is there any way to describe it somewhere in the specification? > > > It does but I'm not sure how >
Thanks, Joshua-san. I understood. > There probably needs to be some json-ld serialization annex written to > describe that I agree that it will be more easier to understand if the json-ld annex is written. As I'm writing Lite-example with json-ld, I'm happy if I could contribute in the future. > Best, > -- Kobota > > > > From: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]> > On Behalf > Of Kate Stewart > Sent: Thursday, May 9, 2024 8:46 AM > To: Joshua Watt <[email protected] > <mailto:[email protected]> > > Cc: SPDX Technical Mailing List <[email protected] > <mailto:[email protected]> > > Subject: Re: [spdx-tech] Linking SPDX 3.0 documents > > > > Thanks Joshua! > > > > Very much appreciate your pulling this together. > > > > Alexios, Max - can you please review? > > > > Thanks > Kate > > > > On Wed, May 8, 2024 at 6:40 PM Joshua Watt > <[email protected] <mailto:[email protected]> > wrote: > > All, > > In the tech call it was asked how to link SPDX 3 documents > together. > To describe this, I've written another How-To Annex which > can be read > here: https://github.com/JPEWdev/spdx- > spec/blob/development/v3.0.1/docs/annexes/cross-reference.md > <INVALID URI REMOVED > spec/blob/development/v3.0.1/docs/annexes/cross- > reference.md__;!!JmoZiZGBv3RvKRSx!9Mr_mPJtMSk4H49WSnitZmq7Y_GxR > 5ymRm0MkAdOjlJv7LQWF3gj7zxVodBV3hxf48MKfpvTNWf4wfL_DeH4$> > > The pull request to integrate this into the documentation is > here: > https://github.com/spdx/spdx-spec/pull/938 > <INVALID URI REMOVED > spec/pull/938__;!!JmoZiZGBv3RvKRSx!9Mr_mPJtMSk4H49WSnitZmq7Y_GxR > 5ymRm0MkAdOjlJv7LQWF3gj7zxVodBV3hxf48MKfpvTNWf4wfwltkyM$> > > This is the correct way to do it to the best of my knowledge; > please > review and let me know if it needs corrections. > > Thanks, > Joshua Watt > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5638): https://lists.spdx.org/g/Spdx-tech/message/5638 Mute This Topic: https://lists.spdx.org/mt/105992376/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
