-
Notifications
You must be signed in to change notification settings - Fork 822
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
StructuredValue description is confusing #109
Comments
See also #394 |
There is a pull request for this at #395 |
Moving my comment in here from #395 pull request. It was: """"Structured values are values that consist of sub-elements and thus have some kind of internal structure." Thanks for making an exact suggestion. We haven't so far used the term "element" heavily; it sounds rather XML-oriented. Maybe something like "Structured values are used when the value of a property has more complex structure than simply being a textual value or a reference to another thing."?""" |
WfM |
I'm still confused by this to be honest. |
Its a Parent Type for holding ANY structured value. 16R22L12R Like my old high school locker combination. Then proceed to describe the structure. Name=LockCombination This is a quick hack and not very applicable, but should help you In Schema.org we use StructuredValue as a parent Type for all those Just don't expect the Search Enginges to fully understand your Use it when you can breakdown a value itself into ...into parts, etc. like |
"If you are messing around near StructuredValue, it would probably be worthwhile to fix up the comment on StructuredValue, which says that structured values are strings, but all the subclasses of StructuredValue are not strings." -- http://lists.w3.org/Archives/Public/public-vocabs/2014Aug/0205.html
http://schema.org/StructuredValue "Structured values are strings—for example, addresses—that have certain constraints on their structure."
Subtypes:
More specific Types
ContactPoint
GeoCoordinates
GeoShape
NutritionInformation
OpeningHoursSpecification
OwnershipInfo
PriceSpecification
QuantitativeValue
TypeAndQuantityNode
WarrantyPromise
The text was updated successfully, but these errors were encountered: