Re: Schema.org generator

Screenshots a great help.

Wondering if it would run in Google App Engine - as the Schema.org site
does.

~Richard

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 18 March 2016 at 16:03, Hans Polak <info@polak.es> wrote:

> Hi Richard,
>
> It's a pity my hosting doesn't do Python, otherwise I could link you to
> it. The other syntaxes can be added in a next version. I focused on
> microdata because that was the problem I needed to solve and because I
> thought there was already a tool for json.
>
> My idea is to add a validate button to avoid the copypaste. Google allows
> it (I think). The other options can be added, no problemo.
>
>
>
>
>
> I hope these screenshots clarify it a tat.
>
> Cheers,
> Hans
>
>
> On 03/18/2016 04:41 PM, Richard Wallis wrote:
>
> HI Hans,
>
> Thank you for your answers.
>
> Again a quick response
>
> On 18 March 2016 at 15:13, Hans Polak < <info@polak.es>info@polak.es>
> wrote:
>
>> Hi Richard,
>>
>>
>>    - This *only* generates Microdata. I thought JSON (at least) already
>>    has a tool.
>>
>> Schema.org approaches all three syntaxes with equal importance.  If a
> generator tool was to be integrated with the schema.org site (*and I am
> not saying it should or should not*) it should have that equality of
> approach.
>
>>
>>    - This doesn't, actually, validate against the Google testing tool.
>>    The user has to *manually* copy and paste it. So, any tool should
>>    work.
>>
>> Ah I see.  In that case I would suggest a simple
> copy-output-to-paste-buffer option with prominent links to the several
> available validation tools - Google, Bing, Yandex, Structurd Data Linter,
> RDF Translator, etc.
>
>>
>>    - If I understand this correctly, my tool can handle related types
>>    without any problem (AJAX).
>>
>> Does that mean when user drops on the *seller* property of *Offer* they
> get taken to an *Organisation* form to fill in?
>
>>
>>    - It will *only* output the information provided by the user. So, if
>>    the user adds both...
>>
>> So referencing the previous point they would get the choice of a *Person*
> or *Organization* to fill in?
>
>>
>>    - The user is in charge of choosing the subtype. The tool will handle
>>    that.
>>
>> Providing a list to choose from?
>
>>
>>    - Yes, it does track schema.org. The bot can be set-up to check every
>>    24 hours, more often, less often...
>>
>> Excellent.
>
>>
>>    - At this moment, only the core will be handled.
>>    <http://schema.org/docs/full.html>http://schema.org/docs/full.html
>>
>> So once an equivalent file that included extensions was available, it
> will?
>
>
> Sorry for short replies - I’ll see if I can find time to make a more
> detailed look.
>
> ~Richard
>
>>
>>    -
>>
>> Hans
>>
>>
>> On 03/18/2016 02:06 PM, Richard Wallis wrote:
>>
>> Hi Hans,
>>
>> This looks interesting.  I have not as yet had time to delve into the
>> technical documentation, but the following questions come to mind looking
>> at the documentation.
>>
>>    - Will it produce all three serialisations as output - Microdata,
>>    RDFa, JSON-LD
>>    - Will it validate against more than just the Google testing tool
>>    - How does it handle related types.  i.e.. A *PriceSpecification*
>>    linked to an *Offer* for a *Product* offered by a *seller*
>>    *Organisation*
>>    - How will it handle properties with more than one type in its range
>>     e.g.. for *creator* how to choose to create *Person* or
>>    *Organization* schema
>>    - How will you choose which subtype to create e.g A property
>>    expecting a CreativeWork could reference a *Book, *a* Painting,* or a
>>    *SoftwareApplication*
>>    - Does it track the evolution of the vocabulary - getting its
>>    structure from the live schema.org site
>>    - Will it handle extensions such as bib.schema.org
>>
>> ~Richard
>>
>> Richard Wallis
>> Founder, Data Liberate
>> <http://dataliberate.com>http://dataliberate.com
>> Linkedin:  <http://www.linkedin.com/in/richardwallis>
>> <http://www.linkedin.com/in/richardwallis>
>> http://www.linkedin.com/in/richardwallis
>> Twitter: @rjw
>>
>> On 18 March 2016 at 12:21, Hans Polak < <info@polak.es>info@polak.es>
>> wrote:
>>
>>> I've uploaded everything to Github.
>>>
>>> https://github.com/GUI-Junkie/Schema.org-Generator
>>>
>>> Yours sincerely,
>>> Hans Polak
>>>
>>>
>>> On 03/18/2016 10:58 AM, Hans Polak wrote:
>>>
>>> Good morning,
>>>
>>> Yesterday, I released a software package for schema.org under the GNU
>>> GPL.
>>>
>>> This software generates valid schema's in HTML5 format. I would like to
>>> integrate this at <http://schema.org/generator/>
>>> http://schema.org/generator/ if possible. Here is the Online Help
>>> <http://polak.es/generator_help/index.html>
>>>
>>> The system requirements are: Python3 (with or without Apache2). Here is
>>> the Technical documentation <http://polak.es/generator_tech/index.html>
>>>
>>> tar.gz <http://polak.es/generator.tar.gz> file, checksums
>>> <http://polak.es/en/generator.html>
>>>
>>> Yours sincerely,
>>> Hans Polak
>>>
>>>
>>>
>>
>>
>
>