- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 May 2017 02:56:23 +0000
- To: public-poe-archives@w3.org
The IM has been updated to replace the "type" property with subclasses. I have included 3 subclasses: Set, Offer, Agreement in the IM. Do we need to include all the rest? (As the above 3 are the core policy subclasses...and the reader now has a better idea about what they mean in terms of additional constraints/cardinalities... the others in the Vocab/Profiles should be more clearer?) All the JSON-LD examples in the IM now use @type. Updated Vocab (removed the word "type"). Updated Figure. Updated XML Encoding narrative. Commit: 20a7992dc7965429e0c5f782a6083f6de795a4ab -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/154#issuecomment-300047637 using your GitHub account
Received on Tuesday, 9 May 2017 02:56:30 UTC