Re: archived technical documentation & schema

I would model the products as schema:ProductModel and the documents as CreativeWork, and link them via the about property.

That should do the trick. For product features not covered by, simply use additionalProperty (see examples for typical patterns).

martin hepp          @mfhepp

> On 18 Jan 2017, at 16:41, JP Sherman <> wrote:
> I have a fairly interesting situation.
> We have thousands of multi-page technical documents for software products that we no longer support. However, they're still used. We want to create a "no longer supported" archive for these docs. My issue is that I can't find a good schema to describe the status of these documents. 
> I've created different schema templates for different types of documents (solutions, documentation, articles, security vulnerabilities etc) and while these docs would be in the "documentation" schema template, I want to add a new schema like documentArchive or even a schema like documentStatus 
> to give a bit more context, we have many types of statuses for our content such as:
> - verified
> - work in progress
> - unverified
> I'd appreciate any thoughts or suggestions on this. 
> Cheers!
> JP
> JP Sherman
> Customer Portal Search & Findability
> office | 919.301.3259 x8143259
> mobile | 919.749.2219
> IRC | jpsherman
> Red Hat | Red Hat Customer Portal | Raleigh Office

Received on Wednesday, 18 January 2017 15:59:55 UTC