- From: Nathan Rixham <nathan@webr3.org>
- Date: Tue, 4 Oct 2016 20:06:48 +0100
- To: Timothy Holborn <timothy.holborn@gmail.com>
- Cc: Jonas Smedegaard <dr@jones.dk>, public-rww <public-rww@w3.org>
- Message-ID: <CANiy74xjVPwCeGtD3G53Edg33sjX+QC0RxC0740TJBW+hwDT1A@mail.gmail.com>
<script type="application/ld+json">{"@context": "http://example.org", "@type": "Whatever", ... }</script> seems good enough for the use cases I've encountered in production so far. On Tue, Oct 4, 2016 at 10:53 AM, Timothy Holborn <timothy.holborn@gmail.com> wrote: > HTML should allow for an array of ontologies to be used. Schemaorg is > needed for search discovery. Others are required for a variety of different > purposes. > > To decentralized, It would be good to change the way the document is > presented based on the client. > > Its of course important to ensure a page is available to search. But I > don't think it's important to ensure all the ontology (linguistics) is > embedded in schemaorg. > > Tim.h. > > On Tue., 4 Oct. 2016, 8:41 pm Jonas Smedegaard, <dr@jones.dk> wrote: > >> Quoting Timothy Holborn (2016-10-04 11:19:47) >> > Had an idea. >> > >> > The idea relates to the various ontology mark-up currently placed >> in-line >> > with a HTML document. Problem is various agents want different formats >> / >> > different ontologies. >> > >> > So, >> > >> > HTML5 currently has a >> > >> > .HTML >> > .js >> > .css >> > >> > the suggestion is to add a .bot file (or other name - as that's not >> > consequential) >> > >> > The intention is to improve support for schema by identifying what the >> > client is, much like the means CSS improves user-experience for 'style'. >> > >> > In this way, if the 'agent' is FB - then OG tags; or search providers = >> > schemaorg, etc. >> > >> > The external file would need to be linked to tags in the HTML doc; >> allowing >> > it to be flexibly parsed using various schema markup to suit different >> > agents. >> > >> > Thoughts? >> >> Problem is, as I see it, that ontologies like schema.org are designed >> for a specific purpose. >> >> Seems backwards to me to support segmentation of communication like >> that: HTML was invented as a means to _unify_ the needs for exchanging >> documents, and RDF to do the same for data more generally. Your idea >> seems to try go the opposite direction and encourage single-purpose >> sub-languages of RDF. >> >> >> - Jonas >> >> -- >> * Jonas Smedegaard - idealist & Internet-arkitekt >> * Tlf.: +45 40843136 Website: http://dr.jones.dk/ >> >> [x] quote me freely [ ] ask before reusing [ ] keep private >> >
Received on Tuesday, 4 October 2016 19:07:18 UTC