You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2019. It is now read-only.
The specification mentions vocabularies, and vocabulary specifications, dozens of times. It makes assertion about vocabulary design, and about constraints that are imposed by vocabularies. But it never actually says what a vocabulary is.
I think that a lot of the fixing needed is editorial, but given that there is no formal way of processing a vocabulary, we might end up making some substantive changes like removing constraints, or insteadof saying "only if it is allowed by a vocabulary" provide the more actionable "unless invalid according to a machine-readable specification of the item type: or some such.
The text was updated successfully, but these errors were encountered:
In Microdata to RDF a vocabular is established via @itemtype. There is a mechanism to make document-relative URIs if there is no established type. The first version had some arcane URI-building logic to support hcard (IIRC), but that was trimmed in the second version. Most of the logic for building URIs is in Generate Predicate URI.
This should be more or less resolved by #49 - effectively, we don't really say how to define a vocabulary, you can do it how you want. We do note that you can use e.g. prose or something like RDF.
The specification mentions vocabularies, and vocabulary specifications, dozens of times. It makes assertion about vocabulary design, and about constraints that are imposed by vocabularies. But it never actually says what a vocabulary is.
I think that a lot of the fixing needed is editorial, but given that there is no formal way of processing a vocabulary, we might end up making some substantive changes like removing constraints, or insteadof saying "only if it is allowed by a vocabulary" provide the more actionable "unless invalid according to a machine-readable specification of the item type: or some such.
The text was updated successfully, but these errors were encountered: