-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal for a route format standard #27
Comments
Considering the possibility of having more than one picture per "node" of the itemList. I'm thinking that it may a good idea to create a list, as done with the "nodes". In fact we should also consider "videos". |
As @luispc1998 said, there can be one and only one imageObject per itemList, I propose that first we change the name from "image" to "resource" (and from imageObject to resourceObject) because it is messy to call image any type of resource (as you said it can also be a video for example) and that we allow the now called "resource" list to have 0..* of the now called resourceObject |
Yeah thats right. I forgot to include videos and comments for the waypoints. May be posible to add them in two ItemList, one containing media objects and another one containing user comments {
"@context": "http://schema.org",
"@type": "Trip",
"name": "A route 1",
"description": "The test route with all the properties",
"itinerary": {
"@type": "ItemList",
"numberOfItems": 1,
"itemListOrder": "http://schema.org/ItemListOrderDescending",
"itemListElement": [
{
"@type": "GeoCoordinates",
"name": "Waypoint 1",
"address": "Calle Cardenal Cienfuegos",
"addressCountry": "ES",
"elevation": 266,
"latitude": 43.3551061,
"longitude": -5.8512792,
"postalCode": 33007,
"media": {
"@type": "ItemList",
"numberOfItems": 2,
"itemListOrder": "http://schema.org/ItemListOrderDescending",
"itemListElement": [
{
"@type": "VideoObject",
"author": "John Doe",
"contentUrl": "mexico-beach.avi",
"datePublished": "2013-11-28"
},
{
"@type": "ImageObject",
"author": "Jane Doe",
"contentUrl": "mexico-beach.jpg",
"datePublished": "2008-01-25"
}
]
}
}
],
"comments": {
"@type": "ItemList",
"numberOfItems": 2,
"itemListOrder": "http://schema.org/ItemListOrderDescending",
"itemListElement": [
{
"@type": "UserComments",
"commentText": "hello there!",
"commentTime": "2020-02-17T15:58:42",
"creator": "Ben kenobi."
},
{
"@type": "UserComments",
"commentText": "general kenobi!",
"commentTime": "2020-02-17T16:58:42",
"creator": "The angry cyborg"
}
]
}
}
} In this case the comments are part of the route instead of the waypoints. In case the design of our application needs to add comments to the uploaded media we would just have to add the same field inside the GeoCoordinates |
Seems fine to me |
LGTM, but are we really sure about when recovering the data from the pod, the item list nodes will keep the same order of insertion? |
The order of the itemlist should remain after recovering the route. If that does not work we can always add a property order with the index of the element. |
As now there is a new repository dedicated to this topic, this is no longer necesary. |
It would be very interesting if you try to integrate your work with the ViadeSpec work. Some of your ideas are interesting and you can discuss them there if you want. |
Proposal for a route format
The use of a subset of the existing "Trip" scheme from schema.org is proposed to structure the route data
I have tried to reduce the number of properties to the minimum possible, but always with the future in mind in order to extend it in the future if changes arise that would make us require more information
Next, the schemes used that will make up the route are broken down. At the end of the document you can see two examples of routes
Already existing schemas and fields in use
As the web Schema.org says:
To define the route, existing schema.org schemes have been used. This allows us to create a format that is compatible with existing structured data.
A property name in bold means that it is mandatory to define the route
Trip
Complete schema: Trip
GeoCoordinates
Complete schema: GeoCoordinates
ImageObject
Complete schema: ImageObject
ItemList
Complete schema: ItemList
Example of a complete route
Example of a minimum route
An example of a route in RDF Triples
The minimum route from the examples in n-triples
The text was updated successfully, but these errors were encountered: