W3C home > Mailing lists > Public > public-vocabs@w3.org > March 2014

Re: Candidate schema.org 1.0g release: Reservations, Questions/Answers, EmailMessage

From: Vicki Tardif Holland <vtardif@google.com>
Date: Wed, 26 Mar 2014 12:20:58 -0400
Message-ID: <CAOr1obH0Ahjt2eaCje96SCiG0Vxw5hQcW6-c9-EFX_Sa07L9rQ@mail.gmail.com>
To: Aaron Bradley <aaranged@gmail.com>
Cc: Dan Brickley <danbri@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
LegalService seems like a nice catch all that expresses the meaning
properly to anyone who might want to try to translate the schema into
another language.

- Vicki


Vicki Tardif Holland | Ontologist | vtardif@google.com



On Mon, Mar 24, 2014 at 3:50 PM, Aaron Bradley <aaranged@gmail.com> wrote:

> Regarding the aim for neutral or US-EN spelling, I see at least one case
> where this impetuous has actually influenced the actually framing of a
> schema:
>
> http://schema.org/Attorney
>
> Among the many problems with this designation is the fact that in Great
> Britain only a solicitor may be an attorney, meaning that this type does
> not encompass barristers.
>
> "Lawyer" is a much better catch-all term for the professional who may give
> legal advice, aid and represent clients at course.  Or, along the line of
> "AccountingService" the more generalized "LegalService" or "LawOffice" or
> similar term may be more globally applicable.
>
>
>
>
> On Mon, Mar 17, 2014 at 12:32 PM, Dan Brickley <danbri@google.com> wrote:
>
>> On 13 March 2014 16:44, Dan Brickley <danbri@google.com> wrote:
>> > I've made a test build of a 1.0g release, at
>> http://sdopending.appspot.com/
>>
>> I've updated the test build (aiming to go live this week):
>>
>> a) we're calling it 1.1 now. The naming scheme was becoming silly! (I
>> was holding '1.0 proper' back for Actions, but there are plenty of
>> numbers left for that).
>>
>> b) http://sdopending.appspot.com/Question now has an example, thanks
>> to Stephane. I've taken out any user content and names...
>>
>> c) thanks re focussed; it wasn't intentionally British English.
>> Generally we aim for neutral or US-EN. Will leave it for now.
>>
>> And as mentioned in another thread, I should've pointed out that
>> 'comment' can now take 'Comment' as value, alongside the earlier
>> UserComments type.
>>
>> Dan
>>
>> > Draft release notes:
>> >
>> > """1.) This release of schema.org adds a finalized Reservations
>> > schema, which refines earlier proposals discussed in the Web Schemas
>> > community over the last year. See wiki
>> > <https://www.w3.org/wiki/WebSchemas/ReservationsSchema> for details
>> > [todo].
>> >
>> > The Reservations vocabulary includes:
>> >
>> > Reservation, ReservationPackage, ReservationStatusType, Ticket,
>> > Flight, EventReservation, FlightReservation, TrainReservation,
>> > BusReservation, TaxiReservation,  LodgingReservation,
>> > RentalCarReservation, ProgramMembership, Seat, Vehicle, Airline,
>> > FoodEstablishmentReservation, TrainTrip, Car, BusTrip, Taxi.
>> >
>> > See http://sdopending.appspot.com/Reservation and nearby.
>> > I
>> > 2.) QA sites
>> >
>> > A simple vocabulary for Question/Answer and FAQ sites. It adds types
>> > for Question, Answer, and QAPage.
>> >
>> > * http://sdopending.appspot.com/Question
>> > * http://sdopending.appspot.com/Answer
>> > * http://sdopending.appspot.com/QAPage
>> >
>> > 3.) EmailMessage
>> >
>> > * http://sdopending.appspot.com/EmailMessage
>> >
>> > We add a type EmailMessage, analogous to the existing WebPage type."""
>> >
>> > Thanks to everyone who has contributed, in particular St├ęphane
>> > Corlosquet who has been a major contributor to the QA schema work.
>> >
>> > As with the last release I'm circulating a test build here in the hope
>> > (a) that there are no bugs (b) if there are, folks here will catch
>> > them before we go live with the changes. There are a few other small
>> > details to take care of too, including example(s) for QA, and
>> > publishing information on the changes in the Reservation schema since
>> > it was first proposed.
>> >
>> > cheers,
>> >
>> > Dan
>>
>>
>
Received on Wednesday, 26 March 2014 16:21:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:38 UTC